Issue logging in after linking to Emby account

[invalid 0]

I have about 20 users on my box right now and none of them can log in, including myself, directly to the server. This started happening after linking accounts to Emby accounts. Basically, we can all log in from http://emby.media then go to the server from there perfectly fine. However, if I visit my server directly (IE http://emby.example.com:8096/) it says "Invalid username or password". If we try to hit forgot password at this location it doesn't even recognize the username.

 

Any help would be much appreciated. I'm running the stable build on Debian 7 x64. Logs are attached. No firewall rules are in place that affect these ports.

 

Here is the error:

2015-08-25 21:00:35.8566 Debug - HttpServer: HTTP Response 401 to xxx.xxx.xxx.xxx. Response time: 1.065 ms.
	Url: http://emby.example.com:8096/Users/authenticatebyname
2015-08-25 21:00:53.3260 Debug - HttpServer: HTTP POST http://emby.example.com:8096/Users/authenticatebyname
	Ip: xxx.xxx.xxx.xxx:49618. Headers: Host=emby.example.com:8096,Connection=keep-alive,Content-Length=91,Accept=application/json, text/javascript, */*; q=0.01,Origin=http://emby.example.com:8096,User-Agent=Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.157 Safari/537.36,Authorization=MediaBrowser Client="Emby Web Client", Device="Chrome 44.0.2403.157", DeviceId="5f071f8d073c1aaca87a9d8cda7cba52a6fa4119", Version="3.0.5675.1",Content-Type=application/json,Accept-Encoding=gzip, deflate,Accept-Language=en-US,en;q=0.8
2015-08-25 21:00:53.3272 Error - DtoUtils: ServiceBase<TRequest>::Service Exception
	*** Error Report ***
	Version: 3.0.5675.1
	Command line: /usr/lib/emby-server/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartpath /usr/lib/emby-server/restart.sh
	Operating system: Unix 3.2.0.4
	Processor count: 8
	64-Bit OS: True
	64-Bit Process: True
	Program data path: /var/lib/emby-server
	Mono: 4.0.3 (Stable 4.0.3.20/d6946b4 Tue Aug  4 09:43:57 UTC 2015)
	Application Path: /usr/lib/emby-server/MediaBrowser.Server.Mono.exe
	Invalid username or password entered.
	MediaBrowser.Controller.Net.SecurityException
	  at MediaBrowser.Server.Implementations.Library.UserManager+<AuthenticateUser>c__async1.MoveNext () [0x00000] in <filename unknown>:0 
	--- End of stack trace from previous location where exception was thrown ---
	  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x00000] in <filename unknown>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00000] in <filename unknown>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00000] in <filename unknown>:0 
	  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[System.Boolean].GetResult () [0x00000] in <filename unknown>:0 
	  at MediaBrowser.Server.Implementations.Session.SessionManager+<AuthenticateNewSession>c__asyncC.MoveNext () [0x00000] in <filename unknown>:0 
	--- End of stack trace from previous location where exception was thrown ---
	  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x00000] in <filename unknown>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00000] in <filename unknown>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00000] in <filename unknown>:0 
	  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[MediaBrowser.Model.Users.AuthenticationResult].GetResult () [0x00000] in <filename unknown>:0 
	  at MediaBrowser.Api.UserService+<Post>c__async1.MoveNext () [0x00000] in <filename unknown>:0 
	
2015-08-25 21:00:53.3272 Error - HttpServer: Error processing request for /Users/authenticatebyname
	*** Error Report ***
	Version: 3.0.5675.1
	Command line: /usr/lib/emby-server/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartpath /usr/lib/emby-server/restart.sh
	Operating system: Unix 3.2.0.4
	Processor count: 8
	64-Bit OS: True
	64-Bit Process: True
	Program data path: /var/lib/emby-server
	Mono: 4.0.3 (Stable 4.0.3.20/d6946b4 Tue Aug  4 09:43:57 UTC 2015)
	Application Path: /usr/lib/emby-server/MediaBrowser.Server.Mono.exe
	Invalid username or password entered.
	ServiceStack.HttpError
	No Stack Trace Available
	
2015-08-25 21:00:53.3282 Debug - HttpServer: HTTP Response 401 to xxx.xxx.xxx.xxx. Response time: 1.993 ms.
	Url: http://emby.example.com:8096/Users/authenticatebyname

Log.txt

[Luke 42077]

When you login locally you should be using your local server username and password, not your Emby Connect info. Are you making sure to do that?

[invalid 0]

When you login locally you should be using your local server username and password, not your Emby Connect info. Are you making sure to do that?

 

I've tried doing that to no avail. The way I added users was:

 

I hit Add Guest, the email was sent to sign up to Emby. The Emby account was linked to my server. I then had to create the user on my server then enter their Emby username/password to link that. Now they can log in if they go through emby.media, however if they get logged out they cannot login to the server directly it seems. Also, this would mean that they don't technically have a 'local' password since I synced them to an Emby account?

Edited August 26, 2015 by invalid

[Luke 42077]

Right ok yea, guests are intended to be Emby Connect only. If you want them to work both ways, you should remove the guests, then create local users, and when you do this, enter their Emby Connect info which will link the local account to the online account. This is a more advanced scenario whereas the guest feature is more designed to just have one simple way of doing it.

[invalid 0]

Right ok yea, guests are intended to be Emby Connect only. If you want them to work both ways, you should remove the guests, then create local users, and when you do this, enter their Emby Connect info which will link the local account to the online account. This is a more advanced scenario whereas the guest feature is more designed to just have one simple way of doing it.

 

After trying out something I'm able to say that I can log into the users.. however.. they don't have a password - I simply typed the username and hit enter. I don't quite understand the user system it seems. Why doesn't it use the Emby account password if I linked the account to their Emby account? This is quite cumbersome to have them make an Emby account, me create a local account, then ask them to login to their local account and set their local account password to whatever they made their Emby password to simplify things. Then when they want to stream from the Emby web app they have to user their Emby password, so if they forget that and use the reset feature.. they will try to use that new password when logging in locally, reset that one.. it's just a mess from my perspective.

Edited August 26, 2015 by invalid

[Luke 42077]

The guest feature is not intended to use the local login system. Nobody has ever really requested that and to be honest, if you want them to connect to your server directly then you don't even need to use the Emby Connect feature.

[invalid 0]

The guest feature is not intended to use the local login system. Nobody has ever really requested that and to be honest, if you want them to connect to your server directly then you don't even need to use the Emby Connect feature.

 

Excuse my assumptions of how the user system works . I'm coming from Plex, so they simply needed to create 1 account - a Plex account. It just sounded easier to have them make an Emby account. I like knowing that if and when they make an Emby account, they have a password and it's decent since it was allowed by your system. Now I have to create a generic password or generate, manually, a password for each individual user when creating them.

 

When creating a local user I would suggest adding a legit creation page. Asking for their e-mail, having some simple password options (Change on first login, generate, manual, etc). Have the system send an email saying that their account was created, etc. Either this or detect when logging in if the associated user has an account linked w/ Emby - if so, use your login API to login instead of the local password.

[Luke 42077]

Yes allowing the concept of local accounts and online accounts creates power but also confusion, this being a perfect example. Everything is easy when there's just one way of doing it. But we chose to allow both ways so that if users want to avoid the cloud, they can do that. That's why they both exist.

 

I don't think we're going to do email addresses and things of that nature though for local accounts. Well I suppose I wouldn't rule it out but imagine the scenario of just wanting to create a user profile for your kids or your wife. that would create some hassle. now I imagine you might respond saying well the system could do both but then that brings us down the path of even more ways of doing it and even more confusion. So then that brings us back to square one which is, hey, you can have all that if you just keep them as Emby Connect users.