I instaled to Debian 12 onlyoffice community server 9.1.0.168.
Next errro if I tried open in thridparty webapp:
[ERROR] [localhost] [019324ae-7037-7581-a391-e3bef81f3ace.1731592666] [696d0f00-5db6-4b56-bca9-c216f70423f3] nodeJS - error downloadFile:url=https://server/s3elma365/60f474c9-d4bb-4531-a41b-3ae38fe171cb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=PZSF73JG72Ksd955JKU1HIA%2F20251114%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20251114T084230Z&X-Amz-Expires=28800&X-Amz-SignedHeaders=host&response-content-disposition=attachment%3B%20filename%3D".docx"%3B%20filename*%3DUTF-8''%25D0%2594%25D0%25BE%25D0%25B3%25D0%25BE%25D0%25B2%25D0%25BE%25D1%2580.docx%3B&X-Amz-Signature=1c070eb9f6aff37faf3c33bcd08e607d7c4e5b97a52fd270bc49401e6491e580;attempt=3;code:ERR_BAD_REQUEST;connect:undefined AxiosError: Request failed with status code 400
at settle (/snapshot/server/Common/node_modules/axios/dist/node/axios.cjs)
at RedirectableRequest.handleResponse (/snapshot/server/Common/node_modules/axios/dist/node/axios.cjs)
at RedirectableRequest.emit (node:events:536:35)
at RedirectableRequest._processResponse (/snapshot/server/Common/node_modules/follow-redirects/index.js:409:10)
at ClientRequest. (/snapshot/server/Common/node_modules/follow-redirects/index.js:102:12)
at Object.onceWrapper (node:events:639:26)
at ClientRequest.emit (node:events:524:28)
at HTTPParser.parserOnIncomingClient (node:_http_client:702:27)
at HTTPParser.parserOnHeadersComplete (node:_http_common:118:17)
at TLSSocket.socketOnData (node:_http_client:544:22)
at Axios.request (/snapshot/server/Common/node_modules/axios/dist/node/axios.cjs)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Object.downloadUrlPromise (/snapshot/server/Common/sources/utils.js)
I’m solved))
Hey @DmitryS, 
Super glad you got it working!
It would be really helpful for the community if you could share how you solved it — just a quick note on what was causing the 400 error and what fixed it. That way if someone else runs into the same thing with third-party storage, they’ll find the answer right away.
Thanks a lot and congrats on fixing it! 
Hello, I encountered the same problem. How did you solve it?
Hello @Jacob
Usually such error appears when a server is configured incorrectly. You should start with simple port check to make sure that requests are sent and received correctly. Also, keep in mind that proxy services can also cause this type of error.