Getting a ERR_CONNECTION_REFUSED

[sgtcoder]

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? No
• Have you searched for similar issues (both open and closed)? Yes

Describe the bug This is the docker compose file

version: '3'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - /root/nginx:/data
      - /root/letsencrypt:/etc/letsencrypt

Then I run

docker compose -f /root/docker-compose.yml up -d

I try to goto the web page: http://10.0.6.23:81 and I get a ERR_CONNECTION_REFUSED.

I tried to even telnet 10.0.6.23 81 and telnet 127.0.0.1 81, I also get connection refused. Some dockers I have this problem with, while others I don't. I also removed all my running dockers and networking. Yes of course I can ping.

Nginx Proxy Manager Version the latest

To Reproduce Described above

Expected behavior The webpage should load

Screenshots telnet 10.0.6.23 81

Operating System Debian 11

Additional context Latest of everything

[Vegas10128]

And this is still left unanswered which is annoying, its almost like my last resort is to wipe a drive and reinstall ubuntu just to get this to work.

[JoryHogeveen]

Same issue here

[infinitydon]

I am having the same issue, created a fresh VM all together and it's the same..

[github-actions[bot]]

Issue is now considered stale. If you want to keep it open, please comment :+1:

[chenxiaoquan233]

same issue here

[Crazor]

I'm potentially facing the same issue, but for me it's intermittant. Services work just fine, but once or twice a day, I start to get "ERR_CONNECTION_REFUSED" from the browser. What's strange is that a different browser on the same machine works just fine, until it gets to the same point where the connection is just refused (without any error messages in the log). When I look at the proxied service's logs, I cannot see a single request get through once a browser starts acting up. This also happens with python scripts querying XML-RPC API endpoints on the same service. The issue resolves itself after a couple of minutes or sometimes hours, so I haven't figured out any regularity. Also I'm at a loss as how to proceed debugging the issue.

[Crazor]

I've sorted out my issues, which were totally unrelated to Nginx Proxy Manager. I'm posting this as a headsup for anyone that is suspecting having issues with NPM, like I did for a while: I have a split-horizon DNS setup that runs on the same docker host. Unfortunately, somehow my machine had the ISPs DNS server set up as a secondary resolver. Every once in a blue moon, macOS decided to switch over to the ISP DNS, and thus starting to resolve my subdomains with an external IP instead of the internal one. This then creeps into various browsers with various delays, as they all seem to handle their own DNS caching these days. Flushing the DNS cache resolved the issue for CLI tools and Safari every time. Once I removed the secondary DNS from my config, the other browsers stopped misbehaving too.