Accessing dockerised emby server via IP Address

[healyhatman 3]

When attempting to access emby server via direct ip address I get the error `Could not find a part of the path '\dashboard-ui\index.html'`

I am running Windows 11 and have emby server installed in a docker container and proxied using nginx proxy manager. I can access it via `emby.localhost` just fine, or `localhost:8096` but I cannot access it using `http://my-ip-address:8096` or `127.0.0.1:8096`. I am also unable to connect to it using the app and ip address

If I disable the proxy host in NPM I get the same thing.

docker-compose.yml:

```

  emby:
    image: emby/embyserver
    container_name: emby
    ports:
      - 8096:8096
      - 8920:8920
    volumes:
      - C:/Servarr/emby:/config
      - E:/Movies:/mnt/movies
      - F:/TV Shows:/mnt/tv
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Australia/Sydney
    restart: unless-stopped

```

Settings in NPM are

```

domain names: emby.localhost

scheme: http

forward hostname / ip: emby

forward port: 8096

```

I activated debug logging but it the access attempt doesn't appear to add any entries to embyserver.txt

 

[healyhatman 3]

I can access other dockerised things like prowlarr via the ip address by the way. It's just emby that's not working properly.

[Luke 42077]

Quote

When attempting to access emby server via direct ip address 

Hi, what exactly are you doing?

[healyhatman 3]

I'm trying to access emby server from, say, the app on my tv. I put the I address of my PC in and the port and it doesn't work.

 

If I try to access emby on my browser on my PC, via local host:8096 or 127.0.0.1:8096 or my IP address 192.168.1.3:8096  I get that error message as described. 

[Luke 42077]

What address is in the browser address bar?

[healyhatman 3]

emby.localhost (which works from my PC that docker is running on)

 

 

192.168.1.3:8096 which is the IP of that computer does not work, it gives me that error message.

Edited May 8, 2025 by healyhatman

[Luke 42077]

What is the full address in the browser address bar?

[healyhatman 3]

http://192.168.1.3:8096/web/index.html

[healyhatman 3]

It's 1:30am I'm falling asleep, talk more in about 7 hours.

[Luke 42077]

OK please try clearing browsing data and see if that helps.

After that, if there's still an issue, then please attach the Emby server log from when the problem occurred:

How to Report a Problem

Thanks!

 

[healyhatman 3]

Even with debugging turned on, attempting to access it via the ip does not trigger any log entries.

 

I found this link https://forum.jellyfin.org/t-freebsd-fresh-install-could-not-find-a-part-of-the-path-dashboard-ui-index-html from someone having an identical problem on the Jellyfin fork, if that helps?

Edited May 8, 2025 by healyhatman

[Luke 42077]

Well there’s always a chance that we’ll spot something. Beyond that, then it sounds like it’s just never reaching Emby server so you’ll need to look at whatever is in your network or container setup that is standing in the way.

[healyhatman 3]

Here are the logs anyway

embyserver.txt

[healyhatman 3]

SOLVED

This is very stupid, and I apologise for wasting any of your time.

The issue is that even though I had told Emby for Windows to uninstall, EmbyServer.exe was still running. There was nothing in the tray or in services.msc to hint that it might still be running.

 

Investigation

In powershell I ran the command netstat -aon | findstr :8096 which output

  TCP    0.0.0.0:8096           0.0.0.0:0              LISTENING       66612
  TCP    0.0.0.0:8096           0.0.0.0:0              LISTENING       31828
  TCP    192.168.1.3:8096       0.0.0.0:0              LISTENING       4132
  TCP    [::]:8096              [::]:0                 LISTENING       66612
  TCP    [::1]:8096             [::]:0                 LISTENING       65076
  TCP    [::1]:8096             [::1]:60785            ESTABLISHED     65076
  TCP    [::1]:60785            [::1]:8096             ESTABLISHED     25804

For each entry I ran tasklist /FI "PID eq <id on the right>"

For 31828 the output looked like

tasklist /FI "PID eq 31828"

Image Name                     PID Session Name        Session#    Mem Usage
========================= ======== ================ =========== ============
EmbyServer.exe               31828 Console                    1  1,009,904 K

As soon as I killed that program, I was able to access 192.168.1.3:8096 as normal.