Archived and Closed
This conversation is no longer open for comments or replies and is no longer visible to community members. The community moderator provided the following reason for archiving: Archiving inactive conversations.
I am going to assume, that the reason I am getting this error message is because I don't have my websites registered as a domain?
If this is correct, will my websites still be accessible to my customers?
They mostly are for information.
Another question sorta unrelated to this situation.
One of my websites is password protected, I started noticing a drop-down box appearing when you try and enter a password, I will embed it below.
I appreciate your relpy's.
NiceSeeingYou aka Keith
Yes you are absolutely correct. Since your sites are under site names, not domains, the Cloudflare set up does not apply to you. Your site will still be accessible, however, if you want the HTTPS option and to correct that second issue you posted, I would recommend rebuilding any sites you need to have HTTPS with, in our newer builder, Website Builder. Those sites (sitename.homesteadcloud.com) will be secure. We just cannot provide that with sites under Sitebuilder (sitename.homestead.com)
Your sites will also be mobile friendly and a lot more updated in the new builder. To start using it, just log in to homestead.com , click on Websites Manager > Add New Website > and give it a site name. Then Choose design and start rebuilding!
Thanks for the fast reply!
So are you saying in order for my websites to be accessible, they must now read mylearningcenter.homesteadcloud.com?
If you say yes, this will suck because I have spent years with it being mylearningcenter.homestead.com.
My customers will be lost, because their bookmarks won't work and neither will mine!
It's also on all my tens of thousands of business cards that are out in the world circulating.
I need to wrap my head around what is happening now.
Is my offline Site Builder not going to work anymore?
What you are suggesting is, I must recreate every webpage I have ever created, using your on line editor, and not the editor I have been using since 2001, am I understanding you correctly?
If I am, you have brought my worst nightmare to my demise!
if I don't convert my webpages to the "https" and to the "homestead.cloud" format, then my customers who access my webpages will get a warning box, that my pages are not secure which will probably scare them off correct?
Will my webpages even display after this "https" goes into effect, and I don't convert?
How long do I have before this will happen?
From reading many peoples comments on here, I am getting the impression that a lot of people knew about this change coming for some time, but I was left in the dark! :-(
There was no mention of this in any of the newsletters Homestead sent me, even though I read your newsletters faithfully!
The first I heard about this was via an e-mail from you "Homestead" dated 8-14-18.
Had I known about it sooner, like July 3rd, when my bill came do, I probably would not have renewed! ;-(
I appreciate your time and replies Elyzabeth
Your site will still display, the changes have already gone into affect. If you haven't seen much of an impact, you might not see a big impact. If it becomes an issue, you can certainly use Website Builder because we are able to make those sites secure. Otherwise, you can consider connecting domains to your sites to be able to use Cloudflare. This has been huge news coming from Google, not Homestead. We posted an article in Community with the instructions for setting Cloudflare up months ago, but since we could see not everyone was seeing it, we sent the email out to get peoples attention to the issue.
What a nightmare! :-(
Status: Website not active (DNS modification pending)
Please ensure your website is using the nameservers provided:
I worked hard at getting people to my sites and seeing the numbers climb over the years!
You are giving me the impression Elyzabeth, that when "Homestead" was sold the last time, that "you all" decided to stop using the "off line Site Builder, "that I been using for years!"
But you failed to tell the people who were using it, to stop using it, and to use the new one you created on line!
Had you done that, then either we would have started using the new one, or we would have quit Homestead! But we would have been better off than we are now, that is for sure.
I am disappointed in Homestead, for the handling of this situation this way, surely I can't be the only one who feels this way?
I am now 17 years older than I was when I started with Homestead in 2001, I just don't have the drive to alter every webpage I ever created! ;-(
Time will tell how that turns out for my business.
Call Keith aka NiceSeeingYou aka Keith