+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Jellyfin through caddy only accessable on local network (/t-jellyfin-through-caddy-only-accessable-on-local-network)
Jellyfin through caddy only accessable on local network - bond-title-bond - 2023-11-08
Hello,
huge noob here.
I have jellyfin setup on debian going though caddy as a reverse proxy to my domain. I have cloudflare handling dns. Everything works when I'm connected to the local network but when I try to access it in public it doesn't work.
I mostly followed this tutorial https://www.youtube.com/watch?v=zCyx4vmp4k0 but changed a few things. mainly I didn't include the api because it was giving me an error.
I also have openvpn running on the whole server. I tried it with and without it running with no change.
Does anyone know what I need to do to get this going?
Thanks in advance!
RE: Jellyfin through caddy only accessable on local network - weberc2 - 2023-11-08
How does it fail (what error are you getting)? Are you trying to access it via your VPN or the public Internet? without more information, my guess is the DNS entry contains the private IP address of your server rather than the public address—you can use
dig or nslookup to check the IP address associated with your domain name.
RE: Jellyfin through caddy only accessable on local network - bond-title-bond - 2023-11-08
On web browsers it just doesn't load. On the android app it says "Tried 5 candidates for input, without success. Unable to reach server" then it shows 5 variations of my domain (https, http, port 8096 and 8920.
I'm trying to access it via public internet.
The nameserver is pointed at cloudflare. And DNS on cloudflare is pointed at my public IP.
It was working yesterday morning. But I uninstalled openmediavault because I couldn't get it to stop listening to port 80 and I caddy kept telling me I had a syntax error on the caddyfile. Once it was working (accessible via public internet through my domain name) I reinstalled openmediavault. I forgot to set the private IP to static so it changed. I couldn't get caddy to reload the new IP on the caddyfile without getting errors so I reinstalled caddy, changed the caddyfile to exactly what it was except the IP change and now it only works when I'm connected to the local network
RE: Jellyfin through caddy only accessable on local network - TheDreadPirate - 2023-11-08
When the local IP changed did you update your routers port forwarding rule?
RE: Jellyfin through caddy only accessable on local network - bond-title-bond - 2023-11-08
Hello again!
Yes I updated the ports
RE: Jellyfin through caddy only accessable on local network - TheDreadPirate - 2023-11-08
In the network dashboard, is "remote connections" enabled? Is there a remote IP allow list?
RE: Jellyfin through caddy only accessable on local network - weberc2 - 2023-11-08
(2023-11-08, 08:12 AM)bond-title-bond Wrote: On web browsers it just doesn't load. On the android app it says "Tried 5 candidates for input, without success. Unable to reach server" then it shows 5 variations of my domain (https, http, port 8096 and 8920.
I'm trying to access it via public internet.
The nameserver is pointed at cloudflare. And DNS on cloudflare is pointed at my public IP.
It was working yesterday morning. But I uninstalled openmediavault because I couldn't get it to stop listening to port 80 and I caddy kept telling me I had a syntax error on the caddyfile. Once it was working (accessible via public internet through my domain name) I reinstalled openmediavault. I forgot to set the private IP to static so it changed. I couldn't get caddy to reload the new IP on the caddyfile without getting errors so I reinstalled caddy, changed the caddyfile to exactly what it was except the IP change and now it only works when I'm connected to the local network
I've never used CloudFlare before, but I would check their logs to see if you can tell whether it's getting hit or not. I would also check Caddy's logs to see if the requests are making it to Caddy. Depending on the results, you might consider pulling CloudFlare out of the path altogether by pointing DNS directly at your public IP address (one other thing to verify is that you don't have any firewall rules in the path, particularly if you're using a cloud provider). Essentially you have to figure out where the failure point is (maybe you're already identifying that it's a caddy problem? I can't quite tell).