SOLVED: Newbie Can't Connect to Wizard

[BooBounder]

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).

[Ted Hinklater]

Have you tried http://localhost:8096/web/index.html#!/wizardstart.html

[TheDreadPirate]

Did you add the firewall rule on the NAS's firewall?

[BooBounder]

1 to Ted Hinklater) I tried that before going to # 2 below. Both with and without the Avast firewall on. Same answer as before: a "This site can't be reached" page.

2 to TheDreadPirate) I have now. I do not have any details on how this rule should be set up. I did set one up to allow TCP through 8096. Tried the original URL and the one from Ted Hinklater, without an Avast firewall, and got the same answer: a "This site can't be reached" page.

---

Also not clear if my container/project jellyfin should be started or stopped while doing all of this.

[TheDreadPirate]

http://192.168.X.X:8096

Whatever your NAS's IP is. "localhost" only applies if you are running Jellyfin on the same machine you are access it from, which isn't the case here.

[BooBounder]

Woo-hoo. Progress. Combination of 8096 port opened to TCP on the NAS, Jellyfin container/project started with a green light, and using the numerical address of my NAS. Did not need my Avast firewall opened.

Still trying to figure out Jellyfin at a busy time of the year, but I think this thread is done.

---

One last thing ... believe it was the suggestion to add a rule for Jellyfin *** to the firewall of the NAS *** that made the difference.