Jump to content


Photo

Connecting Roku Emby externally over HTTPS

roku external https firewall

  • Please log in to reply
4 replies to this topic

#1 TheRealGrale OFFLINE  

TheRealGrale

    Newbie

  • Members
  • 4 posts
  • Local time: 02:35 PM

Posted 25 November 2015 - 02:53 AM

Ok so I'm not a network novice, but clearly I am missing something here.  I've searched the forums and have only found mention of using http port 8096 for external connections.  None of the documentation/posts I have seen specifically speak of using https, which I would like to use if possible.

 

The firewall on my 2008r2 server has the proper ports all opened, the exe is also allowed access, and the port forwarding rules are in effect on my modem.  On the web console of EMBY it even reports "Remote Access: https://xxx.xxx.xxx.xxx:8920.

 

Now when I go to my EMBY Roku app, it doesn't matter if I enter https://:xxx.xxx.xxx.xxx or just the IP and then use 8920, the Roku will not connect, it gives the following error:

 

We were unable to connect to this server.  Please make sure it is running and try again.

 

HTTPS works from a web browser, but it will not work from the EMBY Roku, nor the EMBY client for android.

 

 

Now I know all is working on the server/firewall side because if I go back and connect using the IP and use 8096, boom, connects and works both Roku and droid clients.  I am using the latest release of EMBY server, as of this writing, and I have removed and reinstalled the EMBY Roku client just to be sure.

 

Can the roku connect over HTTPS and if so what am I missing?

 

Thanks guys!

 

P.S.  EMBY ROCKS!


Edited by TheRealGrale, 25 November 2015 - 02:55 AM.


#2 legallink OFFLINE  

legallink

    Advanced Member

  • Alpha Testers
  • 1230 posts
  • Local time: 08:35 AM

Posted 25 November 2015 - 06:59 AM

Have you tried using Emby connect?

#3 Vidman OFFLINE  

Vidman

    Advanced Member

  • Alpha Testers
  • 2662 posts
  • Local time: 09:35 PM

Posted 25 November 2015 - 07:04 AM

I believe there is a caveat for https atm that you must use a special kind of certificate

#4 TheRealGrale OFFLINE  

TheRealGrale

    Newbie

  • Members
  • 4 posts
  • Local time: 02:35 PM

Posted 25 November 2015 - 02:48 PM

Have you tried using Emby connect?

 

I have not, are there fee's associated with it and does it use HTTPS?  My goal is to try and be as secure as possible and have only the one needed port open for function.

 

 

I believe there is a caveat for https atm that you must use a special kind of certificate

 

Would make sense considering the error given by IE on the HTTPS side of things.  Do you have more data on this or what resources to refer too?

 

Thanks guys! :D



#5 speechles OFFLINE  

speechles

    Advanced Member

  • App Developer
  • 5582 posts
  • Local time: 05:35 AM

Posted 25 November 2015 - 04:41 PM

The problem will wind up being the stock roku gridscreen (rogridscreen). The images wont work under ssl. So even if you do get this working, you will see what I mean. For ssl to work on roku will require moving away from using rogridscreen and using custom roscreen instead. The move to scene graph will allow this. The home screen and each library screen of the roku app are rendered with rogridscreen.

Sent from my Nexus 7 using Tapatalk





Also tagged with one or more of these keywords: roku, external, https, firewall

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users