UPNP setup of Emby Server has suddenly stopped working remotely

[Beta8088_Proto 0]

I can access Emby locally, but ONLY locally. I had a remote access solution through Emby Connect working, however, now Emby Connect continuously hallucinates a "wrong password" (which I know factually is the correct one, and yes, I have tried BOTH the Emby Connect and the local password, neither work, even after half a dozen password resets to make sure, deleting the account in question, and then recreating the account with another known password).

Emby Connect is out of the question, and my Remote Access address has NEVER worked correctly (it's running HTTP, and yes, I have made sure it's not HTTPS), and I have UPnP enabled on BOTH my router AND server.

I have tried manually port forwarding with no luck.

What do I need to do to get Emby Connect working like it used to, so I can actually use this outside my own home?

[Abobader 3515]

Hello Beta8088_Proto,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[Luke 43045]

Hi, how did you setup port forwarding in your router?

[Beta8088_Proto 0]

As stated previously, I have UPnP enabled on both Emby Server and my router, which, up until yesterday, worked perfectly fine with Emby Connect. Manual port forwarding (no matter what settings or guides I have followed) has never once worked for WAN access for me, no matter what I've done, so I have never utilized it.

Edited 4 hours ago by Beta8088_Proto

[Beta8088Proto 0]

Additional detail: Connecting with a PIN on Emby Connect still does not work. I provided Emby Connect with the correct PIN and hitting "NEXT" does nothing. This is almost certainly Emby Connect not working.

[ebr 16681]

1 hour ago, Beta8088_Proto said:

As stated previously, I have UPnP enabled on both Emby Server and my router, which, up until yesterday, worked perfectly fine with Emby Connect. Manual port forwarding (no matter what settings or guides I have followed) has never once worked for WAN access for me, no matter what I've done, so I have never utilized it.

Hi.  All UPnP does is automatically create the port forwarding rules in your router.  Whether created that way or manually by you, that is how access to your server inside your network is achieved.

Also, Emby Connect is just an easy way to arrive at your server.  Technically, it is doing the exact same thing as you manually connecting to it.

If you run the troubleshooting steps here: Connecting from Client Apps which ones succeed and which fail?

[Beta8088Proto 0]

2 minutes ago, ebr said:

Hi.  All UPnP does is automatically create the port forwarding rules in your router.  Whether created that way or manually by you, that is how access to your server inside your network is achieved.

Also, Emby Connect is just an easy way to arrive at your server.  Technically, it is doing the exact same thing as you manually connecting to it.

If you run the troubleshooting steps here: Connecting from Client Apps which ones succeed and which fail?

None have succeeded historically or currently for WAN access (as previously stated) and/or are not practical to accomplish and/or are already set as per the suggestions. And I can access over LAN just fine, and Emby connect worked fine for over a year until yesterday, when it suddenly quit working.

[ebr 16681]

1 hour ago, Beta8088Proto said:

None have succeeded historically or currently for WAN access

 

1 hour ago, Beta8088Proto said:

Emby connect worked fine for over a year

If those two statements are true, then you were not testing properly because Emby Connect is simply using the information from your server to connect directly to it.

Were you testing with the WAN address shown on your Emby dashboard?

[Beta8088Proto 0]

4 minutes ago, ebr said:

 

If those two statements are true, then you were not testing properly because Emby Connect is simply using the information from your server to connect directly to it.

Were you testing with the WAN address shown on your Emby dashboard?

I was using app.emby.media and Emby Connect because using the WAN address directly never once worked, the only way any of this would work was when Emby Connect was used. And yes, I do mean "never". The WAN address and port listed by the server have NEVER resulted in a successful connection, but Emby Server, up until yesterday, somehow managed to connect remotely, despite using the WAN address directly never once working.

Edited 53 minutes ago by Beta8088Proto