Jump to content

Unable to connect after add-on update


gevarghe
 Share

Recommended Posts

gevarghe

Hi, I updated the emby nextgen add-on when prompted and now can connect at all anymore to the server.

The server is fine and can connect via my phone app.

When I enter my credentials it briefly shows the welcome message and then shows the select server window again and no login is shown in the add-on settings.

Stuff I've tried:

Reinstalled the add-on from both stable and beta repos. Same result

Reinstalled kodi. Same result.

What else can I try? I couldn't find a solution in the forum. TiA!

Onn TV box running kodi 19.3

 

Link to comment
Share on other sites

quickmic

I need a kodi.log for review. Must be special to you use case.

Edited by quickmic
Link to comment
Share on other sites

melkalehun

Hello,

I had the same problem as @gevarghe, emby-next-gen plugin stopped working after update to version 6.2.12. Tried with 6.2.13 and 7.0.0-501, same thing. I didn't update anything else before it stopped working.

At first I couldn't play the files, so I went into the plugin settings and I could not connect to server (when clicking on the button, the popup just closes and I get an error). Looked a bit more at logs and apparently, the advancedsettings.xml was malformed, so I removed it and after a few kodi reboots, I can connect again.

I attached some infos and the kodi.log and advancedsettings.xml that was causing my problems if it can help.

Thanks for the great plugin !

Quote

kodi --version

19.1 Debian package version: 2:19.1+dfsg2-2+deb11u1 Media Center Kodi from Debian

Copyright (C) 2005-2021 Team Kodi from Debian - http://kodi.tv

Quote

uname -a

Linux my-server 5.10.0-12-amd64 #1 SMP Debian 5.10.103-1 (2022-03-07) x86_64 GNU/Linux

Quote

emby version 4.6.7 running in linuxserver/emby container

 

kodi.log advancedsettings.xml

  • Thanks 1
Link to comment
Share on other sites

quickmic

Thanks, at least the header is missing in the xml.

This one: <?xml version='1.0' encoding='UTF-8'?>
 

Should look like that:

<?xml version='1.0' encoding='UTF-8'?>
<advancedsettings>
    <network>
        <curlclienttimeout>120</curlclienttimeout>
        <curllowspeedtime>120</curllowspeedtime>
        <curlkeepaliveinterval>0</curlkeepaliveinterval>
        <disablehttp2>false</disablehttp2>
    </network>
</advancedsettings>

I'll check if there is another issue with the advancedsettings.xml

Edited by quickmic
Link to comment
Share on other sites

melkalehun

Yes, after removing the xml and rebooting kodi, emby-next-gen created a new one with those infos inside.

Link to comment
Share on other sites

gevarghe
Posted (edited)

kodi.logHi... Was tied up last few days. Tried deleting the advancedsettings.xml but didn't work for me after the reboot.

@quickmic here's the log you asked for and the 

Edited by gevarghe
Link to comment
Share on other sites

quickmic
34 minutes ago, gevarghe said:

kodi.logHi... Was tied up last few days. Tried deleting the advancedsettings.xml but didn't work for me after the reboot.

@quickmic here's the log you asked for and the 

How did try to connect? Was there a list of servers? Did you use manual connect or emby connect?

The log shows there are no Emby servers found.

If manually, did you enter the server address (ip) WITH the http or https prefix?

e.g.

http://192.168.0.207

Link to comment
Share on other sites

gevarghe

Used emby connect... Showed the welcome message after entering my details then the list of servers dialog window comes up but nothing to connect to (but server's up and accessible on my phone via the official emby app)

Link to comment
Share on other sites

gevarghe

Think I'll need to be more structured with my testing. Will uninstall both kodi and emby add-on again and share 3 logs. 1) with emby connect 2) with manual connect 3) deleting advancedsettings.xml

Anything else I can try out?

 

Link to comment
Share on other sites

quickmic
2 hours ago, gevarghe said:

Think I'll need to be more structured with my testing. Will uninstall both kodi and emby add-on again and share 3 logs. 1) with emby connect 2) with manual connect 3) deleting advancedsettings.xml

Anything else I can try out?

 

This has nothing todo with advanced settings. If there would be an issue, it's in the logs. Yes please try manual connect. Do you have special characters in the url. (yes this is possible even not a good idea).

With emby connect the server url comes from the "API". I assume something is wrong there, so a manual connect would prove that the connection itself works (or not).

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
 Share

×
×
  • Create New...