[GH-ISSUE #243] GUI does not work anymore #212

Closed
opened 2026-02-26 06:31:32 +03:00 by kerem · 3 comments
Owner

Originally created by @Merrick28 on GitHub (Nov 20, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/243

Describe the bug

The GUI does not work anymore. The proxy hosts already added continue to work.
When I Try to connect to http://ip:81, I hace no answer.

seed@op:~/docker-compose$ docker logs -f proxymanager
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.                                                                        
[s6-init] ensuring user provided files have correct perms...exited 0.                                                                                
[fix-attrs.d] applying ownership & permissions fixes...                                                                                              
[fix-attrs.d] done.                                                                                                                                  
[cont-init.d] executing container initialization scripts...                                                                                          
[cont-init.d] done.                                                                                                                                  
[services.d] starting services                                                                                                                       
[services.d] done.                                                                                                                                   
[11/20/2019] [9:10:37 AM] [Global   ] › ✖  error     connect ETIMEDOUT                                                                               
[11/20/2019] [9:10:48 AM] [Global   ] › ✖  error     connect ETIMEDOUT                                                                               
[11/20/2019] [9:10:59 AM] [Global   ] › ✖  error     connect ETIMEDOUT                                                                               
[11/20/2019] [9:11:10 AM] [Global   ] › ✖  error     connect ETIMEDOUT                                                                               
[11/20/2019] [9:11:21 AM] [Global   ] › ✖  error     connect ETIMEDOUT                                                                               
[11/20/2019] [9:11:32 AM] [Global   ] › ✖  error     connect ETIMEDOUT                                                                               
[11/20/2019] [9:11:43 AM] [Global   ] › ✖  error     connect ETIMEDOUT                                                                               
[11/20/2019] [9:11:54 AM] [Global   ] › ✖  error     connect ETIMEDOUT                                                                               
[11/20/2019] [9:12:05 AM] [Global   ] › ✖  error     connect ETIMEDOUT                                                                               
[11/20/2019] [9:12:16 AM] [Global   ] › ✖  error     connect ETIMEDOUT                                                                               
[11/20/2019] [9:12:27 AM] [Global   ] › ✖  error     connect ETIMEDOUT                                                                               
[11/20/2019] [9:12:38 AM] [Global   ] › ✖  error     connect ETIMEDOUT                                                                               
[11/20/2019] [9:12:49 AM] [Global   ] › ✖  error     connect ETIMEDOUT                                                                               
[11/20/2019] [9:13:00 AM] [Global   ] › ✖  error     connect ETIMEDOUT                                                                               
[11/20/2019] [9:13:11 AM] [Global   ] › ✖  error     connect ETIMEDOUT                                                                               
[11/20/2019] [9:13:22 AM] [Global   ] › ✖  error     connect ETIMEDOUT                                                                               
[11/20/2019] [9:13:33 AM] [Global   ] › ✖  error     connect ETIMEDOUT                                                                               
[11/20/2019] [9:13:44 AM] [Global   ] › ✖  error     connect ETIMEDOUT         

When I go into the container :

seed@op:~/docker-compose$ docker exec -it proxymanager bash                                                                                          
[root@docker-9208b9ea7100:/]# cd /data/logs/                                                                                                         
[root@docker-9208b9ea7100:/data/logs]# tail error.log 
2019/11/20 09:12:29 [error] 226#226: *418 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: localho
st, request: "GET /health HTTP/1.1", upstream: "http://127.0.0.1:81/health", host: "localhost:9876"                                                  
2019/11/20 09:12:35 [error] 226#226: *10 upstream timed out (110: Connection timed out) while connecting to upstream, client: 185.16.252.2, server: j
ackett.sdewitte.net, request: "GET /UI/Dashboard HTTP/1.1", upstream: "http://172.21.0.6:9117/UI/Dashboard", host: "jackett.sdewitte.net", referrer: 
"https://jackett.sdewitte.net/UI/Dashboard"                                                                                                          
2019/11/20 09:12:45 [error] 226#226: *453 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: localho
st, request: "GET /health HTTP/1.1", upstream: "http://127.0.0.1:81/health", host: "localhost:9876"                                                  
2019/11/20 09:13:00 [error] 226#226: *481 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: localho
st, request: "GET /health HTTP/1.1", upstream: "http://127.0.0.1:81/health", host: "localhost:9876"                                                  
2019/11/20 09:13:16 [error] 226#226: *514 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: localho
st, request: "GET /health HTTP/1.1", upstream: "http://127.0.0.1:81/health", host: "localhost:9876"                                                  
2019/11/20 09:13:32 [error] 226#226: *544 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: localho
st, request: "GET /health HTTP/1.1", upstream: "http://127.0.0.1:81/health", host: "localhost:9876"                                                  
2019/11/20 09:13:36 [warn] 226#226: *552 using uninitialized "server" variable while logging request, client: 172.21.0.1, server: localhost, request:
 "GET /robots.txt HTTP/1.1", host: "mercury.tvlogy.to"                                                                                               
2019/11/20 09:13:47 [error] 226#226: *577 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: localho
st, request: "GET /health HTTP/1.1", upstream: "http://127.0.0.1:81/health", host: "localhost:9876"                                                  
2019/11/20 09:14:03 [error] 226#226: *607 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: localho
st, request: "GET /health HTTP/1.1", upstream: "http://127.0.0.1:81/health", host: "localhost:9876"                                                  
2019/11/20 09:14:19 [error] 226#226: *635 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: localho
st, request: "GET /health HTTP/1.1", upstream: "http://127.0.0.1:81/health", host: "localhost:9876"   
  • What version of Nginx Proxy Manager is reported on the login page?
    I cannot see, as I don't have a login page anymore...

Operating System

  • Linux server
steph@op:~$ uname -a                                                                                                                                 
Linux op 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux                                                 
steph@op:~$ more /etc/lsb-release                                                                                                                    
DISTRIB_ID=Ubuntu                                                                                                                                    
DISTRIB_RELEASE=18.04                                                                                                                                
DISTRIB_CODENAME=bionic                                                                                                                              
DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS"   
Originally created by @Merrick28 on GitHub (Nov 20, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/243 **Describe the bug** The GUI does not work anymore. The proxy hosts already added continue to work. When I Try to connect to http://ip:81, I hace no answer. ``` seed@op:~/docker-compose$ docker logs -f proxymanager [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. [11/20/2019] [9:10:37 AM] [Global ] › ✖ error connect ETIMEDOUT [11/20/2019] [9:10:48 AM] [Global ] › ✖ error connect ETIMEDOUT [11/20/2019] [9:10:59 AM] [Global ] › ✖ error connect ETIMEDOUT [11/20/2019] [9:11:10 AM] [Global ] › ✖ error connect ETIMEDOUT [11/20/2019] [9:11:21 AM] [Global ] › ✖ error connect ETIMEDOUT [11/20/2019] [9:11:32 AM] [Global ] › ✖ error connect ETIMEDOUT [11/20/2019] [9:11:43 AM] [Global ] › ✖ error connect ETIMEDOUT [11/20/2019] [9:11:54 AM] [Global ] › ✖ error connect ETIMEDOUT [11/20/2019] [9:12:05 AM] [Global ] › ✖ error connect ETIMEDOUT [11/20/2019] [9:12:16 AM] [Global ] › ✖ error connect ETIMEDOUT [11/20/2019] [9:12:27 AM] [Global ] › ✖ error connect ETIMEDOUT [11/20/2019] [9:12:38 AM] [Global ] › ✖ error connect ETIMEDOUT [11/20/2019] [9:12:49 AM] [Global ] › ✖ error connect ETIMEDOUT [11/20/2019] [9:13:00 AM] [Global ] › ✖ error connect ETIMEDOUT [11/20/2019] [9:13:11 AM] [Global ] › ✖ error connect ETIMEDOUT [11/20/2019] [9:13:22 AM] [Global ] › ✖ error connect ETIMEDOUT [11/20/2019] [9:13:33 AM] [Global ] › ✖ error connect ETIMEDOUT [11/20/2019] [9:13:44 AM] [Global ] › ✖ error connect ETIMEDOUT ``` When I go into the container : ``` seed@op:~/docker-compose$ docker exec -it proxymanager bash [root@docker-9208b9ea7100:/]# cd /data/logs/ [root@docker-9208b9ea7100:/data/logs]# tail error.log 2019/11/20 09:12:29 [error] 226#226: *418 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: localho st, request: "GET /health HTTP/1.1", upstream: "http://127.0.0.1:81/health", host: "localhost:9876" 2019/11/20 09:12:35 [error] 226#226: *10 upstream timed out (110: Connection timed out) while connecting to upstream, client: 185.16.252.2, server: j ackett.sdewitte.net, request: "GET /UI/Dashboard HTTP/1.1", upstream: "http://172.21.0.6:9117/UI/Dashboard", host: "jackett.sdewitte.net", referrer: "https://jackett.sdewitte.net/UI/Dashboard" 2019/11/20 09:12:45 [error] 226#226: *453 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: localho st, request: "GET /health HTTP/1.1", upstream: "http://127.0.0.1:81/health", host: "localhost:9876" 2019/11/20 09:13:00 [error] 226#226: *481 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: localho st, request: "GET /health HTTP/1.1", upstream: "http://127.0.0.1:81/health", host: "localhost:9876" 2019/11/20 09:13:16 [error] 226#226: *514 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: localho st, request: "GET /health HTTP/1.1", upstream: "http://127.0.0.1:81/health", host: "localhost:9876" 2019/11/20 09:13:32 [error] 226#226: *544 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: localho st, request: "GET /health HTTP/1.1", upstream: "http://127.0.0.1:81/health", host: "localhost:9876" 2019/11/20 09:13:36 [warn] 226#226: *552 using uninitialized "server" variable while logging request, client: 172.21.0.1, server: localhost, request: "GET /robots.txt HTTP/1.1", host: "mercury.tvlogy.to" 2019/11/20 09:13:47 [error] 226#226: *577 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: localho st, request: "GET /health HTTP/1.1", upstream: "http://127.0.0.1:81/health", host: "localhost:9876" 2019/11/20 09:14:03 [error] 226#226: *607 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: localho st, request: "GET /health HTTP/1.1", upstream: "http://127.0.0.1:81/health", host: "localhost:9876" 2019/11/20 09:14:19 [error] 226#226: *635 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: localho st, request: "GET /health HTTP/1.1", upstream: "http://127.0.0.1:81/health", host: "localhost:9876" ``` - What version of Nginx Proxy Manager is reported on the login page? I cannot see, as I don't have a login page anymore... **Operating System** - Linux server ``` steph@op:~$ uname -a Linux op 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux steph@op:~$ more /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS" ```
kerem 2026-02-26 06:31:32 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@Merrick28 commented on GitHub (Nov 20, 2019):

My bad, I had an issue on my docker network...

<!-- gh-comment-id:556054059 --> @Merrick28 commented on GitHub (Nov 20, 2019): My bad, I had an issue on my docker network...
Author
Owner

@Matt-CyberGuy commented on GitHub (Apr 3, 2021):

What did you do to fix this? I've been having this issue non-stop

<!-- gh-comment-id:812800123 --> @Matt-CyberGuy commented on GitHub (Apr 3, 2021): What did you do to fix this? I've been having this issue non-stop
Author
Owner

@Merrick28 commented on GitHub (Apr 4, 2021):

I honestly don't remember... I think I put the docker in a specific network that was not available from internet, but I'm not 100% sure. Sorry.

<!-- gh-comment-id:813033083 --> @Merrick28 commented on GitHub (Apr 4, 2021): I honestly don't remember... I think I put the docker in a specific network that was not available from internet, but I'm not 100% sure. Sorry.
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/nginx-proxy-manager-NginxProxyManager#212
No description provided.