Emby Connect issues on FireTV Stick

[WonkoTheSane 11]

Hi all,

a friend of mine is unable to log in to my Emby Server using Emby Connect. I assume that the following server log lines reflect that issue.

Quote

2020-08-05 12:33:21.748 Info HttpServer: WS http://192.168.1.114:8096/embywebsocket?api_key=9066106a34bd4b3a931c34db940e70cb&deviceId=B13D6BA8B1A04D9D9073DAB40484980D. UserAgent: EmbyConWebSocket
2020-08-05 12:33:21.750 Warn SessionWebSocketListener: Unable to determine session based on url: /embywebsocket?api_key=9066106a34bd4b3a931c34db940e70cb&deviceId=B13D6BA8B1A04D9D9073DAB40484980D
2020-08-05 12:33:22.279 Info HttpServer: HTTP GET https://dropkick.argh.org:8920/emby/ScheduledTasks. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0
2020-08-05 12:33:22.279 Info HttpServer: HTTP GET https://dropkick.argh.org:8920/emby/News/Product?StartIndex=0&Limit=4. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0
2020-08-05 12:33:22.283 Info HttpServer: HTTP GET https://dropkick.argh.org:8920/emby/Sessions?ActiveWithinSeconds=300. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0
2020-08-05 12:33:22.284 Info HttpServer: HTTP GET https://dropkick.argh.org:8920/emby/System/Info. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0
2020-08-05 12:33:22.286 Error HttpServer: Error in ProcessAccept
*** Error Report ***
Version: 4.4.3.0
Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3
Operating system: Unix 4.19.107.0
64-Bit OS: True
64-Bit Process: True
User Interactive: True
Runtime: file:///system/System.Private.CoreLib.dll
System.Environment.Version: 3.1.2
Processor count: 4
Program data path: /config
Application directory: /system
System.IO.IOException: System.IO.IOException: Authentication failed because the remote party has closed the transport stream.
at System.Net.Security.SslStream.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.ProcessAuthentication(LazyAsyncResult lazyResult, CancellationToken cancellationToken)

Any help in solving this is appreciated.

 

Best regards!

 

embyserver.zip

[Carlo 4330]

What I would try first is to remove the connect username from the user on your system and save the record.

Then add back the Emby connect username and save the record.

Have the user check his email and click on the link generated for Emby Connect.

Then try logging into your server again.

[WonkoTheSane 11]

Thanks for your reply. We tried that, still no joy. All my friend sees in the Emby Android TV App is depicted in the attached screenshot.

[ebr 14913]

Hi.  After you did that process on the server, did your friend log out of Connect (that red button there) and then re-do the PIN process?

[WonkoTheSane 11]

Hi,

we tried that and ended up on a screen stating that my server was unreachable. When I repeated the PIN process on my phone with WIFI off, it worked without a hitch.

Anything else we can try to sort this out.

[Carlo 4330]

Hello,

Got a question for you.  Do you have any other users that are presently accessing your server remotely?  Can you access your Emby Server remotely?

Thanks

[WonkoTheSane 11]

Yes, I do. The same user can access my server remotely using Emby Web with manual login.

[Carlo 4330]

Can you have them try from a web browser going to app.emby.media and trying to login in using connect that way.

Let us know how this works.

[Luke 37066]

Make sure it's http://app.emby.media if your server doesn't have ssl setup.

[Carlo 4330]

Can this be handled on the app/website side at all Luke?

What would be the correct way to know if you have multiple servers you can connect to with some using SSL and some not?

How do the clients with Emby Connect built in handle the distinction?

[WonkoTheSane 11]

44 minutes ago, Luke said:

Make sure it's http://app.emby.media if your server doesn't have ssl setup.

ssl setup is in place. It works for me, waiting for feedback from my friend.

[WonkoTheSane 11]

My friend is able to connect to my server via app.emby.media.

[Luke 37066]

Does your emby server dashboard display the correct remote address, and is that address https?

[WonkoTheSane 11]

Well, not entirely. I've got a reverse proxy involved and configured the secure connection mode in Emby as such. What I see in the dashboard for remote connections is https://my.domain.org:443. The actual address to directly connect to my Emby server is https://my.domain.org/emby. Could that be a problem for the Android TV App?

 

Thanks for your time, Luke!

 

[Carlo 4330]

Hi,

It sounds like you're controlling access using rewrites which you need to be careful with.

What happens when you open a browser and go to https://my.domain.org/web/index.html remotely?

Now try this.  Go on the left menu go to NETWORKS and scroll down to the "External Domain" field and enter

my.domain.org/emby

Now try again remotely in a browser using https://my.domain.org/emby/web/index.html and tell us what happens?

 

[ebr 14913]

4 hours ago, WonkoTheSane said:

Well, not entirely. I've got a reverse proxy involved and configured the secure connection mode in Emby as such. What I see in the dashboard for remote connections is https://my.domain.org:443. The actual address to directly connect to my Emby server is https://my.domain.org/emby. Could that be a problem for the Android TV App?

 

Thanks for your time, Luke!

 

Yes, that would be a problem.  The app is going to try and connect using the address the server tells it to.

[WonkoTheSane 11]

8 hours ago, cayars said:

Hi,

It sounds like you're controlling access using rewrites which you need to be careful with.

What happens when you open a browser and go to https://my.domain.org/web/index.html remotely?

Now try this.  Go on the left menu go to NETWORKS and scroll down to the "External Domain" field and enter

my.domain.org/emby

Now try again remotely in a browser using https://my.domain.org/emby/web/index.html and tell us what happens?

 

Hi,

the first link goes nowhere since there is no subfolder forwarding in place for /web. The second one works with and without appending /emby to "External Domain".

Could appending "/emby" to "External Domain" fix the issue with the Android TV client app?

Thanks for your help!

 

 

 

[Carlo 4330]

That's what I was getting at.  Give that a shot to see if it will work for you.

If that doesn't work then instead of my.domain.org you could use emby.domain.org specifically for Emby with it's own A record and my.domain.org for any other thing running through your proxy.

 

[WonkoTheSane 11]

Thanks for your input.
Waiting for my friend to test this at home. I"m a bit sceptical about this working since the external link I now see Iin the dashboard is malformed. It's https://my.domain.org/emby::443.

I'll report back on how this turns out.

[Luke 37066]

22 hours ago, WonkoTheSane said:

Well, not entirely. I've got a reverse proxy involved and configured the secure connection mode in Emby as such. What I see in the dashboard for remote connections is https://my.domain.org:443. The actual address to directly connect to my Emby server is https://my.domain.org/emby. Could that be a problem for the Android TV App?

 

Thanks for your time, Luke!

 

If 443 is your default https port then it should be fine. You'll need to configure the network settings of the server to ensure the server dashboard displays the correct remote address.

[WonkoTheSane 11]

Hi,

unfortunately, my friend is still unable to connect to my server from his FireTV stick using Emby connect.

He's doing the PIN procedure, selects my server and then gets to a server unreachable screen. Is there anything

else we can to to narrow down the source of this issue?

[Luke 37066]

13 minutes ago, WonkoTheSane said:

Hi,

unfortunately, my friend is still unable to connect to my server from his FireTV stick using Emby connect.

He's doing the PIN procedure, selects my server and then gets to a server unreachable screen. Is there anything

else we can to to narrow down the source of this issue?

Before you have your friend connect, have you personally tested a remote connection to your server?

[ebr 14913]

Does the dashboard WAN address now show the correct address to reach your server from the outside?

[WonkoTheSane 11]

The remote connection works fine with Emby Web manual connect for him and for me. As I stated earlier,

the WAN address displayed in the dashboard now looks like this: https://my.domain.org/emby:443.

 

[ebr 14913]

1 minute ago, WonkoTheSane said:

the WAN address displayed in the dashboard now looks like this: https://my.domain.org/emby:443

And is that the exact address you enter via manual connect in the web?