Public HTTP and Public HTTPS not functional.

[aterfax 0]

I assume that the public http and https options are supposed to bind the ports and then be forwarded through the router with the use of the separate ports to denote the public (login) page.

I have my linux box running Emby, ports are 8098 and 8099.

Ports are forwarded via the router - not working.

Testing from the LAN on to those ports with direct IP and with hostname - not working

Netstat and telnet does not show emby binding the 8098 or 8099 port.

Is this a bug or am I misunderstanding something?

As this is ran in a docker host mode, docker forwarding should be irrelevant.

Ultimately I just want to prevent random people using my media centre as admin and forwarding the default ports just logged them in as admin. Is there an alternative working method?

[Luke 37118]

Hi, I think you misunderstand or have the wrong perception. There isn't actually any function behind these settings. It is only so that Emby Server can figure out what your full remote address is so that it can:

• display the address on the emby server dashboard
• inform emby apps of this address

Ultimately you are still responsible for making sure the traffic can make it from point A to point B. Does this answer your question?

[aterfax 0]

>assume that the public http and https options are supposed to bind the ports and then be forwarded through the router with the use of the separate ports to denote the public (login) page.

This menu needs a bit of clarification as I was expecting a Plex like situation where the LAN subnet is automatically granted access to the device except Emby was attempting the demarkation via port binding rather than subnet checking.

[Luke 37118]

The public ports = your router ports. Note the help text under the public port field:

The public port number that should be mapped to the local http port.

The local ports are what Emby Server will bind to. Note the help text under the local port field:

The tcp port number that Emby's http server should bind to.

So the router should be configured to forward the public port to the local port on your emby server. Please let us know if this helps. Thanks.

[aterfax 0]

The public ports = your router ports. Note the help text under the public port field:

The public port number that should be mapped to the local http port.

The local ports are what Emby Server will bind to. Note the help text under the local port field:

The tcp port number that Emby's http server should bind to.

So the router should be configured to forward the public port to the local port on your emby server. Please let us know if this helps. Thanks.

 

I understand the concept of port forwarding and how to implement it.

 

As I said, I had expected the public http port and public https port to be a second set of ports for remote access only.

 

i.e. ports 8096 and 8097 for LAN and 8098 and 8099 for WAN where the former are the local ports and latter public ports. So I expected Emby to bind 2 sets of ports or  4 in total.

[Luke 37118]

Ok, no, Emby only binds to the local ports. You will need to configure your router to forward the public ports to local ports.

 

Our automatic port mapping feature does attempt to do this for you, but it's not guaranteed to work with all router models.

[pse 9]

Some more detail: I tried setting "local networks" to 192.168.178.0/24 now (even though that should have been detected automatically). The problem remains -- if I set X-Forwarded-For to 127.0.0.1, Emby thinks I'm local again. Setting it to 192.168.178.x has the same effect, as expected. A "foreign" IP like 192.168.199.199 is rejected, though. So it seems X-Forwarded-For is checked in some way -- but the real Problem is, that this header should not be trusted in any way!