Babatom 6 Posted January 16 Posted January 16 Hi, ich teste gerade Emby, Server ist auf Unraid installiert mit Portmapping 8099:8096 weil Jellyfin schon auf 8096 läuft. Sobald ich die App schließe iOS & tvOS bekomme ich immer den Fehler "Server muss aktualisiert werden" und er zeigt mir die "ServerIP :8096" an obwohl ich beim einrichten ja Port 8099 angegeben habe. Ist das ein Bug oder mache ich was falsch? In den Server einstellungen unter Übersicht zeigt er mir auch an : Heimnetzwerk-Zugriff (LAN): http://10.18.2.2:8096.
Luke 42077 Posted January 16 Posted January 16 Hi, from the iOS and tvOS app, try doing a new server connection and manually entering the address and port. please see if that helps.
Babatom 6 Posted January 16 Author Posted January 16 Yes, of course, that's something I've had to do several times already. But why is port 8096 saved when I enter 8099?
Luke 42077 Posted January 17 Posted January 17 8 hours ago, Babatom said: But why is port 8096 saved when I enter 8099? What makes you think port 8096 is saved when you enter 8099? Can you please show a screenshot example of exactly what you are doing? Thanks !
Babatom 6 Posted January 17 Author Posted January 17 (edited) It happens with both the internal IP address and my domain. When I connect to the server with the internal IP address, I choose port 8099; for the domain, I don't specify a port. The connection works. As soon as I close and reopen the app, I get the error "The server needs to be updated." When I go to the info, I see that port 8096 is saved. Edited January 17 by Babatom
Luke 42077 Posted January 17 Posted January 17 Quote for the domain, I don't specify a port Where exactly are you not entering a port? I don't see any screenshot of the manual server entry screen...
Babatom 6 Posted January 17 Author Posted January 17 Come on... forget the domain. I connect to 10.18.2.2:8099 and it works. If I close the app and reopen it, I get the error. If I go to "forget this server," I see that 10.18.2.2:8096 is saved. Then I delete the server and enter 10.18.2.2:8099 again, and it works again.
Luke 42077 Posted January 17 Posted January 17 Does your emby server dashboard display the correct LAN and WAN addresses that you want to connect to?
Babatom 6 Posted January 17 Author Posted January 17 No. The LAN address shows port 8096, and the WAN address shows HTTP, not HTTPS. Under settings-network-external domain, I've entered the correct subdomain with https://. (The external connection works.)
Luke 42077 Posted January 20 Posted January 20 Quote I've entered the correct subdomain with https://. (The external connection works.) Hi, this isn't the way to setup https on your emby server. There are dedicated https options on the network settings screen. Can you please configure those? Then see if the server dashboard reflects your changes. Thanks.
Babatom 6 Posted January 20 Author Posted January 20 Sorry, but I don't quite understand. In the Unraid template, I've set the port mapping to 8099:8096 for HTTP and 8922:8920 for HTTPS. Local access works with internal_ip:8099, and externally I'm using a subdomain and a reverse proxy(caddy), with the subdomain pointing to internal_ip:8099. I have now set the following in the Emby network settings: local HTTP port 8099 and external HTTP port 8099. Now I can no longer access my server.
Babatom 6 Posted January 21 Author Posted January 21 Ich bekomme das Problem nicht in den Griff. Habe mal meine Netzwerk Einstellung gescreenshottet, vielleicht sieht jemand den fehler! Ich kann mich Intern einloggen mit 10.18.2.2:8099 Von extern geht es mit emby.meinedomain.de Beides funktioniert bis ich die App komplett schließe, dann kommt immer der Fehler aus Post #5. ( iOS & tvOS ) emby.meinedomain.de wird von Caddy (VPS) auf 10.18.2.2:8099 geroutet, habe CGNat deswegen ein VPS. ----- Ich habe außerdem Emby Connect probiert, mein Admin Account mit meinem Emby Account verbunden. Dann einen neuen User erstellt, vorher für diesen ebenfalls einen Emby Account angelegt und dann eingeladen. Der User verbindet sich auch und ich sehe meinen Server aber wenn ich darauf klicke bekomme ich wieder "Verbindung zum Server nicht möglich". ( Diese Verbindung soll auch von extern erfolgen )
Luke 42077 Posted January 22 Posted January 22 Now does the server dashboard display the addresses that you want to connect with?
Babatom 6 Posted January 22 Author Posted January 22 As you can see in my screenshot of the Unraid template, I'm mapping port 8099 to 8096. So, when I want to connect to Emby, whether via the app or browser, I use port 8099. The Emby dashboard shows port 8096. When I connect to Emby via a domain, again with the app or browser, I only use the subdomain without specifying a port, but the Emby dashboard does show a port number. A port MUST be specified in the network settings.
Luke 42077 Posted January 22 Posted January 22 Quote Now does the server dashboard display the addresses that you want to connect with? So yes? And what router ports do you want to use?
Babatom 6 Posted January 23 Author Posted January 23 @Luke Okay, I think it's a bug or a restriction with the Apple client apps. I tested the Emby app on Android TV and I don't have this problem there. No matter what server address I enter in Apple, it always tries to connect via port 8096 after restarting. The only solution for me is probably to disable port forwarding and use 8096. 18 hours ago, Luke said: So yes? Please take a look at the first screenshot from my last post. The address http://10.18.2.2:8096 is displayed there for LAN, and I see exactly this address every time I restart the app, even though I previously set up the server with http://10.18.2.2:8099. After restarting the client app, it simply ignores what I used previously. 18 hours ago, Luke said: And what router ports do you want to use? None at all; no ports are open on the router. The external connection goes through a VPS with a reverse proxy, which is connected to my Unraid server via WireGuard. emby.mydomain.com --> 10.18.2.2:8099
Luke 42077 Posted January 29 Posted January 29 On 1/20/2026 at 2:04 AM, Babatom said: Sorry, but I don't quite understand. In the Unraid template, I've set the port mapping to 8099:8096 for HTTP and 8922:8920 for HTTPS. Local access works with internal_ip:8099, and externally I'm using a subdomain and a reverse proxy(caddy), with the subdomain pointing to internal_ip:8099. I have now set the following in the Emby network settings: local HTTP port 8099 and external HTTP port 8099. Now I can no longer access my server. Hi, these are not Emby server settings. These look like TrueNAS container settings. It looks like you also want to set 8099 in the local port number field in emby server network settings.
Babatom 6 Posted January 29 Author Posted January 29 1 hour ago, Luke said: These look like TrueNAS container settings Unraid. 1 hour ago, Luke said: It looks like you also want to set 8099 in the local port number field in emby server network settings. I've now simply left Emby on port 8096 and assigned Jellyfin port 8099. This works flawlessly with all clients, both Emby and Jellyfin.
Am0kSepp 6 Posted January 30 Posted January 30 Hi, i also have the same issue. i have disabled the remote access, have configured an reverse proxy (cloudflare zero trust) but the access is not working through emby app on ios. It works fine from my browser safari and firefox, but as soon i try to connect with the app on iOS device i got the same error.
Luke 42077 Posted January 30 Posted January 30 40 minutes ago, Am0kSepp said: Hi, i also have the same issue. i have disabled the remote access, have configured an reverse proxy (cloudflare zero trust) but the access is not working through emby app on ios. It works fine from my browser safari and firefox, but as soon i try to connect with the app on iOS device i got the same error. Hi, perhaps try enabling remote access?
Am0kSepp 6 Posted January 30 Posted January 30 (edited) 29 minutes ago, Luke said: Hi, perhaps try enabling remote access? Makes no difference, i started with the default setup, and tried every combination of remote access. enabled, disabled, enforced ssl, revers proxy decide, standard port normal port ec. ec. It's always the same error. And it is always that only the iOS App can not connect. On Normal Computer with Browser it works every time, no matter what is configured. The connection always comes from the reverse proxy machine, which is internal. I think there is something wrong how the emby server pushes the connection info to the iOS client. Cause no matter what i configure in the app it always has the server with its private ip and port 8096 configured. It is complete ignoring the setup i enter with url of my public faced reverse proxy on default ssl port. Clients -> proxyurl:443 -> Proxy -> internalIP:8096 Thats how it is setup and working from External with any browser. But not with the emby app Btw the emby app throw this error also when i try to connect via internal network and the ip:8096 Edited January 30 by Am0kSepp
Babatom 6 Posted January 30 Author Posted January 30 1. Allow remote connections to this Emby Server must be enabled. 2. Enter the domain under "external domain" 3. "Secure connection mode" -> handled reverse proxy Thats works for me. The app only failed to save the changes when I changed the default port to 8096 in the container template, but the connection always worked for me.
Am0kSepp 6 Posted January 30 Posted January 30 No Remote has not to be enabled, as the reverser proxy builds the connection from internal interface. And as mentioned, Emby App also fails when the iPad i in internal network and tries to connect to internal ip of emby server.
Luke 42077 Posted January 31 Posted January 31 9 hours ago, Am0kSepp said: No Remote has not to be enabled, as the reverser proxy builds the connection from internal interface. And as mentioned, Emby App also fails when the iPad i in internal network and tries to connect to internal ip of emby server. Right but trying it for testing purposes would be helpful to try to narrow down the problem.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now