+- 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)
NPM reverse proxy, Cloudflare, Docker Compose help! - sunnythe14 - 2024-02-11
Hey there,
Been trying to get Nginx Proxy Manager, along with a custom domain managed in Cloudflare, Jellyfin, JSeer and the *arrs to work nicely.
So far I've had no success.
Here's my setup:
Cloudflare DNS records
NPM Proxy host setup for JF
JF Proxy host SSL settings
JS Proxy host setup
Properly Activated Cert with LetsEcrypt
Forwarded port on my Router
I've also attached my Docker compose file.
I also am unsure if I'm supposed to forward port 80 on my router, and if that's the case, my ISP blocks port 80, so if that's causing issues, how do I go about that?
Finally, "Allow remote connections to this server" is activated on JF, but none of the services are accessible.
EDIT: WITH STEPS TRIED:
1. Everything works with local IP
2. browsing to the setup subdomain and domain with https e.g. "https://jf.*****.xyz" leads me to Cloudflare error 522
3. Browsing to public ip with designated container subdomains doesn't work (as expected if it's passing through NPM)
4. Browsing to public ip takes me to router login
5. Browsing to domain, no subdomain takes me to router login
Please help, I've been on this for three days lol
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - tmsrxzar - 2024-02-11
what tests have you ran and what were the results?
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - TheDreadPirate - 2024-02-11
1) Turn off proxying in CF. Streaming video through a CF tunnel/proxy is against their TOS
2) On your ROUTER port forwarding rules, change the external port to some port other than 443/80. But the internal port can stay 443/80. Save
3) In your browser tack on the new port to the URL.
I am pretty sure there is a way to get NPM to listen on a different port, but my cursory searches aren't finding a straightforward answer.
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - sunnythe14 - 2024-02-11
(2024-02-11, 03:24 AM)tmsrxzar Wrote: what tests have you ran and what were the results?
edited my post for visibility
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - sunnythe14 - 2024-02-11
(2024-02-11, 03:43 AM)TheDreadPirate Wrote: 1) Turn off proxying in CF. Streaming video through a CF tunnel/proxy is against their TOS
2) On your ROUTER port forwarding rules, change the external port to some port other than 443/80. But the internal port can stay 443/80. Save
3) In your browser tack on the new port to the URL.
I am pretty sure there is a way to get NPM to listen on a different port, but my cursory searches aren't finding a straightforward answer.
tried:
disabled proxy, forwarded 5555 to 80 and 5556 to 443, tried browsing to jf.*****.xyz and
jf.*****.xyz:5555/5556, with both http and https; no avail.
using just domain no subdomain also fails entirely now, unless adding port 5555, which leads me to nginx default page for non set up hosts
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - TheDreadPirate - 2024-02-11
At any point have you restarted NPM? It sounds like it only has the default config. Any changes you make to NPM require it be restarted.
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - sunnythe14 - 2024-02-11
(2024-02-11, 04:02 AM)TheDreadPirate Wrote: At any point have you restarted NPM? It sounds like it only has the default config. Any changes you make to NPM require it be restarted.
Yeah, ive done docker compose up and down a few times now, but just to be clear, was I supposed to change the ports in NPM compose.yml to?
e.g.: from 443:443 to 5556:443?
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - TheDreadPirate - 2024-02-11
In NPM, instead of using the hostnames for your services, put in the IP.
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - sunnythe14 - 2024-02-11
(2024-02-11, 04:14 AM)TheDreadPirate Wrote: In NPM, instead of using the hostnames for your services, put in the IP.
By doing so, now i get
error SSL_ERROR_RX_RECORD_TOO_LONG with port 5555 at end of url
bad gateway 502 with port 5556 at end of url
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - TheDreadPirate - 2024-02-11
Where did you put the IP? I meant in the "Forward Hostname/IP" put the LAN IP for jellyfin.