We thought that we can share it here as there were too many responses from our Bloggers + Nuffnang friends (particularly) in Singapore -- you know who you are -- received via mail in the past week or so. Due to our tight schedule attending clients custom themes & website/blog projects, we could send the links to this post for further reference.
If you are serving ads from Nuffnang or any blog-ing advertising network, these services may deploy ads/assets using the HTTP url protocol. This is (some) of the main reasons why after troubleshooting, you're still wondering why the insecure warning is shown.
If you are using Windows, when viewing your blog pages, hit the F12 key & view your web browser Console Panel. You can view warnings like so:-
Mixed Content: The page at 'https://<your-blog>' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Fenix'. This request has been blocked; the content must be served over HTTPS. (anonymous)
Mixed Content: The page at 'https://<your-blog>' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Fenix'. This request has been blocked; the content must be served over HTTPS. (anonymous)
Mixed Content: The page at 'https://<your-blog>' was loaded over HTTPS, but requested an insecure image 'http://eccdn1.static.nuffnang.com.my/assets/img/my/nuffnang_footer_2.png'. This content should also be served over HTTPS.
Mixed Content: The page at 'https://<your-blog>' was loaded over HTTPS, but requested an insecure script 'http://eccdn1.static.nuffnang.com.my/assets/ads/1112841/1201481.js'. This request has been blocked; the content must be served over HTTPS.
We have highlighted the assets or ads served by #nuffnang where it continues to use the HTTP in its URL protocol. This causes the Mixed Content issues & your blog pages will continue to display the Insecure Website dreaded warnings if it is not taken care of.
What Can You Do About these Ads?
Unfortunately, you can't do anything about the ads (or assests) served by Nuffnang. It is included dynamically to your blog pages & handled by Nuffnang servers/application.
You can send Nuffnang a support ticket, but based on our readers experiences -- the sent mail/inquiry did not get any response - for months!
You probably can hit Nuffnang up via their socials for example their Facebook Page, Instagram or Twitter & hopefully your plead will be heard -- rather then waiting for the right personnel to handle this (easy) task for updates.
Temporary measures -- you can also apply this simple Blogger HTTPS adjustments at your Blogger powered blogs to prevent Nuffnang ads displayed on your HTTPS version of your blog. Our readers have found it was useful -- possibly it may help you!
Image courtesy pixabay.com -- CC0 Creative Commons
Hope you find this useful!