Aurora Bug Reports Discussion

Due to your excellent troubleshooting we are going to try disabling TLS 1.3 on our end and see if it helps any others that might be facing the same issue. The connection will simply revert to TLS 1.2. Not everyone even uses 1.3 as of yet.

The only time i have Aurora issues is when something with the program is outdated, only way for me to fix it is downloading the latest version or just downloading it again in general and overwriting whats in the folder..

Kind of annoying

I believe thats also whats going on, but im never locked out of being able to login as long as i redownload Aurora... I always thought it meant that the program was updated and there was some kind of version auth check problem

[Edited by CJ, 10/25/2022 12:18:21 AM]

That is a different issue and you forgot to mention important details. "Aurora issues when program is outdated" is not concrete enough. What kind of issues? Error message? Screenshot? Log file?

I believe its the same TLS problem
i just checked my keys and whats described above isnt there so i dunno..
But it had to do with logging in and some type of authentication issue which gets resolved by redownloading Aurora, if it shows up again i'll post it

I found it, thanks for reminding me about the log file lol

8:10 PM: Failed to download update because of System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.

[Edited by CJ, 10/25/2022 12:26:13 AM]

sorry heres the whole thing

8:10 PM: Failed to download update because of System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure: RemoteCertificateNameMismatch
at System.Net.Security.SslStream.SendAuthResetSignal(ProtocolToken message, ExceptionDispatchInfo exception)
at System.Net.Security.SslStream.CompleteHandshake(SslAuthenticationOptions sslAuthenticationOptions)
at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](TIOAdapter adapter, Boolean receiveFirst, Byte[] reAuthenticationData, Boolean isApm)
at System.Net.Http.ConnectHelper.EstablishSslConnectionAsync(SslClientAuthenticationOptions sslOptions, HttpRequestMessage request, Boolean async, Stream stream, CancellationToken cancellationToken)
--- End of inner exception stack trace ---

[Edited by CJ, 10/25/2022 12:27:06 AM]

not the same problem afterall maybe?

[Edited by CJ, 10/25/2022 12:27:58 AM]

It's not the same error. In your case it dislikes the SSL certificate at all although it's valid 😕

Ah, gotcha lol
Well redownloading Aurora fixes it, BUT i have to do that every time i get that error which is kinda ehhh

[Edited by CJ, 10/25/2022 12:37:23 AM]

FYI: It turns out to be McAfee which re-encrypts the HTTPS traffic using its own certificate. The certificate it uses is valid but it's different from the original certificate we use. I think that the only solution is to whitelist Aurora in McAfee and if that doesn't help, turn off the "security feature" which is responsible for analyzing https traffic in McAfee.

Unfortunately as the Whole Home Protection is ISP/Router based and not on my PC i dont have any control over being able to whitelist websites.. So if it comes down to it ill just disable it on an as needed basis or just continue to manually update Aurora when i get the error.

Thanks

For the record, it didnt always do this, only the past few months or a year or so

[Edited by CJ, 10/25/2022 7:02:06 AM]