We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do you want to request a feature or report a bug?
Upstream errors
What is the current behavior?
Docker container nginx.error.log spits hundreds of errors per day
nginx.error.log
[error] recv() failed (104: Unknown error) while reading response header from upstream
or
[error] connect() failed (111: Unknown error) while connecting to upstream
[error] upstream timed out (110: Unknown error) while reading response header from upstream
What is the expected behavior?
These errors are handled by either the Nginx server or the Upstream (Converter service)
Did this work in previous versions of DocumentServer?
No
DocumentServer Docker tag:
sudo docker run -i -t -d -p 80:80 \ -v /app/onlyoffice/DocumentServer/logs:/var/log/onlyoffice \ -v /app/onlyoffice/DocumentServer/data:/var/www/onlyoffice/Data \ -v /app/onlyoffice/DocumentServer/lib:/var/lib/onlyoffice \ -v /app/onlyoffice/DocumentServer/rabbitmq:/var/lib/rabbitmq \ -v /app/onlyoffice/DocumentServer/redis:/var/lib/redis \ -v /app/onlyoffice/DocumentServer/db:/var/lib/postgresql \ onlyoffice/documentserver
Host Operating System:
Ubuntu 22.04
The text was updated successfully, but these errors were encountered:
I wonder if switching from Nginx to Caddy wouldn't be a good move since it handles everything out of the box (even Websockets).
Sorry, something went wrong.
avdddd1111
No branches or pull requests
Do you want to request a feature or report a bug?
Upstream errors
What is the current behavior?
Docker container
nginx.error.log
spits hundreds of errors per day[error] recv() failed (104: Unknown error) while reading response header from upstream
or
[error] connect() failed (111: Unknown error) while connecting to upstream
or
[error] upstream timed out (110: Unknown error) while reading response header from upstream
What is the expected behavior?
These errors are handled by either the Nginx server or the Upstream (Converter service)
Did this work in previous versions of DocumentServer?
No
DocumentServer Docker tag:
Host Operating System:
Ubuntu 22.04
The text was updated successfully, but these errors were encountered: