ishmo65 0 Posted September 10 Posted September 10 (edited) I've seen this discussed in another conversation thread, but there was no solution. This is a new install of Emby on 2 separate Qnap systems. Both do not work when I open the web interface. I'm getting: This site can’t be reached 192.168.1.21 refused to connect. full url is 192.168.1.21:8920 (also tried http and https) I rebooted both servers but get the same issues (refused to connect). I have also installed Emby on a Synology server (last night) without any issues, although the web interface port opening in Chrome from that NAS is 8096 ... I've also tried that with the two Qnap addresses without success. Note: The exclamation mark in the QNAP screenshot is due to the absence of a digital signature. Edited September 10 by ishmo65 added more tags
Neminem 617 Posted September 10 Posted September 10 Try with port 8096. As port 8920 is for when you have a valid ssl certificate.
ishmo65 0 Posted September 10 Author Posted September 10 @JayceDKClearly, you've not read the full issue text... I clearly said: ... installed Emby on a Synology server (last night) without any issues... Chrome from that NAS is 8096 ... I've also tried that with the two Qnap addresses without success.
GrimReaper 3746 Posted September 10 Posted September 10 Quote QNAP Emby server ok but web interface starts/fails on port 8920 4 hours ago, ishmo65 said: This is a new install of Emby on 2 separate Qnap systems. Both do not work when I open the web interface. I'm getting: This site can’t be reached 192.168.1.21 refused to connect. full url is 192.168.1.21:8920 (also tried http and https) You cannot connect to port 8920 for local connections if you don't have SSL setup (typically involving reverse proxy configured accordingly). You need to use local-IP:8096. If that failed (and you've confirmed that server is actually running), something is blocking incoming connections to your server - don't know whether QNAP has built-in firewall or maybe you have double NAT setup in your network or it is something else. In either case, you should try to obtain server logs (you'll likely have to SSH into your NAS), maybe some fellow QNAP user might chime in about latest location, from what I gathered from past topics, it might be something like either: /share/CACHEDEV1_DATA/.qpkg/Emby/Emby/ProgramData-Server/logs or /share/xxxxx_DATA/.qpkg/ folder How to Report a Problem
One2Go 105 Posted September 10 Posted September 10 Mine is on a different port 8097 and I have no problems connecting.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now