mylesmar10 0 Posted January 7, 2019 Share Posted January 7, 2019 Hi there, I recently replaced my old Roku 3 with a Roku Streaming Stick+ and have found that Remember User doesn't work properly on it. Emby App Version: beta 3.0.134 (Previously was using stable, but thought maybe beta would fix the problem. It did not.) Roku Model: 3810X - Roku Streaming Stick+ Roku Software: 9.0.0 - build 4083-50 Direct/Manually connecting to the server locally on its private IP. Things I have tried: I have verified that Remember User is set to ON, but every time I open the app I have to enter my PIN on my user account. I have tried turning it to OFF, restarting the Roku, signing back in, turning it back to ON, restarting Roku again. I tried installing the beta app, which has the same problem as stable. The Remember User feature is still working properly on all other Rokus in my house, but I have now set up two Streaming Stick+ and they both fail to remember the user. The other Rokus include a Roku3, a Roku4, and a Roku Streaming Stick (older model). Thank you for your help! Link to comment Share on other sites More sharing options...
ebr 14925 Posted January 7, 2019 Share Posted January 7, 2019 Hi. If you are in your local environment there should be no need for Emby Connect (logging in with PIN). Have you tried logging in by selecting the server and user? Link to comment Share on other sites More sharing options...
mylesmar10 0 Posted January 8, 2019 Author Share Posted January 8, 2019 Hey ebr thanks for taking time to look into this. I utilize the “Enable in-network sign in with my easy pin code” feature. I am not using Emby connect, I manually entered the private IP of my server, then chose my user, then entered my pin code. This works on my older Roku devices, but in the streaming stick+ it makes me select my user and enter my pin every time. Link to comment Share on other sites More sharing options...
ebr 14925 Posted January 8, 2019 Share Posted January 8, 2019 On the device that is having this issue, please follow the instructions to send a log from the app after you've logged in. Thanks. Link to comment Share on other sites More sharing options...
mylesmar10 0 Posted January 9, 2019 Author Share Posted January 9, 2019 ebr, I have sent the log at Jan 09, 2019 0548 CST. Steps taken: Go to Roku Home Select Emby Beta Select user "Myles" Enter pin code when prompted Go to settings and turn debug on Press back, select exit emby Select Emby Beta from Roku Home Select user "Myles" Enter pin code when prompted Send log Please let me know if you need any additional information. Link to comment Share on other sites More sharing options...
ebr 14925 Posted January 9, 2019 Share Posted January 9, 2019 Your server is advertising no local address. Do you have a VPN or reverse proxy or something else like that involved? Does the address show properly on your server dashboard? Link to comment Share on other sites More sharing options...
mylesmar10 0 Posted January 18, 2019 Author Share Posted January 18, 2019 (edited) Sorry for the late reply, been a bit busy. Emby server does NOT see a local address. I can see the following error in the logs: System.Net.NetworkInformation.NetworkInformationException: System.Net.NetworkInformation.NetworkInformationException (2): An error was encountered while querying information from the operating system. ---> System.AggregateException: One or more errors occurred. (Could not find a part of the path '/proc/sys/net/ipv4/conf/lo/forwarding'.) (Could not find a part of the path '/proc/sys/net/ipv4/conf/eth0/forwarding'.) (Could not find a part of the path '/proc/sys/net/ipv4/conf/lo/forwarding'.) (Could not find a part of the path '/proc/sys/net/ipv4/conf/eth0/forwarding'.) (Could not find a part of the path '/proc/sys/net/ipv4/conf/lo/forwarding'.) (Could not find a part of the path '/proc/sys/net/ipv4/conf/eth0/forwarding'.) ---> System.IO.DirectoryNotFoundException: Could not find a part of the path '/proc/sys/net/ipv4/conf/lo/forwarding'. This makes sense, I am running Emby in a LX container under smartOS on Ubuntu 16.04. Networking doesn't work quite the same as you would see in a normal virtualization environment. (Py2.7.13) root@emby:~# ls -lah /proc/sys/net/ipv4/ total 0 dr-xr-xr-x 1 root root 0 Jan 17 21:37 . dr-xr-xr-x 1 root root 0 Jan 17 21:37 .. -rw-r--r-- 1 root root 0 Jan 17 21:37 ip_local_port_range -rw-r--r-- 1 root root 0 Jan 17 21:37 tcp_fin_timeout -rw-r--r-- 1 root root 0 Jan 17 21:37 tcp_keepalive_intvl -rw-r--r-- 1 root root 0 Jan 17 21:37 tcp_keepalive_time -rw-r--r-- 1 root root 0 Jan 17 21:37 tcp_max_syn_backlog -rw-r--r-- 1 root root 0 Jan 17 21:37 tcp_rmem -rw-r--r-- 1 root root 0 Jan 17 21:37 tcp_sack -rw-r--r-- 1 root root 0 Jan 17 21:37 tcp_window_scaling -rw-r--r-- 1 root root 0 Jan 17 21:37 tcp_wmem (Py2.7.13) root@emby:~# But the IP is local and does not change. (Py2.7.13) root@emby:~# ifconfig eth0 Link encap:Ethernet HWaddr c2:b1:d0:97:f1:88 inet addr:192.168.111.230 Bcast:192.168.111.255 Mask:255.255.255.0 inet6 addr: fe80::c0b1:d0ff:fe97:f188/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:74355124 errors:0 dropped:0 overruns:0 frame:0 TX packets:132380122 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:79424745846 (79.4 GB) TX bytes:158710257924 (158.7 GB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MULTICAST MTU:8232 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 TX bytes:0 (0.0 BUT as I mentioned, my older Roku devices and my TCL Roku TV all remember my user without issue. It is only the newer Roku Stick+ devices that are exhibiting this behavior. Also, a follow up, I updated Emby Server to the new 4.X version that just came out and switched back to the production Emby Roku app, and things have gotten worse. Now when I open the app it takes me straight to the Emby Connect screen. If I back out I see my server in the list, select it, and it fails to load my users at all. I have to now delete the server and re-enter the IP to get the user list up, and login with my PIN code. I have tried completely removing the Emby app and reinstalling it, but nothing changes. Again, this is ONLY on the Roku Stick+ devices. I can record video of the issue if that would help. Edited January 25, 2019 by ebr Formatting Link to comment Share on other sites More sharing options...
ebr 14925 Posted January 18, 2019 Share Posted January 18, 2019 I think you need to get your server to properly report the local address on the dashboard for all of this to work properly. Link to comment Share on other sites More sharing options...
mylesmar10 0 Posted January 25, 2019 Author Share Posted January 25, 2019 I went to Advanced -> Bind to local network address and set it to 192.168.111.230. The dashboard now shows/recognizes the local IP. This broke even my older Roku devices. Now when I open the Emby app on ANY Roku device it goes straight to my user list and requires that I log in. I reset my PIN so I could sign in as my user without entering a password. So now my steps to access Emby on any Roku device in my home network are... Go to Emby Be presented with user list Select my user Good to go I prepended my local username with an underscore so my user is the first/default selected user on the user list. This is manageable, of course, but the original reason for creation of this thread persists. If you don't want to dig any deeper I won't cry over it, but I do feel this is a bug. Let me know if there is anything I can do to assist! Link to comment Share on other sites More sharing options...
Luke 37098 Posted January 25, 2019 Share Posted January 25, 2019 Do you use other Emby apps? are they able to remember the user? Link to comment Share on other sites More sharing options...
mylesmar10 0 Posted January 26, 2019 Author Share Posted January 26, 2019 Hey Luke, I do not have this issue with the iOS app nor the Emby app for Samsung TVs. Both of these apps are opening straight into the last used user. Link to comment Share on other sites More sharing options...
Luke 37098 Posted January 26, 2019 Share Posted January 26, 2019 Ok, @@speechles will review and test this out, thanks ! Link to comment Share on other sites More sharing options...
Solution mylesmar10 0 Posted May 14, 2019 Author Solution Share Posted May 14, 2019 Ok, @@speechles will review and test this out, thanks ! Just a heads up to anyone interested, this issue has been resolved as of Emby Server Version 4.1.1.0. It was still a problem up until this version specifically. I didn't see it noted in the changelogs but something there fixed it. Thanks to everyone involved! Link to comment Share on other sites More sharing options...
Luke 37098 Posted May 14, 2019 Share Posted May 14, 2019 Thanks for the feedback. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now