I get "Certificate is not trusted because it is self-signed" error

This error occurs when your server uses a certificate it generated itself instead of one issued by a Trusted Certificate Authority (CA) like Sectigo .

  • The Cause: Browsers do not recognize the server as a valid authority, so they warn visitors that the connection might not be secure.
  • The Solution: To remove this warning, you must purchase and activate a Hostaday SSL certificate (DV, OV, or EV) . Once a trusted certificate is installed, browsers will recognize your site as secure and display the padlock icon.
  • self-signed SSL, trusted CA, browser warning, شهادة موقعة ذاتياً, Hostaday security, أمان الموقع, تحذير المتصفح.
  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

Why do I get "Common name mismatch" error in my browser?

The "Common Name Mismatch" error appears when the domain name on the SSL certificate does not...

SSL notifications in Chrome and their meaning

Google Chrome uses visual indicators to inform users about a site's security status : Padlock...

My SSL is installed, why do I get the warning ‘Not secure’?

If you see a "Not Secure" warning despite having an active SSL, it is usually due to Mixed...

Firefox error code: ssl_error_rx_record_too_long

This specific Firefox error typically means the browser expected a secure encrypted response but...