Friday, April 13, 2018

All my blog custom domains (Wordpress and Blogger) now have https enabled



I have updated all four (the three remaining) Wordpress blog domains and the three Google custom domains.
  
The Google domains were easy. You just check a box in settings for each corresponding Blog, wait about an hour for propagation, and then check a second box to autoconvert all accesses to https.
   
For Bluehost Wordpress hosting, now you can do multiple domains within one cPanel.
  
One of the domains had minimal SiteLock protection, and that one took the free SSL certificate. Two others, that are newer, have SiteLock CDN (similar to Cloudflare). For these, you have pay for Positive SSL (about $5 a month) and assign a new IP address for the domain (or remember to ask the support technician to do so – not everyone knows this yet).  You then wait for the new IP to propagage. You can check the progress of the propagation on “whatsmydns.net”.  It helps to reload it a few times;  that seems to prompt progress.  The site will go to your BlueHost panel as a redirect or give database errors on https until the entire propagation all over the world is done.  During the propagation, it is possible for foreign servers, especially, to reject your IP address, but this will not prevent the rest of the locations from working.  There seems to be at least one server for every telecom company around the world.  There are many server sites in non-democratic countries.

I hope later that SiteLock will cause the automatic conversion to https to happen.  I am told it is supposed to.   
  
 China blocked one of my domains (the movie reviews).  Maybe that’s retaliation for Trump’s tariffs, or maybe that’s because I had reviewed some films about dissidents (Weiwei).  I don’t think I threaten Xi Jingping’s being god-king for life. 

I've noticed that Trend Micro, at least, does not automatically mark https versions of green http sites as green; it seems to view them as new domains.  This seems illogical. 

No comments: