Featured Post

Pi Network Application It's Now Available For Windows and Mac Computer

 Pi Network application is a cryptocurrency data mining using your mobile phone that you'll enable to earn income using the pi coins th...

Perfect Remedies how to Change http to New https Protocol and Common Issues

HTTPS_Protocol



Hypertext Transfer Protocol for Secure communication (HTTPS) is required on the world wide web or in the internet world over networks of the computer. The main purpose is to secure data over the communication protocol is encrypted by means of using the Transport Layer Security (TLS).

Google this time provides free certificates of Secure Layer (SSL) Certificates to comply with this new protocol over the internet to all bloggers that have a custom domain. Rather than only to the subdomains that automatically settled to the new HTTPS protocol under the Blogspot domain.

Changing HTTP to the new HTTPS protocol is not simple, because probably you will encounter mixed content from the previous posting of your articles. And most probably to your images that link to different sites or in blogger itself.

So meaning before changing HTTP to HTTPS protocol you need to check first all your previous posts that don't have HTTPS, you need to change it manually. Including all the links that belong to your site's navigation menus, including the static pages. In this case, it's very hard to scan hundreds of pages, but thanks to whynopadlock.com help to scan pages and post sites for a mix of contents. BELOW ARE THE REMEDIES HOW TO CHANGE HTTP TO HTTPS

1. HOW TO CHANGE HTTP TO HTTPS USING YOUR BLOGGER DASHBOARD

Blogger

  1. Open your blogger dashboard and click Settings on the right-side panel.
  2. Then click basic.
  3. Now below Publishing, it has HTTPS availability, click the no link beside it.
  4. Then select YES.
  5. So when HTTPS now is a turn-on, you need to redirect your contents from HTTP to HTTPS protocol. Below under it, you have HTTPS redirect, change the NO to YES. Then wait several minutes or hours to fully propagated your new URL protocol.
  6. Now if you see your HTTPS is propagated, click the view blog of your dashboard. And check if the padlock is green and said secure. (Note: If this padlock is not available, your site has a mix of contents and needs to fix it before the HTTPS is fully functional and all your contents are fully encrypted.)
  7. But if the padlock is green meaning your site HTTPS protocol is fully functional.

2. FIXING MIX CONTENTS USING WHYNOPADLOCK.COM

Why_no_Padlock

After successfully enabled, your HTTPS and after viewing your blog, the HTTP's have no padlock, follow the below list of the remedies.

  1. Open the whynopadlock.com
  2. Copy your blog URL, and paste it into the secure address bar.
  3. Check box the I'm not a robot.
  4. Then click the test page.
  5. Below you will see the mixed content results.
  6. Copy and paste the mixed content URL and paste it in your browser address bar. Then you will see the image link that has no HTTPS.
  7. All you need is to find the post or article having the links or image links that have HTTP. Put manually the letter s of HTTP to became HTTPS.
  8. Change your post settings to HTML, and find and change HTTP to HTTPS.
  9. Then save your post.
  10. Repeat the procedure until all the Soft Failure of mix content post is all finished.
  11. Check again using why no padlock if there are no soft failure results. Then view your blog again if the padlock is enabled now or the color green and secure.
3. TOO MANY DIRECTS ERROR AFTER VIEWING BLOG SITE USING YOUR BROWSERS

  1. This is the failure of your hosting provider, if you're using a free hosting provider like CloudFlare this is a common problem. You need to purchase a SSL certificates to complete the settings of https.
  2. If you don't have budgets to buy this certificates using cloudflare, I suggest disconnecting your cloudflare account and call your hosting provider to redirect your domain to your blogger account.
  3. In the procedure above base on my experience, too many redirects, errors will solve 100 percent.

4. NAKED URL OR WITHOUT WWW IS NOT ACCESSIBLE IN MY BLOG SITE

This is not an error or failure, if you remember before the HTTPS you can type your URL like this, example.com rather than www.example.com. Because common our internet users will type the URL without the www. So meaning we need the www.example.com to redirect at example.com.

In this case, Blogger or Google not provided the free SSL certificates with the naked domains. So try below remedies to fix this URL setting.

  1. Inform your hosting or domain provider, example hostgator.
  2. Use the Chat or email to inform them.
  3. And use this statement to help them to understand what you need:
"I need to correct my site DNS address". Forwarding not working properly in my blogger account. I need to use the CNAME referral both the domain root and www host".

TIPS!

Before any changes to your blog, use the draft.blogger.com for beta testing as you test your blog if it is not fully or fully functional, like the new HTTPS protocol.

No comments:

Post a Comment

Note: We have Zero Tolerance to Spam. Avoid Promotions with 'Links' considered as spam will be deleted immediately upon our review.

MAY YOU LIKE THIS POST!