Aurora Bug Reports Discussion

Then I have no idea why it fails on accessing a normal https site. If you have a different machine in the same network where you can run Aurora on, you could at least verify that it's not a network problem. But even if it isn't it doesn't tell us the actual problem.

Checking on another machine. EDIT: same error there.

Just a thought, but is it possible the issue is with the way Aurora connects to the internet? I used steam idlemaster for a long while, but it had authentication issues too that began popping up after Microsoft deprecated Internet Explorer. As soon as that went down, logins to steam were no longer possible without getting login info from the cookies and pasting them into the app.



Just talked to a friend who suggested I run curl on powershell. First time, it spit up an error, so he suggested I try the usebasicparsing tag, like so: "curl -UseBasicParsing www.cheathappens.com"

and I got "StatusCode : 200
StatusDescription : OK"

and a bunch of other stuff (can send if it would help you). He looked at it (I'm a game dev but networking isn't my area of expertise) and said that it didn't indicate a TLS error, which is in keeping with me having the TLS stuff up.

So I've given him a process monitor file and he's looking over it. I can attach it in a zip if it would help you!

I really love Aurora and while it's a bummer I'm having technical difficulties, if I can provide you with any information to ensure nobody else has the problem in the future, I'm happy to assist.

[Edited by docseuss, 10/23/2022 9:59:54 AM]

[Edited by docseuss, 10/23/2022 10:33:23 AM]

I brought up the question with my friend who had me run the curl request and who looked at my logs. We noticed Nvidia's capture was running, so turned that off to see, and got nothing. He had me boot up IE (which is why I added in the note above), we talked about it, and he asked this "is it possible akamai is blocking the request and showing an HTML page that leads to the parser error?"

[Edited by docseuss, 10/23/2022 10:56:18 AM]

Aurora is checking the connection on https : // www.cheathappensnext.com (notice its a different URL also the https, so it should be 443 port). There is nothing special Aurora is doing. Its a simple GET request to the url above using Microsoft's .NET function. And it works fine for everyone else.

You may try VPN or different DNS provider. I'm not really an expert when it comes to SSL stuff.

[Edited by 0x90, 10/23/2022 10:59:22 AM]

Hey! So! I fixed it, and here's how we did it:

In the registry, we deleted the TLS 1.3 entry (there was no TLS 1.2 entry).

We have two theories on what happened: I had installed hardly anything when I installed Windows. Steam, stuff like that. NO firewalls, no networking, nothing of that nature.

But one thing I did install was Asustor Control Center, which had TLS 1.3 as a prerequisite.

So either:
1) installing TLS 1.3 from Asustor is broken on its own,
2) or TLS 1.3 is normally not configured on people's machines and I installed a valid version and the Aurora app has an issue with improperly handling TLS 1.3 on its end.

I hope that helps anyone who might have this issue in the future--deleting TLS1.3 from the registry in windows rather than adding it is what actually solved the problem!

I dunno if you can double check on your end and see if there are any potential configuration issues or conflicts with Asustor Control Center (it's a NAS management software) and how it handles TLS 1.3.

[Edited by docseuss, 10/23/2022 12:55:27 PM]

Microsoft says that .NET relies on the OS to support it. I dont know the current state of TLS 1.3 implementation in Windows but given that it was 2 years ago when it has been added as "experimental" I assume it's now "stable".

I just checked my IE settings and TLS 1.2 and TLS 1.3 are both enabled. I have no issues with Aurora connection. Perhaps it falls back using TLS 1.2 but you said yours wasn't disabled as well, so no idea. 😐

For reference, can you please tell us the exact key(s) you have deleted, so other people can try the same when they find this topic?

Yes!

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\

under there, there should be a folder for TLS 1.3; deleting it is what solved the problem!

Thank you, much appreciated