Aurora Bug Reports Discussion

Would be nice if possible to run Aurora.exe in debug mode or console command to give more details in the log file as its pretty useless info for finding out the problem.
Failed to contact CH server
Exception: An error occurred while sending the request. (What error ?)
This is like telling your car mechanic "The car failed to reach the garage because of an error in the car", Instead of saying, "The car failed to reach the garage because a nail caused a puncture in the near side tyre"
Cheers.

[Edited by excalibre26, 9/14/2022 2:38:50 PM]

[Edited by excalibre26, 9/14/2022 2:46:53 PM]

Sometimes there IS no more information supplied to Aurora regarding the inability to connect. You obviously can ping all servers so something on your end is blocking the APP, not the connection. That should give you enough to go on.

C:\WINDOWS\system32>ping www.cheathappensnext.com

Haciendo ping a www.cheathappensnext.com [172.67.70.214] con 32 bytes de datos:
Respuesta desde 172.67.70.214: bytes=32 tiempo=60ms TTL=56
Respuesta desde 172.67.70.214: bytes=32 tiempo=59ms TTL=56
Respuesta desde 172.67.70.214: bytes=32 tiempo=59ms TTL=56
Respuesta desde 172.67.70.214: bytes=32 tiempo=60ms TTL=56

Estadísticas de ping para 172.67.70.214:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 59ms, Máximo = 60ms, Media = 59ms

C:\WINDOWS\system32>



Haciendo ping a www.ch-downloads.com [172.67.70.189] con 32 bytes de datos:
Respuesta desde 172.67.70.189: bytes=32 tiempo=60ms TTL=56
Respuesta desde 172.67.70.189: bytes=32 tiempo=59ms TTL=56
Respuesta desde 172.67.70.189: bytes=32 tiempo=59ms TTL=56
Respuesta desde 172.67.70.189: bytes=32 tiempo=59ms TTL=56

Estadísticas de ping para 172.67.70.189:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 59ms, Máximo = 60ms, Media = 59ms

C:\WINDOWS\system32>

were you able to solve

Translated: Google Translate

You can check if TLS 1.2 is disabled for some reason, this can also cause this error. Open registry editor and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols

Then check the ENABLED value of TLS 1.2

In Aurora version 1.4.2 (STABLE) I've added a way to output more information. But its not released yet.

[Edited by 0x90, 9/14/2022 9:26:46 PM]

Your a genius, that was the problem, for some reason TLS 1.2 was disabled, don't know how or what caused this change but many thanks for the great support on this forum and for the program.
MY SOLUTION
I have an old pc with a fresh install of win10 and looked at the registry value for the key KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols
On the old pc there are no subkeys but on my pc with the issue I had two subkeys TLS 1.2 and TLS 1.3 so I just deleted the two subkeys and all working again.

I don't suggest you do what I did and just delete keys in the registry at least not without backing it up first but this fixed the issue.

Many thanks to all for the support and input in finding a solution.
Cheers 😀

[Edited by excalibre26, 9/15/2022 3:15:04 AM]

Hello there,

I too have the same issue, as the author of the thread. I tried everything that was reported here, but was unable to solve the issue.

About the last option, to check the ENABLED value of TLS 1.2

It has the value of 1 (which should be correct), so is there any other measure, that I could try out?

Thank you in advance.

I tried this solution but it appears as activated, is there any other possible solution?