2024-12-05, 08:57 AM
Newbie to Jellyfin. Not much better than a newbie on NAS. Good to very good on Windows (although I still have occasional wtf moments with 11).
Installed Jellyfin into a container on my NAS (Synology DS224+ with DSM 7.2.2-72806 Update 2). Manage through a Windows 11 workstation on the same LAN. Did make some goofs along the way. Retried and worked out the issues. In Container Manager, jellyfin stops and restarts just fine, with no error messages.
Following these directions https://www.wundertech.net/how-to-set-up...ology-nas/ for DSM 7.2 with hardware acceleration.
The next step is to connect to the jellyfin configuration wizard. Using
http://[NAS_IP]:8096 (substituting in my 11 digit IP for my NAS).
Getting a "This site can't be reached" error page from a Chrome Incognito instance. Tried this with jellyfin both started and stopped. Tried it with and without a /web at the end of the URL.
If I try this:
http://[NAS_IP]
I connect immediately to my Synology desktop.
My firewall is run through Avast One. I am getting that error page when its firewall is turned OFF.
Side Issue: I also have not figured out yet how to open that port for an app that's not on one of my hard drives, but that seems less important for now.
Suggestions? (Yes, first thing I did was a complete cache clear on Chrome then a restart).
Installed Jellyfin into a container on my NAS (Synology DS224+ with DSM 7.2.2-72806 Update 2). Manage through a Windows 11 workstation on the same LAN. Did make some goofs along the way. Retried and worked out the issues. In Container Manager, jellyfin stops and restarts just fine, with no error messages.
Following these directions https://www.wundertech.net/how-to-set-up...ology-nas/ for DSM 7.2 with hardware acceleration.
The next step is to connect to the jellyfin configuration wizard. Using
http://[NAS_IP]:8096 (substituting in my 11 digit IP for my NAS).
Getting a "This site can't be reached" error page from a Chrome Incognito instance. Tried this with jellyfin both started and stopped. Tried it with and without a /web at the end of the URL.
If I try this:
http://[NAS_IP]
I connect immediately to my Synology desktop.
My firewall is run through Avast One. I am getting that error page when its firewall is turned OFF.
Side Issue: I also have not figured out yet how to open that port for an app that's not on one of my hard drives, but that seems less important for now.
Suggestions? (Yes, first thing I did was a complete cache clear on Chrome then a restart).