Hi! I’ve been running QuObjects on my NAS for quite a while now with no issues, but the latest update apparently broke uploads. I managed to get the log files and every single one is failing with HTTP/1.0 400. I couldn’t find much else, but downgrading it to the previous version (2.5.513) solved the problem. Any ideas on how to get more debug information about this?
Hope this helps, in case anyone else is hitting the same issue.
Cheers!
Hi!
I had the same issue after the last upgrade, I fixed just moving the server port from 59000 to 59010.
Best regards
Same here - The latest QuObject release broke uploads.
Reverting to the previous package version works for now.
Changing port numbers does not.
After internal analysis, we were unable to reproduce this issue for the time being. If you are experiencing a similar problem, please feel free to open a support ticket, or send us the logs and settings via private message so our team can further analyze the issue. Thanks!
any solution for this bug?
do you have tested the latest version before release to production? can you imagine our company loss more user because the system can’t access photo profile account to identify the member?
and why you hiding the stable version before?i need to downgrade. can you share quobject 2.5.513 download?
The same issue at TS-673. FW 5.2.9.3410. I can not upload the files or create the folder. Only downloading is working. Changing the port from http:8010 to 5910 does not helps. Storage space contains myS3 folder. Linked bucket is private with the enabled versioning and enabled Number of days to retain and Number of versions to retain. Object lock is disabled. Server configured for HTTP. Client is Brows3 v0.2.34. QuObject version is 2.5.539