Emby - wrong external IP and not connecting

[Happy2Play 9780]

1 minute ago, Utini said:

This is what I do not know either.

Basically I only changed 3074 on my xbox to something custom (lets say 50000).

Then I created a port forward for "external" 50000.

I would guess external 3074 to internal 5000 but will do a little searching.

[Utini 14]

Just now, Happy2Play said:

I would guess external 3074 to internal 5000 but will do a little searching.

Hmm my main reason to change to a custom port was for security purpose.

So I would want "external" to be 5000 and "internal" to be 3074.

That still gives "port closed" on canyouseemee though

[Carlo 4560]

It's fine to change the external port which is helpful to those running scripts looking for known ports used by certain apps.
However, there really is no reason to change the internal port unless you are running multiple versions of Emby on the same machine.

Keep in mind once you forward the port on the router it's using you local LAN to get to Emby Server.  So Emby is listening on the Internal port.
When it see's the IP address embedded in the packets it knows it was an external address.  Emby then marks the packets with a return port you set in settings.

This way the client will get the public port.  The router intercepts this on the public port then port forwards it to the IP/port you set to your local Emby Server (usually port 8096).

Hope that helps.