Jump to content

roku won't connect to server


bugz000
Go to solution Solved by bugz000,

Recommended Posts

my SO has roku on their tv and i mentioned she could hook that to my emby server
but upon trying it seems there's some fault, we tried a variety of things including:

 

https://ip		
443

https://ip/		
443

http://ip		
443

https://ip/		
443

http://domain.com/	
443

http://domain.com	
443

https://domain.com	
443

https://domain.com/	
443

https://domain.com/emby	
443

http://domain.com/emby	
443

https://domain.com/emby/
443

http://domain.com/emby/	
443

https://ip		
8096

https://ip/		
8096

http://ip		
8096

https://ip/		
8096

http://domain.com/	
8096

http://domain.com	
8096

https://domain.com	
8096

https://domain.com/	
8096

https://domain.com/emby	
8096

http://domain.com/emby	
8096

https://domain.com/emby/
8096

http://domain.com/emby/	
8096

https://ip		
80

https://ip/
80

http://ip
80

https://ip/
80

http://domain.com/
80

http://domain.com
80

https://domain.com
80

https://domain.com/
80

https://domain.com/emby
80

http://domain.com/emby
80

https://domain.com/emby/
80

http://domain.com/emby/
80

https://ip		
0

https://ip/
0

http://ip
0

https://ip/
0

http://domain.com/
0

http://domain.com
0

https://domain.com
0

https://domain.com/
0

https://domain.com/emby
0

http://domain.com/emby
0

https://domain.com/emby/
0

http://domain.com/emby/
0

https://ip		
00000

https://ip/
00000

http://ip
00000

https://ip/
00000

http://domain.com/
00000

http://domain.com
00000

https://domain.com
00000

https://domain.com/
00000

https://domain.com/emby
00000

http://domain.com/emby
00000

https://domain.com/emby/
00000

http://domain.com/emby/
00000


a variety of the above work just fine in browser, some ofcourse have ssl errors etc which is expected
so i suspected perhaps an issue on the server so i ensured emby saw the remote(WAN) access on the dashboard showed at least one that worked fine in browser
this choice was http://domain.com:8096

port 443 and 80 are forwarded to my reverse proxy (nginxPM) and 8096 is forwarded direct to emby (installed using swizzin) 

swizzin ofcourse having it's own reverse proxy, through browser it routes through BOTH reverse proxies just fine, connecting locally to the swizzin RP works fine, connecting remotely through direct to emby through 8096 works just fine - i can't see any reason this won't work
it is NOT hosted using a subdomain, but by port 8096 this shouldn't be an issue, but otherwise it is hosted under /emby/ for ports 80 and 443 - port 8096 skips all reverse proxies and forwards right through to emby, forwarded TCP/UDP

nothing i try works, roku times out - yet her cellphone, her mothers cellphone and both laptops connect just fine using a variety of both my domain names, ip addr and other

sensing i must be doing something monumentally stupid i resolved to try emby connect - let the emby servers do the connecting bit for me,  so she made an account - i added it to her profile, she logged in using the roku, did the code, got authenticated, she could see my emby server listed and had the option to connect under her user but it sat loading forever

we verified she was indeed connected to the internet with the roku, signal was "great"
i do not want to handle SSL certs direct with emby, that's why i let nginxPM handle ssl certs for me, but i tried toggling the the "handled by reverse proxy" option in the emby settings to no avail, but this should not be a problem assuming emby is listening on http and NOT https (ssl disabled) and port 8096 forwarded direct to it and she tries direct IP no domain right?

i've come to a conclusion there must be a problem with the roku app which is a great shame if so - but i'm willing to try many more things if someone has any other ideas

to be clear i see absolutely no activity on the dashboard, no authentication failure, no recent activity on her account, she cannot get through from the roku, as far as i can see, from the roku, nothing gets as far as touching the emby server which is very strange as it works on literally everything else, both remote and local, both mobile and wifi, both laptop and cellphone, both domains and ip, both reverse proxied and direct, it's very strange and i've run out of things to try

r4o1.png

Edited by bugz000
more info added
Link to comment
Share on other sites

Have you seen this thread? Your answer is here likely. The Roku is one of the most strict and secure clients as far as connections allowed.

Edited by speechles
Link to comment
Share on other sites

10 minutes ago, speechles said:

Have you seen this thread? Your answer is here likely.

yes through trying to debug this i did come by this thread, though it's of little relevance as the initial reverse proxying is handled by swizzin, the external reverse proxying is handled by nginxPM, my particular setup forwards connections direct to emby on the container (via 443->8096) and it works just fine in browser

regardless of this - connecting directly via http://domain.com:8096/ routes direct to emby, skipping all reverse proxies, (and ssl for that matter)
this is what emby expects to use for WAN access (as shown on the dashboard) - so there is zero reverse proxying present when using that endpoint
this also works fine in browser 

we did also try http://ip:8096/ to be safe, and this also worked fine in browser, but not roku, as far as i can see there's no reason this shouldn't be working right?

Edited by bugz000
Link to comment
Share on other sites

Did you try using that on your Roku? Ditch the HTTPs and use HTTP instead?

Link to comment
Share on other sites

1 minute ago, speechles said:

Did you try using that on your Roku? Ditch the HTTPs and use HTTP instead?

yes, i do not want to handle https direct within emby, i let my reverse proxies handle that - but for direct connection (8096) i use HTTP not HTTPS, we have tried via domain and ip to be safe - neither work on the roku, but both work on the browser, infact posting the HTTP://domain.com:8096/ url on discord shows the emby metadata which further confirms it should be working 😕

8fJP.png

Edited by bugz000
Link to comment
Share on other sites

In the Roku app you want to choose "Clear settings" from the user screen to start the application in a pure state like it was freshly installed on that Roku.

When the app restarts choose "Manual connection" instead of using Emby connect and the PIN.

Enter the WAN address as HOST/PORT in the Roku app. The connect and wait. It shouldn't just endlessly spin, it should eventually timeout or thrown up an error. If it endlessly spins the routing is broken somewhere.

Link to comment
Share on other sites

Just now, speechles said:

In the Roku app you want to choose "Clear settings" from the user screen to start the application in a pure state like it was freshly installed on that Roku.

When the app restarts choose "Manual connection" instead of using Emby connect and the PIN.

Enter the WAN address as HOST/PORT in the Roku app. The connect and wait. It shouldn't just endlessly spin, it should eventually timeout or thrown up an error. If it endlessly spins the routing is broken somewhere.

to be absolutely clear, that is
HOST box :  http://domain.com/ 
PORT box:  8096

because we have tried this before, but not without clearing the settings, she is at work currently but we can try when she gets home in a couple hours 

mEVi.png

Link to comment
Share on other sites

5 minutes ago, bugz000 said:

to be absolutely clear, that is
HOST box :  http://domain.com/ 
PORT box:  8096

Yep. That exactly. The spinner should start to spin after choosing Connect to Server.

If it spins indefinitely something is definitely wrong somewhere. It should reach your server.

If it ends up with an error screen it should provide some context of what is up with that Roku.

Edited by speechles
Link to comment
Share on other sites

  • Solution
3 hours ago, speechles said:

Yep. That exactly. The spinner should start to spin after choosing Connect to Server.

If it spins indefinitely something is definitely wrong somewhere. It should reach your server.

If it ends up with an error screen it should provide some context of what is up with that Roku.

we're trying this now and it is timing out, but i just got her to open http://domain.com:8096/ in browser and it resolved just ...

nevermind, she managed to get herself blacklisted on my network and it was actively rejecting packets from her ip, all other connection tests she was using her 4g not wifi... 

easy fix, though there's a sizeable dent in my pride 😅

thankyou and apologies for your time regardless haha

io7s.png

  • Thanks 1
Link to comment
Share on other sites

  • 8 months later...
Notryt01

I cant get my roku tv to connect to emby either... works on other devices.. the  FYI I have never gotten emby connect to work

 

Link to comment
Share on other sites

1 hour ago, Notryt01 said:

I cant get my roku tv to connect to emby either... works on other devices.. the  FYI I have never gotten emby connect to work

 

Hi.  Please open a new topic with details since this was solved.  Thanks.

 

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...