[GH-ISSUE #750] Nginx logs hundreds of errors per day #339

Open
opened 2026-02-26 10:31:57 +03:00 by kerem · 1 comment
Owner

Originally created by @solracsf on GitHub (Jul 5, 2024).
Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/750

Originally assigned to: @avdddd1111 on GitHub.

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

Originally created by @solracsf on GitHub (Jul 5, 2024). Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/750 Originally assigned to: @avdddd1111 on GitHub. **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
Author
Owner

@solracsf commented on GitHub (Jul 21, 2024):

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

<!-- gh-comment-id:2241565184 --> @solracsf commented on GitHub (Jul 21, 2024): 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 in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Docker-DocumentServer-ONLYOFFICE#339
No description provided.