SOLVED: No access to synology nas remotely

SOLVED: No access to synology nas remotely - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: No access to synology nas remotely (/t-solved-no-access-to-synology-nas-remotely)

No access to synology nas remotely - vince - 2025-02-24

Hi and sorry for the post but I can't find a solution anywhere.
I have a synology nas and I can't access the jellyfin server remotely. I opened port 8096 but it doesn't work.
I type: https://myservername:8096 but it doesn't work.
Where am I going wrong? What should I do?
I would be very grateful if you could help me.
Thanks

RE: No access to synology nas remotely - TheDreadPirate - 2025-02-24

You are using https on port 8096. You need to use plain http on that port.

RE: No access to synology nas remotely - vince - 2025-02-25

(2025-02-24, 01:47 PM)TheDreadPirate Wrote: You are using https on port 8096. You need to use plain http on that port.

Thanks, I'm really stupid. If I wanted to use https I just have to open port 8920 and enable it in the jellyfin settings right? So it could be https://myservername:8920?

RE: No access to synology nas remotely - TheDreadPirate - 2025-02-25

It would require you provide a certificate. You cannot enable https and use that port without a cert.

However, we recommend using a proper http server, like apache, nginx, or caddy, to handle https connections. They are more secure and there are apps that integrate with those apps to automate getting legitimate certificates.

https://jellyfin.org/docs/general/networking/nginx/
https://jellyfin.org/docs/general/networking/apache/
https://jellyfin.org/docs/general/networking/caddy/

RE: No access to synology nas remotely - vince - 2025-02-26

(Yesterday, 02:03 PM)TheDreadPirate Wrote: It would require you provide a certificate. You cannot enable https and use that port without a cert.

However, we recommend using a proper http server, like apache, nginx, or caddy, to handle https connections. They are more secure and there are apps that integrate with those apps to automate getting legitimate certificates.

https://jellyfin.org/docs/general/networking/nginx/
https://jellyfin.org/docs/general/networking/apache/
https://jellyfin.org/docs/general/networking/caddy/

Ok that's fine. Thank you very much.