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 (https://www.digitalocean.com/community/questions/getting-err_cert_authority_invalid-error) 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.
server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name anarkia.dev;
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;
source: https://misskey-hub.net/en/docs/for-admin/install/resources/nginx/
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!
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:
- 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
- Restart Nginx after making any changes to the configuration file:
sudo systemctl restart nginx
- 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!
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.