Skip to content
New issue

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

Nginx logs hundreds of errors per day #750

Open
solracsf opened this issue Jul 5, 2024 · 1 comment
Open

Nginx logs hundreds of errors per day #750

solracsf opened this issue Jul 5, 2024 · 1 comment
Assignees

Comments

@solracsf
Copy link

solracsf commented Jul 5, 2024

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:

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

@solracsf
Copy link
Author

I wonder if switching from Nginx to Caddy wouldn't be a good move since it handles everything out of the box (even Websockets).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants