For example, if you redirect domainom to .domainom but installed an SSL certificate on .domainom, you may see the error net::err_cert_common_name_invalid on your screen.
To fix this issue, you can use any of the following methods:
Or you can purchase a different SSL certificate for the domain you are redirecting from.
4. Make sure your WordPress URL matches your website URL
There is a high chance that when setting up WordPress, you may have accidentally changed your site's address to S without an SSL certificate in WordPress. You may have tried to follow security best practices or simply explored the settings, but this can cause the NET::ERR_CERT_COMMON_NAME_INVALID error.
But solving this problem is not difficult.
Go to your WordPress dashboard.
Checking WordPress Address and Site Address Settings
Checking WordPress Address and Site Address Settings
Go to Settings > General.
Make sure your WordPress URL and website URL match.
Even after following the above steps, if the error persists, you may need to change your database address via phpMyAdmin or Adminer.
First, open your website’s phpMyAdmin control belgium telegram data panel and open the database by clicking on its name in the left sidebar. Then, find and open the “wp_options” table:
In phpMyAdmin, find the lines “ siteurl ” and “home”.
Checking siteurl and home strings in phpMyAdmin
Checking siteurl and home strings in phpMyAdmin
Edit these lines to change the addresses if necessary.
After editing, check if you can now access your site.
5. Check for browser extension conflicts
Sometimes a browser extension you have installed can cause the net::err_cert_common_name_invalid error. It can be difficult to determine which one is causing the problem unless you check each one individually.