No internet connection
  1. Home
  2. Technical Support

(Resolved) Certificate error after Windows reinstall (cert has been re-added to Windows)

By Don Eitner @FreihEitner
    2024-10-04 02:15:38.694Z

    I have been happily using my TinyPilot KVM until I was recently required to do a full Windows 11 23h2 reinstall. I followed the steps to fix browser privacy errors, and the tinypilot-ca cert is listed in certmgr under Trusted Root Certification Authorities which says the certificate is OK and valid from 2023 until 2033 (today is October 3, 2024). I even restarted Windows after installing the cert, but when connecting to the web interface via Chrome I am getting NET::ERR_CERT_AUTHORITY_INVALID, This server could not prove that it is tinypilot.local; its security certificate is not trusted by your computer's operating system.

    I get slightly different errors when using Firefox, but for this I normally do use Chrome. I am able to go through advanced and bypass, and TinyPilot works fine then, but this forces it to run inside a tab of my main Chrome window rather than being able to run as a Chrome app in its own window, and I still need to do this each time I access the web interface.

    If there's any logs or screenshots which would help troubleshoot, let me know what you need. Thanks again.

    Reply
    • 2 replies
    1. F
      Don Eitner @FreihEitner
        2024-10-04 08:05:22.390Z

        This is resolved. It was at least partially on me. Last year I had this question about copying a certificate from one SD card to a backup SD card (RESOLVED Copy cert and key to 2nd microSD card) and I just tried by pulling the /ca.crt file from the card which had been in storage since last year and installing that into Windows instead of the one I had been using. Now TinyPilot's web interface loads successfully, with HTTPS security, for both SD cards.

        Evidently although I made my backup card work with the certificate I previously had stored in Windows, when pulling the certificate from that 2nd card it's not the same one that it actually uses... or something.

        Reply
        1. David @david2024-10-04 10:45:32.262Z

          Hi @freihEitner, I'm sorry you ran into this cert issue.

          Thanks for the update on resolving this! I'm unsure why you saw this behavior if both ca.crt files were identical. It's possible there could have been an issue with the first cert install on the fresh Windows installation or something similar.

          Please feel free to reach out again in future if you have any questions.

          Reply
        2. Progress
          with handling this problem
        3. F@FreihEitner marked this topic as Done 2024-10-04 08:05:46.976Z.
        Reply (discussion)Add progress note