Bug: Login Failure with 'Check credentials and try again' Message
Login Failure with 'Check credentials and try again' Message
| Status: | Duplicate |
| Added by: |
|
| Reported for: |
Steps to Reproduce
No steps to reproduce
Explanation
Program.BootSequence.SceneState is experiencing an error where login fails with the message 'Check credentials and try again.' This occurs as indicated in the unity log at the timestamp '2025-12-19 15:38:36.0473', resulting in failed login attempts.
Watchers
Screenshots
None
Video Clips
None
Log Files
None
Device
No device information
does the logfile contain anything confidential, like my password?
I sent my logfile location and zip passeword to (unknown user mentioned)
It does not (if it’s the Unity-log.json file there is nothing confidential in it and only devs can see this chat
Thanks again for sending the logs, they are in the hands of (unknown user mentioned) now who will be able to keep you up to date on any findings.
Also an extra thanks because when this has occurred for others on Quest 3 they have been unable to send us their logs so you sending us those will help us.
Btw the location is slightly different than in the instructions
(unknown user mentioned) hey hey. Could you check that your headset time is set to "Automatic"?
The error you're getting is often due to client time being slightly incorrect.
Ok will check
Yes, it‘s set to automatic and the time looks ok
(unknown user mentioned) sorry for the delays, juggling this between various christmas plans.
Any chance you're in a school/college network or in a country like russia with national firewalls?
No I‘m at home, residential
DNS.. I think I‘m using the EU DNS resolver
I can change that…
I changed it to my ISP standard dns and tried again and still got the login screen
This is the error here
Status(StatusCode="Internal", Detail="Error starting gRPC call. HttpRequestException: An error occurred while sending the request WebException: Error: TrustFailure (Authentication failed, see inner exception.) AuthenticationException: Authentication failed, see inner exception. TlsException: Handshake failed - error code: UNITYTLS_INTERNAL_ERROR, verify result: UNITYTLS_X509VERIFY_FLAG_NOT_TRUSTED", DebugException="System.Net.Http.HttpRequestException: An error occurred while sending the request")", "exception": "Alta.Api.DataTransferModels.Exceptions.AuthorizationException: Status(StatusCode="Internal", Detail="Error starting gRPC call. HttpRequestException: An error occurred while sending the request WebException: Error: TrustFailure (Authentication failed, see inner exception.) AuthenticationException: Authentication failed, see inner exception. TlsException: Handshake failed - error code: UNITYTLS_INTERNAL_ERROR, verify result: UNITYTLS_X509VERIFY_FLAG_NOT_TRUSTED", DebugException="System.Net.Http.HttpRequestException: An error occurred while sending the request") ---> Grpc.Core.RpcException: Status(StatusCode="Internal", Detail="Error starting gRPC call. HttpRequestException: An error occurred while sending the request WebException: Error: TrustFailure (Authentication failed, see inner exception.) AuthenticationException: Authentication failed, see inner exception. TlsException: Handshake failed - error code: UNITYTLS_INTERNAL_ERROR, verify result: UNITYTLS_X509VERIFY_FLAG_NOT_TRUSTED", DebugException="System.Net.Http.HttpRequestException: An error occurred while sending the request") ---> System.Net.Http.HttpRequestException: An error occurred while sending the request ---> System.Net.WebException: Error: TrustFailure (Authentication failed, see inner exception.) ---> System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception. ---> Mono.Security.Interface.TlsException: Handshake failed - error code: UNITYTLS_INTERNAL_ERROR, verify result: UNITYTLS_X509VERIFY_FLAG_NOT_TRUSTED\n
Sorry on my phone, so not an easy copy paste
Effectively something about your setup is not trusting something on our side
First occurrence of this we've seen. Hard to tell yet whether there's an issue on our end, but given it's the only case, it could also be something on your end.
Yeah
Could be something like a mitm proxy or whatever
ok so i checked the q3 it uses my wifi router as DNS. my wifi router uses my ISP as DNS
ohhh my router also has DoT configured with noads.joindns4.eu .. that could be blocking some facebook stuff.. let me disable that
yes... that fixed it, i no longer get the s***** login screen.. yeah!
(unknown user mentioned) thanks for explaining and showing the significant part of the log
Awesome to hear that fixed it (unknown user mentioned) 🙂 glad we got there. I’ll note down the solutions you took and the original error so if others come across it I can suggest they try doing that.
Yeah so the problem occurs if you use an adblocking DNS service, I guess something like pihole would also trigger it
Really appreciate you looking into it. Apologies for the inconvenience 🙏
this issue is resolved.