Slow startup screen only on local network connection

[jinxed 4]

I recently changed my setup so now i have a dedicated mediaserver running on linuxserver with docker instead of everything on synology. 
With that change i also added reverse proxy manager so i can have access to it publicly.
Maybe i did something wrong or i forgot something i don't know? (Everything works fine though)

When i connect with emby publicly (super fast) and look at the server settings i see the in-home (LAN) and remote (WAN) is the local docker netwerk ip. (is that correct?)
Trying to connect my androidtv to that ip definitely doesn't work so i use the ip from my linuxserver with port 8096. 
The loading screen takes super long like at least 1-2min but when logged in all is running good.

What could cause this and should i connect to the public domain instead? Maybe emby would resolve it automatically to local network? (not sure)
Or did i forget to add something to my reverse proxy manager

[Q-Droid 989]

It's probably trying the Docker IP and timing out then falling back to the one you set in the app. Your dashboard should reflect the actual LAN and WAN URLs you want to use.

You can set the correct values in the server Network settings:

- Local IP Address: the LAN IP you use to connect locally (not Docker network)

- Don't change the local http and https port numbers.

- Check (enable) Allow Remote Connections.

- Public https port number: the port used for the WAN URL.

- External domain: enter your domain name

- Read proxy headers: "Only when they contain remote network addresses"

- Secure connection mode: "Handled by reverse proxy"

 

 

[Luke 42077]

HI, if this doesn't help resolve your issue, then please attach the emby server log from when the problem occurred:

How to Report a Problem

Thanks !

[jinxed 4]

I did some testing with the provided answer.
I have set LAN networks and Local IP address the same, or should i only fill in local ip?
On the dashboard i now see:

•  LAN access correct (server ip with port 8096)
• WAN access (external domain with port 8920)

After restarting the docker container everything is good and emby is loading fast on my tv now!

Thanks for the help
 

[Q-Droid 989]

LAN networks is meant to be a network or subnet, not a single IP address and as shown in the help text. So if your assigned LAN IPs are like "192.168.1.n" the entry in that field would be "192.168.1.0/24" (CIDR notation). This helps when the docker subnet is different from the LAN subnet then the Emby server can treat them as local devices. 

 

Edited September 3, 2024 by Q-Droid

[Luke 42077]

Quote

I have set LAN networks and Local IP address the same, or should i only fill in local ip?

Why did you fill in those values in the first place? Was there a reason?

[Q-Droid 989]

I recommended they be set because Emby is running in docker and by default it detects the internal docker network and shows the wrong URLs in the dashboard. 

[Luke 42077]

14 minutes ago, Q-Droid said:

I recommended they be set because Emby is running in docker and by default it detects the internal docker network and shows the wrong URLs in the dashboard. 

Got it. Yes that would be one reason.