How to deal with SEC_ERROR_REVOKED_CERTIFICATE
Recently I had a problem with my Caddy server . I wasn’t aware that it’s related to Caddy - the initial thought was that something went wrong with the SSL certificate. But I was wrong. The message was pretty “platonic”
Error code: SEC_ERROR_REVOKED_CERTIFICATE
I’ve been avoiding Docker for a very long time. I started as a sysadmin setting up servers running FreeBSD and early versions of Debian on bare-bone servers. As soon as “cloud” came into the market, I switched to AWS and GCE and have used them since then. EC2 was my always goto choice to deploy something on the internet quickly. But Docker — for some reason, I was avoiding it until this two years ago, when I started using it. Without too much trust.
But today, history is not about my love & hate relationship with Docker, but about deploying the GO application and VIPS library. A couple of problems appeared during the process, and it’s worth mentioning them for future generations because I could find much help around my issues.
links to clear cached records in popular public DNS servers:
Dealing with DNS changes can be annoying and frustrating. Changes are not visible straight away, you have to wait to see them. Thet are not even. Here you can find links to clear cached records in popular public DNS servers:
You can check results here:
Tesseract it’s a great library Open Source library to supply free OCR solutions for multiple libraries. You can use it directly from command line, or in your own software using supplied libraries.
People say that FTP is dead. But not everyone knows or can use SFTP, SSH whatever to update their website. Sometimes you just need something as simple as good old FTP server on your instance. Let’s do it.
