Emby app on iOS and iPadOS won't connect to server

[casperr0426 1]

About four hours ago, I was still able to use the Emby app on my iPhone 16 Pro Max (running the latest iOS version, in case that matters). Later, I tried connecting using my iPad—after freshly installing the Emby app—but it wouldn’t connect. When I went back to my iPhone, I found myself logged out and was prompted to sign in again. I attempted to sign in using Emby Connect, but nothing happened—it just returned me to the same login screen.

I then tried the Add Server option, but it couldn’t connect to my server, even though the port it’s running on is correct.

To further troubleshoot, I tested it on my Android phone as well, but the app there also failed to connect.

This is happening outside my home network, and I’ve already tried multiple Wi-Fi networks and cellular data, with no success. What’s strange is that I can access the server just fine via a web browser on all these devices by entering my hostname, and I’m able to stream videos without any issues. That makes this behavior with the Emby app even more confusing.

Is there anything else I can check or try?

[Luke 42077]

Quote

I then tried the Add Server option, but it couldn’t connect to my server, even though the port it’s running on is correct.

Hi, what exactly happened?

[casperr0426 1]

I figured it out. I needed to remove the port in the port section and leave it blank, then it was able to connect just fine to the server.

 

Edit: Let me clarify, this port I am referring to is when I am adding the server where I enter the server address and then below it is a box where I can enter the port. 

Edited May 2, 2025 by casperr0426

[Luke 42077]

What were you entering for the port number?

[casperr0426 1]

2 minutes ago, Luke said:

What were you entering for the port number?

I was entering the port number I configured emby with during setup. I know this is the right port since this is what I use when I access emby in the server. 

[Luke 42077]

When you leave it blank the app will use the default of 8096, so that must be your public facing router port and not whatever you had tried to enter manually.

[casperr0426 1]

7 hours ago, Luke said:

When you leave it blank the app will use the default of 8096, so that must be your public facing router port and not whatever you had tried to enter manually.

Oh then that makes it even more strange. My public port is 8106 for emby as I am using 8096 for jellyfin. I use caddy for reverse proxy.

When I left it blank, it still used 8106 since it loaded the emby not jellyfin. 

[casperr0426 1]

Realized it is not strange at all since in my caddy file, I specified which ports it uses for jellyfin and emby