(Topic ID: 247220)

Certificate error accessing Pinside from Android Chrome

By barakandl

4 years ago


Topic Heartbeat

Topic Stats

  • 18 posts
  • 16 Pinsiders participating
  • Latest reply 4 years ago by Murphdom
  • Topic is favorited by 1 Pinsider

You

Linked Games

No games have been linked to this topic.

    Topic Gallery

    View topic image gallery

    Screenshot_20190713-215444_Chrome (resized).jpg
    Screenshot_20190713-215506_Chrome (resized).jpg

    You're currently viewing posts by Pinsider jabdoa.
    Click here to go back to viewing the entire thread.

    #17 4 years ago
    Quoted from pinball_ric:

    Can you elaborate more? I'm new to lets encrypt and it's used on a web server at work. Someone before me set it up but i just used it to get a new cert since we were able to secure an addtional domain. Is there something I should keep an eye out for on why it failed? Were there any warning signs it wasn't renewing properly. I assume it tries to renew multiple times before the cert fully expires.

    They use lets encrypt which completely automates the certificate renewal process for you. Certificates are usually valid for 90 days and renew 30 prior to expiry. However, the client sometimes fails or requires attention (i.e. because of new ToS). Monitoring certificate expiry should catch this but probably did not exist or failed for pinside.

    You're currently viewing posts by Pinsider jabdoa.
    Click here to go back to viewing the entire thread.

    Reply

    Wanna join the discussion? Please sign in to reply to this topic.

    Hey there! Welcome to Pinside!

    Donate to Pinside

    Great to see you're enjoying Pinside! Did you know Pinside is able to run without any 3rd-party banners or ads, thanks to the support from our visitors? Please consider a donation to Pinside and get anext to your username to show for it! Or better yet, subscribe to Pinside+!


    This page was printed from https://pinside.com/pinball/forum/topic/certificate-error-accessing-pinside-from-android-chrome?tu=jabdoa and we tried optimising it for printing. Some page elements may have been deliberately hidden.

    Scan the QR code on the left to jump to the URL this document was printed from.