successful remote login shows failed on client

[justinrh 268]

original post title:  successful remote login shows failed on client

I'm logging in from a remote client web app.  The first attempt did fail. The second attempt is successful according to the log file, but the client reported that it failed: "Sign In Error" - invalid user/pass
(Yes, I put that string in the log file after the success msg.)

 

embyserver.txt

Edited October 7, 2021 by justinrh

[Carlo 4561]

Hi, This looks like you tried logging in directly to the server and it failed, then you used Emby Connect and passed.
The passwords can be different between the server and Emby Connect.

[justinrh 268]

I don't use Emby Connect.  I used the web app to make a direct connection to the server using the same creds.

This may not be worth chasing this particular instance, but I do want Emby to be aware.  Entering this user's creds is tedious on a touch screen and it makes me wonder how many times I was told I did it wrong when I didn't and making me do it again.

[Carlo 4561]

Is this device on LAN or remote?

I ask because you can set this in users->password tab
A 4 digit pin on your home LAN is pretty easy to enter!

[justinrh 268]

Thanks for the hint (I was aware) but this account is used only remotely.

[Carlo 4561]

Got ya.  No answer to the original question but maybe something happened in transport of the packets containing username or password.

One time things like this can be impossible to figure out.  If it's not happening regularly it's likely nothing to worry about.

[Luke 42268]

What client was it?

[justinrh 268]

Web app (Firefox on Android).

[Luke 42268]

Can you show a screenshot? Thanks.

[justinrh 268]

Screenshot of the error msg?  No, but if you search the resources in the codebase for the string I posted, you could see it.  Or, just try to login to your server with bogus creds    It is an Emby error msg.

Edited October 5, 2021 by justinrh

[Luke 42268]

The log shows a filed attempt from firefox followed by a successful one, so i'm guessing that's where it came from.

[justinrh 268]

Correct.  That is the client I was using.

[Luke 42268]

So does this answer your question?

[justinrh 268]

9 hours ago, Luke said:

So does this answer your question?

Let's go back to the OP and see: "The second attempt is successful according to the log file, but the client reported that it failed"

The answer would be no.  But, I am willing to abandon this thread and call it done.  If it becomes a habit we can revisit.

Edited October 7, 2021 by justinrh

[Happy2Play 9814]

I guess the question here is why did the first failed attempt try to authenticate with Connect if user is not using Connect?

2021-10-02 11:47:23.349 Info HttpClient: POST https://connect.emby.media/service/user/authenticate

Would it have to do with information cached in browser? @Luke

[Luke 42268]

4 hours ago, Happy2Play said:

I guess the question here is why did the first failed attempt try to authenticate with Connect if user is not using Connect?

2021-10-02 11:47:23.349 Info HttpClient: POST https://connect.emby.media/service/user/authenticate

Would it have to do with information cached in browser? @Luke

Because it's common that users confuse the two login methods, so we try to account for that.

[Luke 42268]

Are you still running into this?

[justinrh 268]

I can't say as I'm not monitoring the logs for it.  I'm also getting better at typing the credentials   Next time I have a failure I'll try to keep in mind to look at the log.