Hi, I’m trying to install and connect to my Misskey instance and I’m facing an ERR_CERT_AUTHORITY_INVALID error. I tried following the instructions in this link ( but it didn’t work. I used the certificate and key provided by Cloudflare. The path of certificate is correct, I restarted nginx, but why doesn’t it work? Any answers would be appreciated. I am attaching a picture for your quick understanding.

image alt text
image caption
image alt text
image caption
server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;

    ssl_session_timeout 1d;
    ssl_session_cache shared:ssl_session_cache:10m;
    ssl_session_tickets off;

    # To use Let's Encrypt certificate
    ssl_certificate     /etc/ssl/certs/cert.pem;
    ssl_certificate_key /etc/ssl/certs/cert.key;

    # To use Debian/Ubuntu's self-signed certificate (For testing or before issuing a certificat>
    #ssl_certificate     /etc/ssl/certs/ssl-cert-snakeoil.pem;
    #ssl_certificate_key /etc/ssl/private/ssl-cert-snakeoil.key;


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Site Moderator
Site Moderator badge
January 21, 2024

Heya @44a03fe70a384a7ca7abc3b64e2e72,

The error message you’re encountering, NET::ERR_CERT_AUTHORITY_INVALID, indicates that there might be an issue with the SSL certificate or its configuration. This error is not because you’re using a free Let’s Encrypt SSL certificate, as they are trusted by most modern browsers.

Here are a few things that I could suggest:

  1. Check the SSL certificate and key paths to ensure they are correct and the files exist:
ls -lah /etc/letsencrypt/live/domain/fullchain.pem
ls -lah /etc/letsencrypt/live/domain/privkey.pem
  1. Restart Nginx after making any changes to the configuration file:
sudo systemctl restart nginx
  1. Ensure that your domain’s DNS settings are correctly pointing to your DigitalOcean droplet’s IP address. You can use this tool to check that:

If the issue persists, you may want to consider reissuing the SSL certificate using Certbot or checking the Certbot logs for any errors. You can do that by running the certbot command again.

Let me know how it goes!

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel