unable to connect to configure server

[deallier 8]

Hi

i have a problem with emby unable to connect to configure server

the problem started after a fresh install of Windows 10 before the server was running on Windows 7 and it was all running very well but as there has not been any updates for W7 for a while and i had some new hardware that would only run on W10 it was time to upgrade. so fresh install of W10 ( i backed up emby and all the settings first ) then fresh install of Emby V 4.6.7.0 then restore the settings from the emby backup ie: users and general settings.

the first problem was anyone using the app could login using the same details as before i understand that they would have to add new server then login but even after doing that it just said invalid username or password

so i reset the passwords and that worked fine

but if you exit the app then restart the app they have to log back in but, i have login as this user enabled and log out set as never and the error is unable to connect to configure server

i have inc a log file and event like this happened at  2021-12-14 10:33:13.837 in the log file

 

thank you

embyserver-63775075355.txt

[ebr 16182]

Hi. Does the message actually say "Unable to connect to configured server"?

Make sure the address shown on the dashboard of the server is correct.  Then try setting the app to "Show login screen", login and then set it back to "Login as this user".

[deallier 8]

Hi Ebr 

yes you are right it says "Unable to connect to configured server"

i did do this ( Then try setting the app to "Show login screen", login and then set it back to "Login as this user" ) a few times but i didn't log out then back in again and change it back 

thanks that did the trick it works, now i just have to explain this to all the users on the server 

thanks for your help

 

[ebr 16182]

If you can make the IP address to your new server be the same as the old one, it will work as well.

I'll have to be sure we are re-saving the server information on each successful login.  It appears the old info is hanging around...