1 Message

 • 

70 Points

Sunday, November 1st, 2026

Problem with Connection

My existing Wyoming Canvas website uses Homestead SiteBuilder. HTTP works, but HTTPS gives ERR_CONNECTION_REFUSED. The main domain points to 216.40.47.17, and www points to websites004.homestead.com. Please diagnose HTTPS and explain how to secure this existing site. Before making changes, tell me whether DNS or nameserver changes are required, how email will be protected, and whether there is any cost. I must approve changes first.

Oldest First
Selected Oldest First

3K Messages

 • 

30.9K Points

12 hours ago

I have been asked by Homestead to corrrect my WHOIS data. There my postal address is incorrect. But in my Homestead account data, the address is correct. How can I correct the WHOIS data?
To correct your WHOIS data, you must update your Domain Contact Information specifically, as Homestead pulls WHOIS records from your domain's registration data rather than your main billing or account profile. [1]
You can fix this by updating the details directly in your dashboard: [1]
  1. Log into your account on the Homestead Portal.
  2. Navigate to the Domains tab or manager.
  3. Select your domain name and click Edit Contact Info.
  4. Update your postal address, state, and zip code with the correct details.
  5. Save your changes. [1]
⚠️ Crucial Step: ICANN policy requires you to verify contact updates within 15 days. Keep an eye on your email for a verification link from Homestead after saving. You must click that link, or your domain could face a clientHold suspension. [1]
Are you able to log into your dashboard normally, or has your domain already been suspended/placed on hold due to the incorrect data? I can give you alternative steps if you are locked out.
AI can make mistakes, so double-check responses
  • Homestead Technologies
    ‎Important Domain Information | Homestead Community
    ICANN policy requires verifying contact info updates within 15 days or face suspension. services resume within 1 to 48 hours. Emai...
  • Homestead Technologies
    Account: Update Domain Contact Info - Homestead Community
    WHOIS data is collected from the information that is on the domain registration. To update WHOIS info, update the domain contact i...
My existing Wyoming Canvas website uses Homestead SiteBuilder. HTTP works, but HTTPS gives ERR_CONNECTION_REFUSED. The main domain points to 216.40.47.17, and www points to websites004.homestead.com. Please diagnose HTTPS and explain how to secure this existing site. Before making changes, tell me whether DNS or nameserver changes are required, how email will be protected, and whether there is any cost. I must approve changes first.
My existing Wyoming Canvas website uses Homestead SiteBuilder. HTTP works, but HTTPS gives ERR_CONNECTION_REFUSED. The main domain points to 216.40.47.17, and www points to websites004.homestead.com. Please diagnose HTTPS and explain how to secure this existing site. Before making changes, tell me whether DNS or nameserver changes are required, how email will be protected, and whether there is any cost. I must approve changes first.
The Diagnosis:
The ERR_CONNECTION_REFUSED error occurs because your classic Homestead SiteBuilder hosting environment (pointing to the legacy IP 216.40.47.17) is only configured to listen to standard HTTP traffic (Port 80). It does not have an SSL certificate installed, and its web servers completely block or reject requests attempting to connect over secure HTTPS (Port 443). [1, 2]
Homestead only provides native, free, one-click SSL certificates for websites built on their newer platform, WebsiteBuilder. They do not natively support or generate SSL certificates for legacy SiteBuilder / SiteBuilder Plus environments. [1, 2]
To secure your existing site without breaking it or rebuilding it from scratch, you have to use a workaround officially recommended by the Homestead community: routing your traffic through a third-party proxy provider like Cloudflare to act as the secure bridge. [1, 2]

Required Changes & Requirements Check
Before you proceed, here is the exact breakdown of what is required based on your criteria:
  • Nameserver Changes Required? Yes. To route your site safely, you will need to change your domain's nameservers inside your Homestead domain registry to the custom nameservers provided by Cloudflare.
  • DNS Changes Required? Yes. Your active DNS management will move to Cloudflare. You will mirror your current setup there, keeping your root domain pointing to 216.40.47.17 and www pointing to websites004.homestead.com. [1]
  • Will Email Be Protected? Yes. When migrating your DNS settings over to Cloudflare, you must copy your current email records (MX records, TXT/SPF authentication records) exactly as they are. Once copied, your email routing will remain uninterrupted and fully operational. [1]
  • Is There Any Cost? No. Cloudflare provides a robust Free Tier plan that includes free SSL/TLS encryption, which is entirely sufficient for securing your legacy SiteBuilder site without any added costs. [1]

Step-by-Step Security Plan (Pending Your Approval)
If you approve this direction, these are the steps we will take to implement the fix:
  1. Create a Cloudflare Account: You will sign up for a free account and add your domain name.
  2. Scan and Copy DNS Records: Cloudflare will automatically scan your existing DNS setup. We will manually double-check to ensure your A record (216.40.47.17), CNAME (websites004.homestead.com), and all current MX/Email records match your Homestead dashboard exactly.
  3. Update Nameservers in Homestead: You will log into your Homestead portal, go to your Domains tab, and swap your current nameservers out for the two new ones assigned by Cloudflare.
  4. Configure SSL to 'Flexible': Because your backend Homestead server doesn't accept HTTPS directly, you must toggle the Cloudflare SSL setting to Flexible. This encrypts the path between your users and Cloudflare, eliminating the ERR_CONNECTION_REFUSED error.
  5. Enforce HTTPS: Once the free certificate goes active (usually within a few hours), you will turn on Cloudflare's "Always use HTTPS" and "Automatic HTTPS Rewrites" settings to seamlessly force all legacy HTTP traffic into your new secure site.