_3X3C

Hi there, did you read the entire post? This wasn't a question at all (im new to this forum..maybe its not the right category) - it was a solution for all these unsolved threads and knowledge base articles that don't solve this problem in the long term. It's not corrupted data, missing admin-rights, rebooting services or routers, or re-installing VC or .NET Runtimes - these things just randomly solve the problem. After trying out these things (https://truckersmp.com/knowledge-base/article/786 or or Solutions 1 to 3 from Million 88) i had the problem over and over again till i finally found a permanent way. The problem is, that the SSL Revocation Service can't be reached: IP: 93.184.220.29 (and all the other IPs from Digicert mentioned above) Port: 80 must be accessible from your computer and the problem is finally solved! Maybe u can add this to your Solutions / Knowledge Base articles - or give it to Support to verify this when the next problem occurs. Sure - not every user is a techie and able to do this - maybe the Standard-solutions like "turning it off and on again" are better for them. But there should be an indicator in these articles what the problem really is! Thank You, _3X3C

Hello everyone, this is for discussion or to let the Support-Team know because of all these unsolved threads regarding this topic - i finally found a possible solution or at least could identify the problem when the Login to TruckersMP fails: The Error Messages will never be shown completely - possible Errors are: InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline. Background: While the programm starts, the SSL-certificates are checked if they are still valid. When the problem occurs, specific Server-IPs can't be reached. Sometimes a Server is really offline or Client-ISP has routing problems, mostly its local problems: Check your local network for blocked IPs and packets: Firewall / DNS / AntiVirus-scanner / wrong Systemtime - there are several possiblities why packets get blocked. In my case its mostly my local PC-Firewall which blocked access to the official Digicert Certificate Revocation List: DNS: http://ocsp.digicert.com IP: 93.184.220.29 Port: 80 Protocol OCSP (Online Certificate Status Protocol) Involved Windows-Processes: System, lsass.exe Possible other IPs are: 192.16.58.8 117.18.237.29 72.21.91.29 Click here for official information from digicert: https://knowledge.digicert.com/generalinformation/INFO4629.html Greetings _3X3C

Hello everyone / Hallo zusammen, i finally found a possible solution or at least could identify the problem when the Login to TruckersMP fails: / endlich habe ich eine mögliche Lösung bzw. zumindest die Ursache für das Login-Problem bei TruckersMP gefunden: The Error Message will never be shown completely / Die Nachricht wird nie komplett angezeigt. Possible Errors / Mögliche Fehler: InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate / Die Sperrfunktion konnte keine Sperrprüfung für das Zertifikat durchführen. InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline. Background: While the programm starts, the SSL-certificates are checked if they are still valid / Hintergrund: Die SSL-Zertifkate werden bei Programmstart auf Gültigkeit überprüft (oder ob zurückgezogen). When the problem occurs, a specific (and chancing) Server can't be reached / Wenn das Problem auftritt kann ein bestimmter (sich ändernder) Server nicht erreicht werden. I will provide some Logs when the problem happens again / Wenn das Problem erneut auftritt, werde ich hier noch passende Logs anfügen. Sometimes the Server is really offline or Client-ISP has routing problems / Manchmal ist der Server wirklich nicht erreichbar oder am Client-Provider treten Routing Probleme auf. Lösung für lokale Probleme: Lokales Netzwerk überprüfen auf blockierte IPs und Pakete: Firewall / DNS / Virenscanner / falsche System-Uhrzeit usw. - Auslöser kann vieles sein - je nach Netzwerkaufbau. Solution for local problems: Check your local network for blocked IPs and packets: Firewall / DNS / AntiVirus-scanner / wrong Systemtime - there are several possiblities why packets get blocked. In my case its mostly my local PC-Firewall -> i set it temporarly to "all through" and the Problem is gone for a while / In meinem Fall ist es meistens immer die lokale PC-Firewall, einmal kurz auf "darf alles raus" und es funktioniert wieder. Greetings / Grüße _3X3C