So I’m just getting started with selfhosting things, and I have a minor problem which I’m having some trouble solving, as I keep getting a connection refused error when trying to connect:
send() failed (111: Connection refused) while resolving, resolver: 127.0.0.1:53
I run a jellyfin server on a NUC - it works well and is accessible on the private network. I want to have a public URL for this server - and other stuff, eventually.
Here’s my setup
- I have a subdomain - jellyfin.mydomain.com - pointed to the external IP for my router
- I have the router set up to allow remote access, and port forwarding directing all port 80 traffic to my public ip > port 80 on the server
- On my server - running ubuntu - I installed nginx
- I used the official jellyfin nginx config for access from a subdomain
- I edited the server_name variable to match my subdomain
Now, whenever I access the subdomain in a browser I get a 502 Bad Gateway error. The /var/lof/nginx/error.log
shows:
2024/05/10 08:26:37 [error] 95335#95335: send() failed (111: Connection refused) while resolving, resolver: 127.0.0.1:53
2024/05/10 08:26:37 [error] 95335#95335: send() failed (111: Connection refused) while resolving, resolver: 127.0.0.1:53
2024/05/10 08:26:42 [error] 95335#95335: send() failed (111: Connection refused) while resolving, resolver: 127.0.0.1:53
2024/05/10 08:26:47 [error] 95335#95335: send() failed (111: Connection refused) while resolving, resolver: 127.0.0.1:53
2024/05/10 08:26:52 [error] 95335#95335: send() failed (111: Connection refused) while resolving, resolver: 127.0.0.1:53
2024/05/10 08:26:57 [error] 95335#95335: send() failed (111: Connection refused) while resolving, resolver: 127.0.0.1:53
2024/05/10 08:27:02 [error] 95335#95335: send() failed (111: Connection refused) while resolving, resolver: 127.0.0.1:53
2024/05/10 08:27:07 [error] 95335#95335: *69 jellyfin could not be resolved (110: Operation timed out), client: 193.29.107.173, server: jellyfin.mysubdomain.com, request: "GET /web/ HTTP/1.1", host: "jellyfin.mysubdomain.com"
I have almost no experience with networking, linux, or nginx :D So I am sure the problem is obvious to someone else…
Can you help?
I’d be very careful to publicly host Jellyfin. Although not necessarily true, it basically advertises that you’re pirating content while also giving out your IP. Even if you rip your own media, this can still be illegal. Please be careful.
Maybe you can put it behind some authentication or, even better, a VPN.
You have a point, thx
Hello 👋
You need to edit the below lines
set $jellyfin jellyfin; resolver 127.0.0.1 valid=30s;
To look like the below
set $jellyfin 127.0.0.1; #resolver 127.0.0.1 valid=30s;
Edited after reading the full config
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters CGNAT Carrier-Grade NAT DNS Domain Name Service/System HTTP Hypertext Transfer Protocol, the Web IP Internet Protocol NAT Network Address Translation VPN Virtual Private Network nginx Popular HTTP server
4 acronyms in this thread; the most compressed thread commented on today has 5 acronyms.
[Thread #771 for this sub, first seen 29th May 2024, 09:05] [FAQ] [Full list] [Contact] [Source code]