Jump to content

Roku TV Emby App Unable to Connect Remotely


JulesC
Go to solution Solved by Happy2Play,

Recommended Posts

My son has been connecting remotely to my Emby Server using his Roku TV / Emby App.  He purchased a new Roku TV and know Emby is unable to connect remotely. I've tested the WiFi, all other apps on his Roku TV are connecting as expected, however, Emby fails to connect.  Let me explain:

  1. We typically connect to server manually via Host
  2. The Port is set to 8096 (Note: I've also tried 8920 - neither worked)
  3. When I try to Connect to Server, I receive the following error:

"We're unable to connect to the selected server right now. Please ensure it is running and try again.
-7: Failed to connect to <my.hostname.xxx port 8096: Success"

What's strange is that I'm unable to connect remotely using my iPhone and Laptop with the same Wifi.

I tried the Connectivity Tips, but no success there either. This has been going on for awhile. Any help would be greatly appreciated.

Link to comment
Share on other sites

5 hours ago, JulesC said:

I'm unable to connect remotely using my iPhone and Laptop with the same Wifi.

Hi.  Did you type that correctly?  You are also unable to connect from any other device on the same network?

If so, that would suggest something blocking it on that network.

Link to comment
Share on other sites

1 hour ago, ebr said:

Hi.  Did you type that correctly?  You are also unable to connect from any other device on the same network?

If so, that would suggest something blocking it on that network.

Sorry @ebr, I am ABLE to connect remotely using my iPhone and Laptop with the same WiFi. Just doesn’t make sense why I can’t connect via Roku. I’m sure that I’m overlooking something. 

Link to comment
Share on other sites

Are you trying to connect via https?  If so, what is the origin of your certificate?  The Roku may not trust it.

Link to comment
Share on other sites

3 hours ago, ebr said:

Are you trying to connect via https?  If so, what is the origin of your certificate?  The Roku may not trust it.

@ebr Yes, trying to connect remotely via HTTPS. As for the certificate, using "Let's Encrypt". FYI - I have Emby Server running on a Synology NAS. Like I mentioned prior, I can access Emby on the NAS remotely from my son's home via my iPhone or Laptop via his Wifi.  It was working, not sure what has changed.

Truly appreciate any help I can get to resolve this issue. TIA

 

Link to comment
Share on other sites

Hi.  You will need to update your certificate on your server.  First be sure you are on server version 4.6.7 and then see this topic:

 

Link to comment
Share on other sites

  • 10 months later...

Emby gang, @Luke @ebr

I’m still unable to connect remotely from my son’s Roku TV to my Emby server. See earlier messages from above for the details related to this issue. I have also attached the error I’m receiving when I try to connect using my domain name, which works for my older son and sister-in-law, both using Firesticks. 

I’m still able to connect to my server successfully from my iPhone (cell data disabled) and laptop using the same WiFi remotely, but not their Roku TV’s - they have 2 of them. 
 

It appears to be specific to these Roku TV’s

Any help in resolving this would be greatly appreciated. Thank you. 
 

Julio
 

4C27F490-BEF1-4E9F-B6B7-B2941E12DCB2.jpeg

Link to comment
Share on other sites

Is your son using a VPN that could be interfering with the connection? Are you sure you used the correct server address and port? If this is https, did you include https in the server address?

Link to comment
Share on other sites

@Luke thank you for your response.
My son isn’t using a VPN. Yes, I used the correct address and Port. Yes, this is a SSL connection, so I did use https. 
 

I’m baffled with this remote connection and I have no experience with Roku TV. Is there something else that I need to configure that I’m unaware of?

Appreciate any help to figure this out. Thank you 

Link to comment
Share on other sites

pwhodges

"No route to host" makes me wonder about network issues, such as the IP address/network mask on the Roku not matching other parts of the network. 

Are other apps on the Roku working OK?  This would indicate that my suspicions are unfounded.  (If not, then is there a possibility that you have two devices handing out addresses using DHCP?)

Paul

Link to comment
Share on other sites

pwhodges
2 minutes ago, ebr said:

No route to host would indicate a DNS issue I think.  Have you tried using the IP address?

IP address won't work with https, because the name used must match the certificate.  But the error might change, of course.

Paul

Link to comment
Share on other sites

1 minute ago, pwhodges said:

IP address won't work with https, because the name used must match the certificate

Ah, of course...  but it might be good to know if it works via plain http.

Link to comment
Share on other sites

49 minutes ago, pwhodges said:

"No route to host" makes me wonder about network issues, such as the IP address/network mask on the Roku not matching other parts of the network. 

Are other apps on the Roku working OK?  This would indicate that my suspicions are unfounded.  (If not, then is there a possibility that you have two devices handing out addresses using DHCP?)

Paul

@pwhodges & @ebr thank you for your responses. 
 

Paul, can you help me understand what you mean by: “network issues, such as the IP address/network mask on the Roku not matching other parts of the network.”

Other apps on the Roku are working fine (i.e. Amazon Prime, YouTube TV, etc.). Emby is the only app I’m aware of that isn’t working. 
 

@ebr I tried with http and https and neither worked. I also tried with local and remote Ports

47 minutes ago, ebr said:

Ah, of course...  but it might be good to know if it works via plain http.


Other suggestions? Thank you 

Edited by JulesC
Link to comment
Share on other sites

pwhodges

If the other apps are working fine, then it would seem that the networking (at the sites with the Roku) is OK.  The next thing I think of, but it is truly grasping at straws, is whether one end or other of the link has IPv6...

Beyond that I'm a bit stuck for now (and off to bed!).

Good luck
Paul

Link to comment
Share on other sites

40 minutes ago, pwhodges said:

If the other apps are working fine, then it would seem that the networking (at the sites with the Roku) is OK.  The next thing I think of, but it is truly grasping at straws, is whether one end or other of the link has IPv6...

Beyond that I'm a bit stuck for now (and off to bed!).

Good luck
Paul

@pwhodges thank you. Not sure how this would impact the connectivity. 
 

Has anyone else encountered this issue or have other ideas on how to resolve this issue? Thank you. 

Link to comment
Share on other sites

Apologies. I believe the mistake is you need to use the hostname on your certificate that points to your server as the HOST on the Roku and leave the port blank or 0. When the port is blank or zero it will not be attached to the HOST. Your emby server will correctly forward the request or should then to the correct port and connect. Let us know if this works. Thanks.

Edited by speechles
Link to comment
Share on other sites

6 minutes ago, speechles said:

Apologies. I believe the mistake is you need to use the hostname on your certificate that points to your server as the HOST on the Roku and leave the port blank or 0. When the port is blank or zero it will not be attached to the HOST. Your emby server will correctly forward the request or should then to the correct port and connect. Let us know if this works. Thanks.

@speechles thank you. Just want to ensure I’m following correctly. So on the Roku/Emby connectivity page, I should use…
Host: “my.hostname.xxx” (my domain name)

- Port: 0 (from my experience, blank doesn’t work)

Is this correct? Am I missing anything?

Thank you  

 

Link to comment
Share on other sites

Just now, JulesC said:

@speechles thank you. Just want to ensure I’m following correctly. So on the Roku/Emby connectivity page, I should use…
Host: “my.hostname.xxx” (my domain name)

- Port: 0 (from my experience, blank doesn’t work)

Is this correct? Am I missing anything?

Thank you  

 

Yes. Make sure to use HTTPS on your hostname. Then 0 for the port will omit the port. That should allow it to work.

We have had users with custom domain names use 0 for the port and it solved the problem for them and it should for you too.

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...