+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access)
+---- Thread: NPM reverse proxy, Cloudflare, Docker Compose help! (/t-npm-reverse-proxy-cloudflare-docker-compose-help)
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - Zhaytoshi - 2024-04-12
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - TheDreadPirate - 2024-04-12
But what about on your router?
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - Zhaytoshi - 2024-04-12
yes its open checked with ping.eu both 80 and 443 is open.
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - TheDreadPirate - 2024-04-12
Oh. I didn't see your prior post with the router settings. The port forwarding needs to go to Nginx's docker IP, which probably starts with 172.X.X.X.
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - Zhaytoshi - 2024-04-12
oh i see thank you I've changed it to 127.0.1.1 in the router but still no luck. and test all the containers IP still not working.
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - TheDreadPirate - 2024-04-12
127.0.0.1 is localhost, which definitely wouldn't work. The address would start with 172, not 127.
Code:
docker inspect jellyfinRE: NPM reverse proxy, Cloudflare, Docker Compose help! - Zhaytoshi - 2024-04-12
ah yes i see. thank you got it wrong. and its weird just like you said it should be 172.XXX
nginxproxymanager IP : 192.168.48.3
Code:
"Links": null,
"Aliases": [
"nginxproxymanager",
"d6f9bfa517e9"
],
"Gateway": "192.168.48.1",
"IPAddress": "192.168.48.3",
"IPPrefixLen": 20,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"DriverOpts": null,
"DNSNames": [
"nginxproxymanager",
"d6f9bfa517e9"My Jellyfin Doesn't have an IP ? is this normal and by the way when i run docker ps its showing unhealthy ? maybe this is the problem ?
Code:
"Networks": {
"host": {
"IPAMConfig": null,
"Links": null,
"Aliases": null,
"MacAddress": "",
"NetworkID": "90084333c399987e39c933ab53c64ea9b7452f5c302ee8394aef544fe8f14d85",
"EndpointID": "3b29349cf268f9faa6ee800fee2b206b004b149c9f8622a7d218841e8745eef1",
"Gateway": "",
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"DriverOpts": null,
"DNSNames": nullRE: NPM reverse proxy, Cloudflare, Docker Compose help! - TheDreadPirate - 2024-04-12
Sorry. I'm mixing us both up. I meant "docker inspect nginxproxymanager". 192.168.48.3 is definitely not typical for a docker IP, but let's go with that for the port forwarding rule.
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - Zhaytoshi - 2024-04-13
It's fine, and I was exhausted last night, haha. Despite reinstalling and starting from the beginning, I am still unable to find any success. No luck again. Thanks for the help. Any information, I will gladly try my best to follow.
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - TheDreadPirate - 2024-04-13
I have to get to bed and won't be on until tomorrow night (US Eastern). The video tutorial has a lot of, IMO, unnecessary stuff. It sounds like they are trying to fiddling around with private IPs in Cloudflare to try to keep traffic local instead of going out to the Internet only to come back to your home. But this is resolved by enabling a feature called "NAT loopback" or "NAT hairpin" in your router (most support this, but some don't).