starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 09:25:55 +03:00

[GH-ISSUE #1274] Periodic ERR_EMPTY_RESPONSE #1029

New issue

Closed

opened 2026-02-26 06:35:29 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 06:35:29 +03:00

Owner

Originally created by @Spiritreader on GitHub (Jul 29, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1274

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
- Yes
Are you sure you're not using someone else's docker image?
- Yes
Have you searched for similar issues (both open and closed)?
- Yes

Describe the bug

I have an issue where nginx stops sending responses at unspecific intervals, the browser reports ERR_EMPTY_RESPONSE.
It recovers after a minute, but during that time everything is down.
Even the nginx proxy manager Web UI is unreachable during this time.

I have failed to find any logs whatsoever that would indicate the problem.
Where do I need to look in the container to check for this error and potentially find a solution?
I've checked all logs in the mounted data folder, nothing there.
Docker logs (attached below) also don't indicate anything wrong.

I have also ensured that the server is up during that time. Direct port forwards go through, networking is up, the server is pingable at all times, and the underlying containers work as well.

Nginx Proxy Manager Version

2.9.6

To Reproduce
I sadly cannot consistently reproduce this, which makes it very frustrating to diagnose and debug.
Disabling and enabling different hosts seems to have no impact on frequency and it happening in the first place.

Expected behavior

The service should be reliable.

Screenshots

I don't have a screenshot with ERR_EMPTY_RESPONSE, but I do have a screenshot of my monitoring tool catching the issue

It's basically the same message, but the tool checks for TLS, which is why the message slighly differs.

Operating System

Debian Buster

Additional context

The entire docker logs file can be found here
npm_app.log

My docker compose (had to change the file ending to txt)
docker-compose.txt

I would appreciate any help and pointers. I am at wits end.

Originally created by @Spiritreader on GitHub (Jul 29, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1274 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug**  I have an issue where nginx stops sending responses at unspecific intervals, the browser reports ERR_EMPTY_RESPONSE. It recovers after a minute, but during that time everything is down. Even the nginx proxy manager Web UI is unreachable during this time. I have failed to find any logs whatsoever that would indicate the problem. Where do I need to look in the container to check for this error and potentially find a solution? I've checked all logs in the mounted data folder, nothing there. Docker logs (attached below) also don't indicate anything wrong. I have also ensured that the server is up during that time. Direct port forwards go through, networking is up, the server is pingable at all times, and the underlying containers work as well. **Nginx Proxy Manager Version**  2.9.6 **To Reproduce** I sadly cannot consistently reproduce this, which makes it very frustrating to diagnose and debug. Disabling and enabling different hosts seems to have no impact on frequency and it happening in the first place. **Expected behavior**  The service should be reliable. **Screenshots**  I don't have a screenshot with ERR_EMPTY_RESPONSE, but I do have a screenshot of my monitoring tool catching the issue ![image](https://user-images.githubusercontent.com/18438899/127476206-0d76851c-54b5-467e-920d-0d8c3fbda231.png) It's basically the same message, but the tool checks for TLS, which is why the message slighly differs. **Operating System**  Debian Buster **Additional context**  The entire docker logs file can be found here [npm_app.log](https://github.com/jc21/nginx-proxy-manager/files/6899844/npm_app.log) My docker compose (had to change the file ending to txt) [docker-compose.txt](https://github.com/jc21/nginx-proxy-manager/files/6899880/docker-compose.txt) I would appreciate any help and pointers. I am at wits end.

kerem

2026-02-26 06:35:29 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:35:29 +03:00

Author

Owner

@Spiritreader commented on GitHub (Aug 24, 2021):

was not able to fix, but also not able to investigate further.

@Spiritreader commented on GitHub (Aug 24, 2021): was not able to fix, but also not able to investigate further.

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/nginx-proxy-manager-NginxProxyManager#1029

No description provided.

Rows
Columns