Error Message “Future home of something quite cool”


#1

I just Change the name server from Godaddy to Cloudfare then I tried to access my website (https://www.newfangledscoop.com/) then the message appears“Future home of something quite cool.” and I am unable to access website… When I turn the nameserver to default it works fine…
When I contacted Godaddy’s help, they said they don’t provide SSL certificate from any 3rd party
and if I do want an SSL certificate and convert my site into https then I have to pay them for the SSL certificate. So I want to install the SSL certificate manually but I don’t know how or Is there anything else I could do to make my website up and running and with an SSL certificate.


#2

https://www.ssllabs.com/ssltest/analyze.html?d=www.newfangledscoop.com&hideResults=on&latest
Looks like SSL is working to me.
When I visit the website a bunch of css and js is blocked because it tries to load it over http.
Where do you see “Future home of something quite cool”?


#3

It was showing earlier before I contacted Godaddy. But now what can I do to make my website look good ?


#4

The problem is that some resources (CSS and JS files) are loaded without HTTPS encryption. You need to change the http:// to either https:// or just // where you load the resources. Alternatively you can let Cloudflare do it for you: In the Cloudflare dashboard under Crypto, enable “Automatic HTTPS Rewrites” and “Always use HTTPS”. Hope this helps.

If you need help with HTTPS checkout this website. https://httpsiseasy.com/


#5

I did go to Crypto and enabled always use https but then also it is not working.


#6

Did you enable “Automatic HTTPS Rewrites” as well ?


#7

No, Should I?


#8

Thank U its working


#9

Yea why not give it a whirl? It should help with the mixed content warnings but might not remove them all.


#10

How shall I do that ? please guide me through


#11

Have a look at Troy Hunt’s video https://www.youtube.com/watch?v=aN4o5BtuTAk from https://httpsiseasy.com/


#12

I also suggest to enable HSTS: https://www.youtube.com/watch?v=mVzdEl5G0iM


#13

Could you suggest me any more of such videos where I could find a way to optimize my website because now I searched for PSI score of my website https://www.newfangledscoop.com/ and it is very low.


#14

Did you see by earlier reply about HSTS? Adding HSTS will improve your TLS score at ssllabs.com. Can you link me to your current (PSI) score?


#15

https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fwww.newfangledscoop.com%2F&tab=mobile

I want to improve the score and yes I watched the video of adding HSTS


#16

https://hstspreload.org/?domain=newfangledscoop.com
I am getting this error after I did HSTS


#17

Thanks, Page Speed Insights measures website performance. The sore depends mostly on your website and web server. I suggest looking into the Speed and Caching tabs in Cloudflare.
You can try the following:

  • Enable “Auto Minify” for CSS
  • Set “Browser Cache Expiration” to something higher maybe 8 hours?
  • Try to Enable “Rocket Loader”

For the HSTS error I suggest to create a “Page rule” -> https://support.cloudflare.com/hc/en-us/articles/200170536-How-do-I-redirect-all-visitors-to-HTTPS-SSL-


#18

If the site it broken disable the Rocket Loader. It might not be compatible, sorry. I think It was worth a try tough.

https://developers.google.com/speed/docs/insights/rules


#19

https://www.youtube.com/watch?v=mVzdEl5G0iM
I’m unable to perform the 3rd and 4th part of the video.
When I turn SSL to full it shows me the error “Future home of something quite cool.” But when I turn SSL to flexible my website runs properly but it shows connection not secure on top.
Help me perform the 3rd part of the video which is adding the meta tag and the 4th part where will I add the .pem and .key file in GoDaddy and how shall I bind them together.


#20

Enabling HSTS should be one of if not the last thing you do around SSL and then only if you have a strong reason to. If you don’t know what you’re doing technically or you make a mistake it can be an absolute pain to recover from while debugging and troubleshooting.