Jellyfin remote access Asustor NAS

[sup3rdonk3y]

Hi all,

I have recently purchased an Asustor NAS to serve primary as mediaserver for Jellyfin.

LAN operation is working perfectly, but i cannot get remote access. I studied and executed college topics 221, 224, 324, 325. 

DDNS seems to be setup, certificate seems to be in place (however chrome says it is not a secured connection "https/" but does not give the pop-up where I needed to manually continue anymore) and reverse proxy seems to be online. I can access the reverse proxy link via my PC on the same LAN as the NAS. However when i use a hotspot and type in the link of the reverse proxy in my browser, it loads for a while (~20 sec) then changes to the local adress HTTPS port 192.168.xxx.xxx:xxxx.  and then after a minute or so gives the error "this site can't be reached".

My router does support Upnp and the right ports seem to be forwarded in the settings of the router (via upnp)

Does anybody have an idea where I am messing up? Help would be greatly appreciated.

[TheDreadPirate]

UPnP should not be relied on for port forwarding and I don't think the proxy even requests a port be open. Jellyfin itself will request 8096 be opened, but since you are using a proxy we aren't using that. Manually open port 443 in your router's settings.

[sup3rdonk3y]

UPnP should not be relied on for port forwarding and I don't think the proxy even requests a port be open.  Jellyfin itself will request 8096 be opened, but since you are using a proxy we aren't using that.  Manually open port 443 in your router's settings.

Thanks for your reply! I believe EZ-router within the ADM software arranges port forwarding in the router. I checked the router and in the port forwarding tab 443 is open.
Any other suggestions?

[TheDreadPirate]

Does your ISP give you an individual IP? Or are they using CGNAT?

[bitmap]

Did you enable HTTPS in Jellyfin's network settings? If so, that might be the issue. When using reverse proxy, the certs and management of HTTPS are handled by the reverse proxy, not Jellyfin itself.

[TheDreadPirate]

Did you enable HTTPS in Jellyfin's network settings? If so, that might be the issue. When using reverse proxy, the certs and management of HTTPS are handled by the reverse proxy, not Jellyfin itself.

I think there would be a problem if they checked "require https" and the comms between the reverse proxy and Jellyfin were unencrypted, which is usually the case.

[bitmap]

I fully admit this is not my realm and it sounds more like a near-infinite loop than my experience with learning what I suggested the hard way. The behavior I experienced with having my RP setup correctly and then trying to enable HTTPS was complete inaccessibility of my Jellyfin instance. But I learned long ago that one experience doesn't fully encapsulate software behavior in similar circumstances.

[sup3rdonk3y]

Hi All,

I also posted this thread on another forum (Asustor). The solution for me was disabling the EZ-router and manually add the ports in my router configuration.
Thanks a lot for your input!