+- 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! - sunnythe14 - 2024-02-11
(2024-02-11, 04:25 AM)TheDreadPirate Wrote: Where did you put the IP? I meant in the "Forward Hostname/IP" put the LAN IP for jellyfin.
that's exactly what I did:
Now my setup is:
NPM Forwards to machine's local IP with JF port,
Router is port forwarding 5555 and 5556 to 80 and 443.
NPM in compose still says 80:80 and 443:443.
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - TheDreadPirate - 2024-02-11
Port 8096 is http. Change the scheme to http. The external connection will still be https.
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - sunnythe14 - 2024-02-11
(2024-02-11, 04:59 AM)TheDreadPirate Wrote: Port 8096 is http. Change the scheme to http. The external connection will still be https.
IT WORKS!!! Thank you so much!!!
In your exoert opinion, now that I wouldn't be using CloudFlare proxy and just NPM, considering my IP is exposed, how risky is sharing my server with one or two friends?
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - TheDreadPirate - 2024-02-11
Not any more risky than with the CF proxy. Unless one of your friends is a Russian FSB hacker or something.
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - sunnythe14 - 2024-02-11
(2024-02-11, 06:04 AM)TheDreadPirate Wrote: Not any more risky than with the CF proxy. Unless one of your friends is a Russian FSB hacker or something.
Good to hear. Thank you so much for all your help. Incredibly appreciated.
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - sunnythe14 - 2024-03-14
Reopening this issue.
Everything has stopped working;
I haven't changed any configs on CF or Docker; I've only added 2 containers to the compose, dash and heimdall.
I cannot access JF or JS through a browser via the external subdomains.
The regular external domain with no subdomain used to point to my router login, now that does nothing.
The connection times out with no error code. Pinging the external address is successful and points to my external IP, as do the subdomains.
Completely at a loss here as everything was working fine not too long ago.
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - TheDreadPirate - 2024-03-14
When you say "CF", is this the CF proxy tunnel? Or just the IP update app?
Walk back ANY changes you made until it starts working. This is assuming one of the changes broke it.
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - sunnythe14 - 2024-03-14
(2024-03-14, 06:18 PM)TheDreadPirate Wrote: When you say "CF", is this the CF proxy tunnel? Or just the IP update app?
Walk back ANY changes you made until it starts working. This is assuming one of the changes broke it.
Alright, I'll try that, thanks.
I'm just using CloudFlare to manage the DNS; their proxy or tunnel aren't being used.
Thanks chief!
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - sunnythe14 - 2024-03-14
(2024-03-14, 06:18 PM)TheDreadPirate Wrote: When you say "CF", is this the CF proxy tunnel? Or just the IP update app?
Walk back ANY changes you made until it starts working. This is assuming one of the changes broke it.
Hello good sir, figured it out.
Cloudflare was pointing to an external IP address that my ISP changed.
Do know of a way to solve for this easily?
Thanks for all your help!
RE: NPM reverse proxy, Cloudflare, Docker Compose help! - TheDreadPirate - 2024-03-14
This?
https://developers.cloudflare.com/dns/manage-dns-records/how-to/managing-dynamic-ip-addresses/
Also check if your router supports DDNS for Cloudflare. Freshtomato, my router's firmware, supports Cloudflare's API for updating the IP.