Jump to content


Photo

OSMC Cannot click the sign in button in Emby addon


Best Answer Angelblue05 , 23 May 2019 - 03:30 PM

@rterblanche

 

Your device name is indeed missing from the header as Luke said. In the add-on settings > Do you have user alternate device name enabled? If not, does your Kodi have a name assigned under kodi settings > services > general > Device name? If not either fill one there, or enable use an alternate device name in the add-on settings. Restart Kodi. That should hopefully get you going.

 

I will patch this to make sure this is not a possibility in the future.

Go to the full post


  • This topic is locked This topic is locked
22 replies to this topic

#1 rterblanche OFFLINE  

rterblanche

    Member

  • Members
  • 22 posts
  • Local time: 02:27 AM

Posted 22 May 2019 - 06:45 AM

When trying to add a connection to my emby server for some reason I cannot click the login button or

it's being click but there's an error I don't get.

 

I am running the latest release osmc version with the latest betas of Emby server and Kodi.

 

Hopefully the log has some info in it : https://paste.osmc.tv/nimefutacu

 

I did a total reinstall from scratch of OSMC on a Vivo 4k.

 

 



#2 sualfred OFFLINE  

sualfred

    The Embuary guy

  • Developers
  • 1674 posts
  • Local time: 02:27 AM
  • LocationGermany

Posted 22 May 2019 - 06:58 AM

Are you running Pi-hole or any other blocker in your network at home?

Because raw.githubusercontent.com is blocked.

 

If yes, please whitelist raw.githubusercontent.com and all other *.github.com addresses.



#3 rterblanche OFFLINE  

rterblanche

    Member

  • Members
  • 22 posts
  • Local time: 02:27 AM

Posted 22 May 2019 - 07:28 AM

Ai. Totally forgot about that.

Will have to remember to always first disable it in the future when having any problems.

Must be newly added to the blocked list. Was fine till sometime last week.

Thanks



Sent from my Pixel 2 XL using Tapatalk

#4 rterblanche OFFLINE  

rterblanche

    Member

  • Members
  • 22 posts
  • Local time: 02:27 AM

Posted 22 May 2019 - 12:24 PM

Looks like the pihole wasn't the problem. Still getting and error when logging in.

Full log : https://paste.osmc.tv/sipaleboya

2019-05-22 17:52:12.352 T:3555713760 NOTICE: Emby.emby.core.http -> ERROR:: 500 Server Error: Internal Server Error for url: http://192.168.1.103...henticateByName 2019-05-22 17:52:12.353 T:3555713760 NOTICE: Emby.emby.core.http -> ERROR:: --[ 500 response ] 500 Server Error: Internal Server Error for url: http://192.168.1.103...henticateByName 2019-05-22 17:52:12.357 T:3555713760 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<-- - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS! Error Type: <type 'exceptions.TypeError'> Error Contents: 'NoneType' object has no attribute '__getitem__' Traceback (most recent call last): File "/home/osmc/.kodi/addons/plugin.video.emby/resources/lib/dialogs/loginmanual.py", line 86, in onClick elif self._login(user, password): File "/home/osmc/.kodi/addons/plugin.video.emby/resources/lib/dialogs/loginmanual.py", line 124, in _login result = self.connect_manager['login'](server, username, password) File "/home/osmc/.kodi/addons/plugin.video.emby/libraries/emby/core/connection_manager.py", line 220, in login self._on_authenticated(result, options) File "/home/osmc/.kodi/addons/plugin.video.emby/libraries/emby/core/connection_manager.py", line 825, in _on_authenticated self.config['auth.user_id'] = result['User']['Id'] TypeError: 'NoneType' object has no attribute '__getitem__' -->End of Python script error report<--

Sent from my Pixel 2 XL using Tapatalk

#5 rterblanche OFFLINE  

rterblanche

    Member

  • Members
  • 22 posts
  • Local time: 02:27 AM

Posted 22 May 2019 - 12:35 PM

Some more info.

I have a raspberry Pi on the same network running libreelec and have no problems.

I am thinking it might be osmc but not sure what to post on the osmc forums.

Sent from my Pixel 2 XL using Tapatalk

#6 Angelblue05 OFFLINE  

Angelblue05

    Advanced Member

  • Developers
  • 12580 posts
  • Local time: 07:27 PM

Posted 22 May 2019 - 01:20 PM

Pi hole was definitely a problem. But now it’s trying to authenticate you and it ends with a 500 internal server error. Can you repeat the test and provide the server log or provide your server log from that time? Thanks.

Edited by Angelblue05, 22 May 2019 - 01:21 PM.


#7 rterblanche OFFLINE  

rterblanche

    Member

  • Members
  • 22 posts
  • Local time: 02:27 AM

Posted 22 May 2019 - 02:09 PM

Hope this help. Logged in with debugging enabled between 19h50-20h00Attached File  Log.txt   7.78MB   3 downloads

Sent from my Pixel 2 XL using Tapatalk

#8 Angelblue05 OFFLINE  

Angelblue05

    Advanced Member

  • Developers
  • 12580 posts
  • Local time: 07:27 PM

Posted 22 May 2019 - 02:34 PM

@Luke

 

Check the previous post, the server log is throwing SQLite errors (Search for response 500 authenticatebyname) trying to create a new access token for a user successfully authenticated it seems.


Edited by Angelblue05, 22 May 2019 - 02:34 PM.


#9 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 138256 posts
  • Local time: 08:27 PM

Posted 22 May 2019 - 02:49 PM

@Luke

 

Check the previous post, the server log is throwing SQLite errors (Search for response 500 authenticatebyname) trying to create a new access token for a user successfully authenticated it seems.

 

Is the Authentication header not being supplied on the request with the device name?


  • Angelblue05 likes this

#10 Angelblue05 OFFLINE  

Angelblue05

    Advanced Member

  • Developers
  • 12580 posts
  • Local time: 07:27 PM

Posted 22 May 2019 - 03:50 PM

Thanks Luke. I will get that confirmed.

 

@rterblanche

 

In the add-on settings > advanced > logging set to Debug/Ok. Restart Kodi. Wait a few and post that Kodi log, thank you. I want to confirm we are sending all the info to your server.


Edited by Angelblue05, 22 May 2019 - 04:04 PM.


#11 rterblanche OFFLINE  

rterblanche

    Member

  • Members
  • 22 posts
  • Local time: 02:27 AM

Posted 23 May 2019 - 02:25 AM

Sent from my Pixel 2 XL using Tapatalk


Edited by Angelblue05, 23 May 2019 - 03:26 PM.


#12 Angelblue05 OFFLINE  

Angelblue05

    Advanced Member

  • Developers
  • 12580 posts
  • Local time: 07:27 PM

Posted 23 May 2019 - 02:49 AM

Hum, you didn't enable logging set to debug in the add-on settings like I requested?



#13 rterblanche OFFLINE  

rterblanche

    Member

  • Members
  • 22 posts
  • Local time: 02:27 AM

Posted 23 May 2019 - 02:52 AM

Sorry. Didn't do it on the add-on.

Didn't read correctly. Unfortunately will only be able to provide a log when I get home again

Sent from my Pixel 2 XL using Tapatalk
  • Angelblue05 likes this

#14 rterblanche OFFLINE  

rterblanche

    Member

  • Members
  • 22 posts
  • Local time: 02:27 AM

Posted 23 May 2019 - 11:31 AM

Let's hope I did it right this time.

Sent from my Pixel 2 XL using Tapatalk


Edited by Angelblue05, 23 May 2019 - 03:26 PM.

  • Angelblue05 likes this

#15 Angelblue05 OFFLINE  

Angelblue05

    Advanced Member

  • Developers
  • 12580 posts
  • Local time: 07:27 PM

Posted 23 May 2019 - 12:53 PM

Let's hope I did it right this time.



Sent from my Pixel 2 XL using Tapatalk


Yes thank you. For future ref, Kodi debug is not needed. Only the add-on’s. I will keep you posted.


Edited by Angelblue05, 23 May 2019 - 03:25 PM.


#16 Angelblue05 OFFLINE  

Angelblue05

    Advanced Member

  • Developers
  • 12580 posts
  • Local time: 07:27 PM

Posted 23 May 2019 - 03:30 PM   Best Answer

@rterblanche

 

Your device name is indeed missing from the header as Luke said. In the add-on settings > Do you have user alternate device name enabled? If not, does your Kodi have a name assigned under kodi settings > services > general > Device name? If not either fill one there, or enable use an alternate device name in the add-on settings. Restart Kodi. That should hopefully get you going.

 

I will patch this to make sure this is not a possibility in the future.


Edited by Angelblue05, 23 May 2019 - 03:34 PM.


#17 rterblanche OFFLINE  

rterblanche

    Member

  • Members
  • 22 posts
  • Local time: 02:27 AM

Posted 24 May 2019 - 03:09 AM

Strange. My hostname/devicename is correct everywhere. I check in the hostname file.

 

I just updated the alternate name in the addon and everything is working again.

 

Thanks


  • Angelblue05 likes this

#18 Angelblue05 OFFLINE  

Angelblue05

    Advanced Member

  • Developers
  • 12580 posts
  • Local time: 07:27 PM

Posted 24 May 2019 - 03:38 AM

It's not your hostname.

 

Does your Kodi have a name assigned under kodi settings > services > general > Device name? Or is that field empty? That's all there is to the issue you faced.



#19 rterblanche OFFLINE  

rterblanche

    Member

  • Members
  • 22 posts
  • Local time: 02:27 AM

Posted 24 May 2019 - 03:48 AM

Ja all that was filled in. Maybe to keep me sane I might reinstall and try reproduce the error. Very interested in how it happened from a clean install.

But at least now I know how to fix and the add-on checks for it.

Thanks

Sent from my Pixel 2 XL using Tapatalk
  • Angelblue05 likes this

#20 Angelblue05 OFFLINE  

Angelblue05

    Advanced Member

  • Developers
  • 12580 posts
  • Local time: 07:27 PM

Posted 24 May 2019 - 03:55 AM

Interesting, well glad it is resolved now :)






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users