Jump to content

Suddenly have to re-add server and login every time I start Emby


Whiskeyjack
Go to solution Solved by ebr,

Recommended Posts

Whiskeyjack

Hi all,

 

I had Emby working fine for months but now all of a sudden every time I start Emby in Roku I have to re-add my server before I connect.  When I initially open the app it shows two servers (I only have one...) and the option to sign in with Emby connect.  If I select either of the servers, I get "Timeout waiting for a response from the server".  If I use Emby Connect and enter the PIN, it goes back to the same list of two servers, and they still don't work.  The only way to connect is to go back through "Add Server" and so on.

 

Emby works fine on my FireStick, on my phone, in my browser, etc.  I've restarted Emby as well as the server it runs on.  I've factory reset my Roku.  I've tried both the stable and beta version of the Emby app.  I've also tried the stable and beta release of Emby Server.  Still have the same result.

 

Any ideas?  If there is a specific log that would help please let me know and I'll provide it.

Link to comment
Share on other sites

1. Go to the home screen of the Roku and press the * key to go to settings

    (... navigate to the cog at the top of the home screen to get to settings that way)

2. Scroll to bottom of the settings and choose "Reset Settings".

3. Open your Emby server on a web client and go to the dashboard

4. Go to the devices tab. Find any Roku devices and delete them. Do not worry they rebuild when the user authenticates with a Roku device again. This just clears the tokens and forces them to regenerate.

 

Doing all the steps above in the order above "should" clear your issue. Let us know if this helps or doesn't. Thanks. ;)

Edited by speechles
Link to comment
Share on other sites

Whiskeyjack

1. Go to the home screen of the Roku and press the * key to go to settings

    (... navigate to the cog at the top of the home screen to get to settings that way)

2. Scroll to bottom of the settings and choose "Reset Settings".

3. Open your Emby server on a web client and go to the dashboard

4. Go to the devices tab. Find any Roku devices and delete them. Do not worry they rebuild when the user authenticates with a Roku device again. This just clears the tokens and forces them to regenerate.

 

Doing all the steps above in the order above "should" clear your issue. Let us know if this helps or doesn't. Thanks. ;)

Hi!

 

Thanks for the reply.

 

I don't have a "reset settings" option other than factory reset which I've done before. I did uninstall the app and restart the Roku. I deleted all Roku instances from the Devices tab.  Still have the same problem.

Link to comment
Share on other sites

Happy2Play

Hi!

 

Thanks for the reply.

 

I don't have a "reset settings" option other than factory reset which I've done before. I did uninstall the app and restart the Roku. I deleted all Roku instances from the Devices tab.  Still have the same problem.

 

You are going to Settings within the Emby Roku app/channel and not the Roku itself, correct?

Link to comment
Share on other sites

Whiskeyjack

You are going to Settings within the Emby Roku app/channel and not the Roku itself, correct?

Hi,

 

Within the Roku channel settings I have these options:

"My Rating"

"Move Channel"

"Remove Channel"

"Check for updates"

"Give us Feedback"

"Close"

Link to comment
Share on other sites

Happy2Play

Hi,

 

Within the Roku channel settings I have these options:

"My Rating"

"Move Channel"

"Remove Channel"

"Check for updates"

"Give us Feedback"

"Close"

You have to log into the Emby Roku channel and go to Settings within the channel.  It is at the bottom of home screen or hit * on home screen within the Emby Roku channel.

Link to comment
Share on other sites

Whiskeyjack

You have to log into the Emby Roku channel and go to Settings within the channel.  It is at the bottom of home screen or hit * on home screen within the Emby Roku channel.

Oh, I definitely misunderstood.  I'll try that, thanks!

Link to comment
Share on other sites

Whiskeyjack

1. Go to the home screen of the Roku and press the * key to go to settings

    (... navigate to the cog at the top of the home screen to get to settings that way)

2. Scroll to bottom of the settings and choose "Reset Settings".

3. Open your Emby server on a web client and go to the dashboard

4. Go to the devices tab. Find any Roku devices and delete them. Do not worry they rebuild when the user authenticates with a Roku device again. This just clears the tokens and forces them to regenerate.

 

Doing all the steps above in the order above "should" clear your issue. Let us know if this helps or doesn't. Thanks. ;)

Hi,

 

I've done all these steps and the issue persists.

Link to comment
Share on other sites

*false alarm*

 

Nothing to see here.. lol

Edited by speechles
Link to comment
Share on other sites

Whiskeyjack

Hey all,

 

It's sorted out now.  I deleted my Emby container, reinstalled, and rebuilt my appdata folder, cleared user settings in the roku app, now everything is working.  Not sure what fixed it, or what caused the issue in the first place, but it works now.

 

Thanks!

Link to comment
Share on other sites

Hey all,

 

It's sorted out now.  I deleted my Emby container, reinstalled, and rebuilt my appdata folder, cleared user settings in the roku app, now everything is working.  Not sure what fixed it, or what caused the issue in the first place, but it works now.

 

Thanks!

 

Glad you got it sorted. Enjoy your sheltering at home now. ;)

Link to comment
Share on other sites

  • 2 months later...
Whiskeyjack

Having this same issue again.

I feel like I shouldn't have to reinstall everything each time.  I don't experience this one any of my other devices, only Roku, so I assume the problem must be with the app.

Link to comment
Share on other sites

How many Emby servers do you have KNOWN on the Roku app?

By KNOWN, I mean, there is a limit to how large we can make the registry.

Each application on ROKU gets 16KB of registry space(memory). This "used to" be 24KB when applications used the older SDKA. 16KB is not infinite space. We must store the registry as JSON so that we do not have issues with encodings and characters staying the characters they are supposed to be and keeping UTF-8 support, etc. So we must use JSON that is what we do. We must treat everything as a string which we do when reading from and writing to the registry.

The problem happens when you use Emby Connect and have LOTS and LOTS of servers listed there. When the JSON exceeds bounds it no longer gets written.

On Roku only the last server the Roku connected to it will remember the credentials. So if you log in on SERVER A and log in on SERVER B it isn't cache the login for both and making it seamless to enter either after. On Roku because of the registry problem I mention above we can only keep track of the last server credentials. We hope you understand and apologies. When Roku allows applications more space in the registry we might be able to do more. But presently we are doing the best we can. 

Edited by speechles
Link to comment
Share on other sites

Whiskeyjack

Thanks for the response!

 

I don't think this is the same issue I'm experiencing as I use only one server and I don't use emby connect, which doesn't typically work either.

Edited by Whiskeyjack
Link to comment
Share on other sites

8 minutes ago, Whiskeyjack said:

Thanks for the response!

 

I don't think this is the same issue I'm experiencing as I use only one server and I don't use emby connect, which doesn't typically work either.

It might be the bashing of the authentication key. Sometimes with a slow server the application may believe it failed. It at that point can/does/will fail the existing tokens. If you press HOME at that point it wont registry save that token bashing. But if you try to enter the server again after it bashed the tokens it can/will/does save these bashed and empty authentication tokens/credentials. That might be what is occuring. 

Can you enable debugging in the app? Once enabled press HOME. Then enter the application once you know it has this problem with logging in. Note the time/date you did this. Do not use HOME button on your remote as it wipes logs. Just keep trying to login until you can log in. After you log in find the SEND LOGS button at the very bottom of the home screen. After that @ebr can check those logs and see if indeed this is a timeout. Unlike the other guys who let any Tom, Dick, or Harry read your logs on Emby only @ebr or @luke have this ability and for a reason. We respect your privacy. ^_~

Edited by speechles
Link to comment
Share on other sites

Whiskeyjack
Just now, speechles said:

It might be the hashing of the authentication key. Sometimes with a slow server the application may believe it failed. It at that point can/does/will fail the existing tokens. If you press HOME at that point it wont registry save that token bashing. But if you try to enter the server again after it based the tokens it can/will/does save this bashed and empty tokens. That might be what is occuring. 

Can you enable debugging in the app? Once enabled press HOME. Then enter the application once you know it has this problem with logging in. Note the time/date you did this. After @ebr can check those logs and see if indeed this is a timeout. Unlike the other guys who let any Tom, Dick, or Harry read your logs on Emby only @ebr or @luke have this ability and for a reason. We respect your privacy. ^_~

Thanks again for the reply!  Fortunately enabling debugging was enough to cause this issue again, so I didn't have to wait long.  Time is 0809MST.

Link to comment
Share on other sites

EBR will need your server name/username on that server and the time/date. You can also use PM to contact him rather than public. He is busy so give him time to reply if you choose to PM. Thanks. :)

Link to comment
Share on other sites

Whiskeyjack

Ah, fair enough.  Just didn't want to harass anyone directly. ;)

@ebr

My server name and username are both 'whiskeyjack', DTG 210720 @ 1409 UTC

Link to comment
Share on other sites

6 hours ago, Whiskeyjack said:

Ah, fair enough.  Just didn't want to harass anyone directly. ;)

@ebr

My server name and username are both 'whiskeyjack', DTG 210720 @ 1409 UTC

Did you actually go through the procedure to send the log at that time?  I do not see it.

Link to comment
Share on other sites

Whiskeyjack

Hi there.

 

I apologize, I thought I had but perhaps I made a mistake.  I went through the process again and sent the logs.  Info:

 

Time: 210720 @ 2123 UTC

Server name: whiskeyjack

User name: whiskeyjack

 

Thank you!

Edited by Whiskeyjack
Link to comment
Share on other sites

Whiskeyjack
3 hours ago, ebr said:

Did you actually go through the procedure to send the log at that time?  I do not see it.

@ebr

My DNS blocks some requests from Roku which may be including these debug logs.  If they're still not available when you find time to assist, please let me know and I'll whitelist Roku and try again.

Link to comment
Share on other sites

I got your log and see a successful sign in but it looks like the automatic sign in failed prior to that.

It may be that your network setup is making your client look like it is remote because the app is trying to connect to an IP address in the public domain.

Make sure that the server is configured to understand your local network and also that the LAN IP address shown on the dashboard is correct (10.0.0.10 in your case).

Link to comment
Share on other sites

You can adjust what Emby Server thinks is your LOCAL network from the web admin.

Click on the Network Menu item on the left and the first item on the right will be a field called LAN networks:

This is where you can adjust what IP blocks are local to the server.

If you need help understanding what to put there just ask.

Link to comment
Share on other sites

Whiskeyjack
1 hour ago, ebr said:

I got your log and see a successful sign in but it looks like the automatic sign in failed prior to that.

It may be that your network setup is making your client look like it is remote because the app is trying to connect to an IP address in the public domain.

Make sure that the server is configured to understand your local network and also that the LAN IP address shown on the dashboard is correct (10.0.0.10 in your case).

Adding my local network in the Emby server settings fixed the issue where Emby thinks I'm connecting remotely (in that, now I can login without a password).  However, I still have to re-add my server each time.  But hey, this is progress and makes it a lot faster to get back in!

29 minutes ago, cayars said:

You can adjust what Emby Server thinks is your LOCAL network from the web admin.

Click on the Network Menu item on the left and the first item on the right will be a field called LAN networks:

This is where you can adjust what IP blocks are local to the server.

If you need help understanding what to put there just ask.

Thanks for the replies!

 

My server is on 10.0.0.10, and my roku is 10.0.0.22, and in Emby's "Network" settings LAN networks has: 10.0.0.0/24.

I believe the server knows I'm accessing it locally as it lists my users that aren't hidden from local networks, but hidden from remote networks.

I've attached some screenshots of my settings just in case you see something that's obviously wrong.

09:55:11-2020.png

09:49:47-2020.png

09:48:50-2020.png

Edited by Whiskeyjack
Link to comment
Share on other sites

The app was seeing an external address from somewhere - not your domain name.   Try clearing the app data (or just uninstall reinstall).

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
×
×
  • Create New...