Problems with remote access

[GruttePier]

Hi all,

First time poster here. I have issues accessing my Jellyfin remotely. I'm not very familiar with all this, so I'm hoping some of you can help me out. Of note: my remote access with Plex used to work fine, so I suppose the easiest way to find out what went wrong is something in the Jellyfin settings. 

I run Jellyfin on my Synology NAS. I Installed Jellyfin through a docker. I also have NordVPN running on my NAS. This is where I'm not entirely sure how it works, but I have two active network interfaces. and the default gateway is my VPN. The NAS is on a static IP address. 

I forwarded port 32400 in my router settings for Plex (TCP). This worked fine, and continues to work. I thought I could simply forward port 8096 for Jellyfin, enable "allow remote connections to this server" in the jellyfin settings, and be done with it. But somehow it doesn't work. I don't have an active firewall on my NAS (Firewall is disabled under the security tab anyhow). I also did mess around a bit with trying to set up a reverse proxy through a let's encrypt certificate. This works in so far that I can now access my synology within my network through  the domain that i set up but it does not work remotely. I thought I maybe finished this process prematurely, because i cannot figure out how to gain access to my ssl certificates. But I thought until i figure out this, i should at least be able to access my jellyfin remotely trough the direct port forward? 

When I use online tools to see if my ports are succesfully forwarded, all mentioned ports show up as closed. Even the 32400 for Plex while I have remote access just fine. Also when I run command -ano | findstr "LISTENING" I do not see any of the relevant ports show up. This confuses me. One final thing that may be relevant: when i try to access router information on my nas through the remote access tab, I get a notification saying "Your gateway setting is invalid". But again, all this time my Plex is working so something else must be off. 

Happy to hear any ideas!

[bitmap]

Reverse proxies should be listening on 443 and nothing else (maybe 80 if you're redirecting). Port forwarding is an extremely insecure way to provide remote access as you're punching a hole directly into your internal network.

What RP are you trying to use?

[pxr5]

Unlike Plex, Jellyfin takes a bit more work to get remote access working.

I'd strongly suggest following this guide to use Caddy as your reverse proxy. Caddy itself can run any device on your LAN, all you have to make sure is ports 80/443 are forwarded in your router to the device running Caddy. Personally I use an old Raspberry Pi to run Caddy. Caddy does all the work for you - certificates etc. all you need is one simple Caddyfile with this in:

yourdomain.com {
       reverse_proxy 192.168.x.xx:8096
}

https://forum.jellyfin.org/t-access-your...with-caddy

[GruttePier]

Reverse proxies should be listening on 443 and nothing else (maybe 80 if you're redirecting). Port forwarding is an extremely insecure way to provide remote access as you're punching a hole directly into your internal network.

What RP are you trying to use?

Thanks for the feedback. It sounds like I need to figure out how to work with Caddy, also as suggested by the other poster on this thread. I'm gonna try that. Thank you!

[GruttePier]

Unlike Plex, Jellyfin takes a bit more work to get remote access working.

I'd strongly suggest following this guide to use Caddy as your reverse proxy. Caddy itself can run any device on your LAN, all you have to make sure is ports 80/443 are forwarded in your router to the device running Caddy. Personally I use an old Raspberry Pi to run Caddy. Caddy does all the work for you - certificates etc. all you need is one simple Caddyfile with this in:

yourdomain.com {
       reverse_proxy 192.168.x.xx:8096
}

https://forum.jellyfin.org/t-access-your...with-caddy

Thank you! I should be able to run Caddy on my synology right? through Docker? I found a way to install the image, but I'm lost setting it up. I think the guide you sent assumes Caddy is already running. I'm looking at this guide, but it's a little outdated and i cannot figure out how to add/link files and folders, and also what to do with "environment"

/ https://ibb.co/9Hmxx62K

[bitmap]

Under volumes, you could map both /config and /data to specific folders. That's what the volumes area is for. The environment area is to set specific variables (defaults are already set for some in your image) the image uses during setup.

If you don't map /config and /data to specific folders, you will likely lose your data when restarting the image.

Here's a little more info from Caddy's site: https://caddyserver.com/docs/running#docker-compose

There's not likely to be much Synology specific from an official source, but the docker compose setup should translate pretty nicely to the interface you're using.