Help! EMBY Won't Connect

[iamanoffering 1]

Hi, all,

So - I purchased a QNAP TS-253D as I wanted to use Emby as a permanent media server solution.

The only problem - after setting up the NAS and drives and volumes, etc., as well as installing Emby onto the QNAP box, I can't connect at all to the local host page to manage the server.

I get a 'connection closed' error.

I tried the stable version found at the QNAP downloads page, (Intel/AMD) then tried the beta version. Neither work.

Disclaimer - I'm not an expert in server/network management by any means, so please be patient. I may have missed some things in the QNAP setup that might be crucial. Any help would be appreciated as I'd love this to work. Ironically it was working better on an old Windows 10 machine that was just constantly running with external hard drives attached to it. I'd rather make this new solution work as I invested a good amount of money into it.

[iamanoffering 1]

Well - look at that - I found some info in another thread that seems like it may be leading me in the right direction. I thought I had done a thorough search.

Turns out you have to type in servername:8096 instead of the local IP. That seems to have done the trick. Could anyone explain why this might be the case?

[Luke 42077]

Enter that where? Ip address should be fine.

[iamanoffering 1]

For whatever reason when I tried to enter app.emby.media into my browser to use Emby connect the connection didn't work. I entered servername:8096 and this worked locally. Remote works through Emby Connect just fine.

[Luke 42077]

22 hours ago, iamanoffering said:

For whatever reason when I tried to enter app.emby.media into my browser to use Emby connect the connection didn't work. I entered servername:8096 and this worked locally. Remote works through Emby Connect just fine.

When you used app.emby.media, what address was in the browser address bar?

[lurch9366 16]

In my case when you click on the emby app in qnap it launches to local ip:8920/  I changed the 8920 to 8096 and it works fine. Not sure why it is auto launching to 8920

[lurch9366 16]

I see why now, https is set for 8920 and http is set for 8096 in the emby server network settings and I run a https plugin on chrome so it is auto changing to https.