Almost all CAs can secure both WWW and non-WWW variations with a single certificate. Certificates issued for example.com will almost invariably work for www.example.com (though the reverse is not often the case), as the latter is often in the SAN field of the certificate.
You’re more likely to be experiencing a mixed-content problem… but it’s impossible to be sure without testing the domain in question.
So if you need a definitive answer to your question and a resolution to your issue, please provide your actual domain so we can take a look and help you.
Standing by.
@wpadminvic
Please update your URLs from
home: http://www.mydomain.com to https://www.mydomain.com
siteurl: http://www.mydomain.com to https://www.mydomain.com
Or add these 2 lines in you .htaccess file
RewriteCond %{HTTPS} !=on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
before # BEGIN WordPress
Or use Really simple SSL plugin to set redirection
Thank you both!
WordPress admin page’s “Settings > General Settings” WordPress Address (URL) and Site Address (URL) are greyed out to prevent editing, so I updated the _options table in the database to change siteurl and home to use https://
However, upon reloading the WordPress admin page, it would still show http:// in the greyed out setting. There are some posts that states wp-config.php can overwrite the setting, but I don’t see any overwrites in that file.
Does WordPress need to be refreshed, or is there another overwrite somewhere in the file structure that points to http:// that overwrites the database records?
WordPress admin page’s “Settings > General Settings” WordPress Address (URL) and Site Address (URL) are greyed out to prevent editing,
You probably have the URLs defined in your wp-config.php file OR in your active theme’s functions.php file.
Both the php files checked out – no hard-coded urls.
However, while scrutinizing the DB, I noticed that all the posts and uploaded images have GUID of HTTP instead of HTTPS.
Also, the blog allows visitors to write to the author, and all the messages have a source_url that is HTTP: in the database. These contacts can be deleted in bulk, and most of them are spam anywawys.
Could this be keeping the URL setting greyed out, because of the dependencies with hard-coded paths?
