Page Shows When Using HomesteadCloud Address, But Not WWW.

My website comes up when using bid-gaming.homesteadcloud.com, but when I use www.bid-gaming.com I get a 521: webserver is down. When I use bid-gaming.com I get : This site can't be reached bid-gaming.com refused to connect. I did not have the www originally signed up for Cloudflare (I don't think), but after looking at all the help posts, I signed the site up and have since paused it because even after following all the directions and giving it a week, it still didn't work. When I do command prompt, www.bid-gaming and the homestead cloud are giving me ips that match and look to be through cloudflare, but when I do bid-gaming.com it looks like a regular ip.

I just looked up bid-gaming.homesteadcloud.com on the homesteadssl.com page and it shows that I can activate the ssl for my domain. Is this possibly what I need to do?? When I searched the www and the bid-gaming.com they both come back with " Domain can't be verified as it doesn't exist on builder". I have had multiple websites for yeeeaaarss through Homestead and have never had this issue before so I didn't want to mess with that until I get some advice. I had read before not to do that part until the https is showing, but I don't know what to look for anymore.

Any ideas on what I need to do or change? Do I just need to call on Monday and ask for help??

Any help would be greatly appreciated!!!

Responses

Oldest First

Selected Oldest First

russell5607

2.7K Messages

•

27.1K Points

22 hours ago

To redirect your Homestead website to a new domain name, log in to your Homestead Account Manager, go to the Domains section, select the domain to move, click Forward, and set the destination URL. Alternatively, use Domain Forwarding within DNS settings for a 301 redirect.

Homestead Technologies +3

Here is the step-by-step process:

Log in and Navigate: Log in to your Homestead Account Manager and click on the "Domains" tab.
Select Domain: Select the domain name currently associated with your Homestead site.
Configure Forwarding: Click on Forward or Manage Domains and choose "Forwarding Domains" or "Domain Forwarding".
Enter New Address: Add the new website URL you wish to redirect to and save changes.
Alternative (Pointer): If you purchased the domain elsewhere, you can use the "Use a Domain You Already Own" feature in the Domain section to point it directly, say users on Homestead Community.
Homestead Technologies +4

If you are transferring to a new host entirely, it is recommended to keep the old site active for a while to allow search engines to recognize the 301 redirect.

1

0

B

brandi8764

2 Messages

•

80 Points

I do not see the "Forwarding Domains" or "Domain Forwarding"on the Domains page. When I go onto the Websites Manager page, it does show www.bid-gaming.com under "Your Websites", and it brings up the picture of the homesteadcloud page, but like I said, the address doesn't work to bring it up. It's like there's a simple switch I need to flip somewhere...

Like

Reply

17 hours ago

0

russell5607

2.7K Messages

•

27.1K Points

16 hours ago

www.bid-gaming.com

Did you recently attempt to install Cloudflare? Review your installation.

Error 1014: CNAME Cross-User Bannedis a Cloudflare-specific security error indicating that a DNS CNAME record points to a domain in a different Cloudflare account, which is restricted. To fix it, ensure your DNS target is valid, use Cloudflare for SaaS (SSL for SaaS) for cross-account setups, or remove the conflicting CNAME.

Cloudflare Community +1

This video explains the causes and solutions for the Cloudflare 1014 error:

58s

Kinsta

YouTube• Dec 30, 2022

Common Causes

- Cross-Account CNAME: A CNAME record points to a domain already on Cloudflare under a different user's account.
- Restricted Domain:
  Connecting a custom domain to a Cloudflare R2 bucket that has "Zone Hold" enabled.

Missing SaaS Configuration: You are attempting to use a subdomain that points to another Cloudflare user's SaaS provider without proper setup.
Propagation Delay: Changes to DNS records haven't fully updated yet, taking up to 48 hours.
Cloudflare Community +2

Solutions and Troubleshooting

Check CNAME Targets: Ensure the CNAME record points to a target that you own. If pointing to a third-party service, verify they support Cloudflare, says a user in the Cloudflare Community.
Use Cloudflare for SaaS: If you must point to a different account, the owner of the target domain must enable Cloudflare for SaaS to allow the cross-account connection.
Disable Zone Hold: If you're using Cloudflare R2, check the destination zone to see if a hold has been placed.
Remove the CNAME: Delete the conflicting record and use an A record instead, suggests a user on Reddit.
Wait for Propagation: Wait 24-48 hours to allow DNS changes to propagate, recommends 10Web.

0

brandi8764

Page Shows When Using HomesteadCloud Address, But Not WWW.

russell5607

brandi8764

russell5607

Related Conversations