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 43047]

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 5 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 2 hours ago by Beta8088Proto

[Luke 43047]

If you're getting a wrong password error then that probably means you are connected, but just entering the wrong password.

Can you please show a screenshot of the entire user interface when this happens? Thanks.

[Luke 43047]

Quote

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.

I realize this might not be your actual issue, but just as a rule of thumb, port forwarding will be more reliable than UPNP. If you have the patience it's in your best interests to revisit it and give it another try.

Remote access is something that requires occasional maintenance. You might think nothing is changing, but everything is changing around you. ISP's changing their rules, a router software update could break or disable UPNP, operating system updates, etc.  Setting up a static LAN IP and preferring port forwarding over UPNP are two ways to reduce your ongoing maintenance of your remote access.

And as Ebr said, using Emby Connect does not escape you from this. It just saves you the trouble of having to remember your server ip address.

[Beta8088_Proto 0]

8 minutes ago, Luke said:

If you're getting a wrong password error then that probably means you are connected, but just entering the wrong password.

Can you please show a screenshot of the entire user interface when this happens? Thanks.

that's the thing though: I am entering the correct password, and I have been changing the access password to ensure it was correct over and over and over again, but yes, it is indeed auth that is broken, on the PIN screen, what happens is I put in my Emby Connect credentials and the PIN the client gives me, it says the PIN is good, and then I hit next and... nothing happens, when on mobile, I put in the correct username and password, and it just says that my username or password is wrong (and yes, I am absolutely certain it's correct).

So I'm certain something on Emby Connect's side has broken auth.

Sorry for not having images, I just got back into my own home on my own network, where none of this is a problem and on Android (the only way I can simulate WAN in my house) it doesn't get that far, it just lies that my valid password is wrong.

In relation to port forwarding... I was literally up till 3 AM following every single guide and solution presented. Absolutely none of it worked. My setup can only work with Emby Connect. I don't know what's different with it, but Emby Connect can connect through WAN, but its auth is broken, and the WAN address just refuses to connect (different error).

Edited 47 minutes ago by Beta8088_Proto

[Luke 43047]

Where are you changing the password?

[Beta8088_Proto 0]

1 minute ago, Luke said:

Where are you changing the password?

The server. And I tried it six times.

[Luke 43047]

2 minutes ago, Beta8088_Proto said:

The server. And I tried it six times.

OK since you say server, but you also say PIN, you may be confusing the difference between Emby Connect credentials and the private user credentials on your server. This is why I asked for this:

Quote

Can you please show a screenshot of the entire user interface when this happens? Thanks.

My guess is that you are entering the credentials for one on the login screen for the other.

[ebr 16681]

45 minutes ago, Beta8088_Proto said:

I put in my Emby Connect credentials and the PIN the client gives me, it says the PIN is good

Hi.  Does it say exactly "PIN Confirmed"?

If so, then the authorization succeeded and, BTW, the password you entered here is different from the one you control in your server. 

46 minutes ago, Beta8088_Proto said:

I hit next and... nothing happens,

How long have you waited?  And please watch the screen for 60 seconds.  My guess is that your server (as defined by your dashboard) is unreachable and the connection is timing out but this would take up to 60 minutes for it to time out and give you a message.

Would you mind PMing one of us the exact address shown on your server for WAN address?