media server behind firewalla not accessible from public internet
I have a firewalla purple+ -> managed switch -> jellyfin on raspberry pi (on vlan). The firewalla is in router mode.
I set up port forwarding, so the usual ports 80 and 443 are sent to the raspberry pi on the ports that jelllyfin expects.
When I'm on my local network (or firewalla VPN), I'm able to load jellyfin via public IP or custom domain name (managed by cloudflare, a .com domain), but not for somebody off network.
I tried running traceroot from a cellular connection. It ran as normal for around 30 hops, then it just freaked out. If I allowed 100 hops, the last 70 hops or so were rapid "no info" hops.
I also wasn't able to see logs from the traceroot / connection attempt in firewalla. IDK.
How can I make my jellyfin server accessible from outside network?
I have rules to allow bidirectional traffic on the jellyfin vlan, I've tried also allowing bidirectional traffic on the device group that the raspberry pi is in, but no dice.
I could post my IP and host name, but I feel like that might be considered sensitive information. I have a great firewall, but I'm not looking to have the whole world come knocking on it ;)
-
I disabled all monitoring and still it's not working, so probably something else.
~~On a related note - I'm trying to troubleshoot, and I can't ping my public IP from outside of network. That should be handled by the firewalla itself, right? Should that work? How can I get that working?~~
Edit: ping is working. The app I was using to ping doesn't work, but running it from termux works fine
-
Fixed! Turns out it was a docker config issue, the jellyfin container needed to exist on the lan (host or macvlan). Used this article.
Something to do with DLNA / service discovery or something.
Networking is hard!
Please sign in to leave a comment.
Comments
3 comments