Comment on Having trouble setting up Nginx
pirateMonkey@lemmy.world 3 weeks agoI’m still very much in a learning mode here, so forgive my ignorance - which logs? Nginx? I’m seeing a fallback_error and fallback_access (which has nothing interesting). There are also some empty files for the host I have set up (proxy-host-1_access/error)
2025/09/01 12:34:54 [error] 193#193: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.181, server: nginxproxymanager, request: “GET /api/ HTTP/1.1”, upstream: “127.0.0.1:3000”, host: “192.168.1.196:81”, referrer: “192.168.1.196:81/nginx/certificates”
Where, presumably obviously, 196 is the server and 181 is a laptop. FWIW I don’t see the directory it’s mentioning, /nginx/certificates, but I’m looking at the host’s directory rather than in the container.
frongt@lemmy.zip 3 weeks ago
The upstream refused the connection. You have it there as 127.0.0.1, but for inter-container communication usually you’d use the name. 127.0.0.1 would refer to the same container.
Docker (and other container platform) networking is a bit tricky and I’ll admit I don’t fully understand how it works, because it doesn’t work like regular networking. But a simple scenario like yours shouldn’t be difficult.
Lyra_Lycan@lemmy.blahaj.zone 3 weeks ago
Docker also has its own LAN IP address, in my experience it’s 172.17.0.1 instead of 127.0.0.1. And yes, between containers the container name is used, e.g. plexserver:2736, and it’s good practice to manually give them names.
frongt@lemmy.zip 3 weeks ago
Yes, there is the internal subnet, but it’s not something you’re supposed to use directly.
pirateMonkey@lemmy.world 3 weeks ago
Even without full understanding, I think you’re a few steps ahead of me! I was also under the impression that it would be fairly straightforward, but getting lessons in how to troubleshoot (and I appreciate them!)
I was testing with 127.0.0.1 earlier, so that’s makes sense on one level, but not port 3000.
Is my understanding correct that the upstream connection was refused means that it went to Cloudflare who then sent it back to my server, and it was rejected there?
frongt@lemmy.zip 3 weeks ago
If your request is showing up in nginx’s log, it means you can reach nginx. The upstream is where nginx is going to get the content you want. In your case, that should be the other containers.
pirateMonkey@lemmy.world 3 weeks ago
Yep, that makes sense. Thank you!