Just got update 1.1.50 - Now can't reach Server!

[Rew452 15]

Come on folks everything was working fine, until this update on my SATV.

 

This make 3 versions which has whacked it in just over week.

 

Rew

[bluemonkey07 590]

Well you are on beta

[Angelblue05 4132]

It is beta. Thank you for helping testing. Can you please post your kodi log: http://emby.media/community/index.php?/topic/17599-how-to-report-a-problem/

 

Thank you

[Rew452 15]

ID = pxodterms

 

One from cold start of kodi  http://xbmclogs.com/p7kdevxfx

Edited October 18, 2015 by Rew452

[Angelblue05 4132]

ID = pxodterms

 

If that's supposed to be the id for the debug log, it does not work.

http://xbmclogs.com/show.php?id=pxodterms

Duh, it doesn't need the id=

Edited October 18, 2015 by Angelblue05

[Rew452 15]

sorry got my systems confused. what directory on android to find log?

[Angelblue05 4132]

@@Rew452

 

Everything you need to know is right here: http://emby.media/community/index.php?/topic/17599-how-to-report-a-problem/

I am linking it back to you because you didn't enable the add-on debug, and you enabled Kodi debug. The android directory is also provide in the same post.

 

Anyway, I don't think it's really an add-on issue because nothing changed in that area for a really long time. Are you able to access your server from the address in your log? Do you really use port 8096 with https? Default is 8920.

Server unreachable at: https://xxx.xxx.x.xxx:8096/mediabrowser 

[Rew452 15]

Server working fine on WMC7. Moved to SATV opened Kodi and Emby was immediately updated from .49 to .50 and it complained about Emby Server unavailable. Give a few minutes and I will get logs over.

 

I even restarted SATV-made no difference.

Edited October 18, 2015 by Rew452

[Angelblue05 4132]

Ok so you use port 8096 with https? I ask because it fills it in by default, and it's easy to forget to change it if you use https.

[Rew452 15]

It is that have never changed it

[Rew452 15]

version .47 and .48 did the same thing .49 worked fine

[Angelblue05 4132]

I will tell you that I've not had any connectivity issues, ever. Nothing has changed in that area for a really long time. It's the same login process as stable version. Anyone else having this issue?

 

Do you get the same problem if you use http instead of https? Let me know, thanks.

Edited October 18, 2015 by Angelblue05

[Rew452 15]

if I uncheck HTTPS everything again works.

[Angelblue05 4132]

Ok, next step. In your browser, if you enter the address with https://xxx.xxx.x.xxx:8096/mediabrowser does it reach your server?

[Rew452 15]

Yes this is how I normally check my server settings and movies

[Rew452 15]

Scratch that using exactly what you posted and subbing in my ip I get SSL Connection error. 

 

Normally I used http://xxx.xxx.x.xxx:8096/web/index.html

[Angelblue05 4132]

Ok, so now we are getting somewhere. Check your https set up. What options are you using for https? Go to your emby dashboard > advanced > hosting.

[Rew452 15]

is this what you want?

 

•  
  Local https port number: 8920
   

   
   
  The tcp port number that Emby's https server should bind to.
•  
  Public https port number:8920
   

   
   
  The public port number that should be mapped to the local https port.

[Angelblue05 4132]

Perfect, see the port number for https is 8920, not 8096. So your setup in the add-on needs to be 1) http://x:8096 or 2) https://x:8920   to test, you can try to access your server with https://xxx.xxx.x.xxx:8920/mediabrowser make sure the port number is open.

 

Then you should have things working again. Turns out it was not an issue with the add-on at all.

Edited October 18, 2015 by Angelblue05

[Rew452 15]

Using chrome it does not connect on port 8920.

Ok, any idea on how to open that port for Emby on WHS 2011?

[Angelblue05 4132]

Sorry I don't. It is worth asking in the server section of the forums. I'm sure other users can help you with that.