Emby Server app uses the wrong address, causing Connection Refused

[JDutton 10]

The Emby Server app on a Windows PC that is directly connected to the router is using https://.../8920, however 8920 is not a port configured in Emby Server. Both the  in-home and remote access are defined with the same address: http://.../8096. All other devices, local and remote, use /8096 and connect correctly.

Can the app be changed to use the /8096 port, or should one of the addresses in Emby Server be changed to https:// .../8920? 

Thanks,

Jeff

[JDutton 10]

Correction: The remote access address is not the same as the in-home address, but the port in both is /8096.

[Luke 42077]

Hi @JDutton does your emby server dashboard display the correct local and remote addresses?

[JDutton 10]

The local address appears to be correct. The remote address is different than the local address, but I don't remember what it is supposed to be. Is there some way to find out what it should be?

What puzzles me is that every device, whether within my wireless network or outside my wireless network has no trouble connecting. Only the PC that is directly wired into the router has this problem.

When I look at the port-forwarding in my router, it only has a single address, which matches the local address in the emby server dashboard.  

[Luke 42077]

Then you should just be connecting using your local lan address and not trying to use the remote address if the machine is inside your network. Please let us know if this helps. Thanks.

[bwlonsdale 0]

I'm a new (QNAP) user with same issue - the port change isn't reflected in the launcher from the QNAP front end, so if you change local/remote ports to something else, it will always launch and try to connect on default port (8096), resulting in server not being found.

Not a big deal as long as you don't change the ports - if there's a requirement to change, I suggest mapping an external port to the default ones on your router rather than in Emby itself.

[JDutton 10]

I apologize, I wasn't clear in trying to describe the problem. I hope this is better.

The remote address is not a factor. The problem is that he QNAP Emby app (version 4.6.7.0) is trying to open Emby using an address that is not in the dashboard display. The correct local address is http://.../8096. The app is trying to use https://...8920, which does not match the local or remote address.

I have no idea where the app is getting the incorrect address from.

[Luke 42077]

54 minutes ago, JDutton said:

I apologize, I wasn't clear in trying to describe the problem. I hope this is better.

The remote address is not a factor. The problem is that he QNAP Emby app (version 4.6.7.0) is trying to open Emby using an address that is not in the dashboard display. The correct local address is http://.../8096. The app is trying to use https://...8920, which does not match the local or remote address.

I have no idea where the app is getting the incorrect address from.

Hi, it's because the QNAP app requires SSL, but this is only going to work if you've setup SSL on your Emby Server. That's why you end up needing to change to the http address with the http port.

[JDutton 10]

How did this change? I have not changed the addresses in any way and only began to have this problem on the day I sent the original post. It has been working fine for a year until that day. Also, this one PC is the only device (local or remote) that is having this problem. Why would that be?

If I change the addresses to SSL (I assume that means the same as HTTPS) will that affect remote users who are currently able to successfully access the server? Also, why would the port number be incorrect? I haven't changed that either.

Here's a thought: I recently installed an updated version of Qfinder Pro. Could that have anything to do with this? 

Sorry for so many questions, but this just isn't making sense.

[JDutton 10]

Problem solved! The issue had to do with the latest version of Qfinder Pro that I installed not too long ago. I was also getting an error when I tried to access the server with it, but thought it was a coincidence that the error was occurring with Emby. I have a laptop that wasn't having the problem, and discovered today that it has an earlier version of QFinder Pro.

I installed an earlier version of Qfinder Pro on the PC and the problem has gone away.

 

[Luke 42077]

1 hour ago, JDutton said:

How did this change? I have not changed the addresses in any way and only began to have this problem on the day I sent the original post. It has been working fine for a year until that day. Also, this one PC is the only device (local or remote) that is having this problem. Why would that be?

If I change the addresses to SSL (I assume that means the same as HTTPS) will that affect remote users who are currently able to successfully access the server? Also, why would the port number be incorrect? I haven't changed that either.

It has always been this way. You can't just "change' the address to ssl. You have to first setup SSL on your Emby Server.