Siteground Hosting - Cloudflare as Registrar..Settings Please

I have been using Siteground Hosting for several years now, and WAS using Google as my Registrar. However as I am sure most of you know Google sold that service to SquareSpace aka GoDaddy. I changed the registrar to Cloudflare and was billed for the change WHOIS shows the domain as Cloudflare, but for the life of me I can’t figure out how to tell Cloudflare where my site is located.

Would love to see a simple…step b step set of instructions on how to do this.
Not great with CNAME, A Records etc.
I do have both the NS1 and NS 2 settings and the ip address of both of these. Also know the ip for the site

Any help would be appreciated. SquareSpace is useless with their help, and Siteground just marginally better.

Thanks

You can’t change your nameservers if using Cloudflare, so you can’t use the NS1 and NS2 records for Siteground on Cloudflare.

Enter the IP address you have as an A record in your Cloudflare DNS here…
https://dash.cloudflare.com/?to=/:account/:zone/dns/records

1 Like

Records resolve OK.

You need to set ssh, mail and ftp records to “DNS only” instead of “Proxied” as Cloudflare only proxies HTTP/HTTPS traffic (unless using Cloudflare Spectrum).

You also have “too many redirects”, so set your SSL/TLS settings “Full (strict)” here…
https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls

See…
https://cf.sjr.org.uk/tools/check?b560834a081d4f099cff385a41845765#connection-server-https

1 Like

I have 20+ other websites registered with Cloudflare, albeit hosted with Hostinger, and they all work fine. Is this a problem coming from Siteground?
Still not working. Not sure where all of the redirects are coming from
I wish there was a step by step video for Siteground. Excellent one for Hostinger that worked first time.

Still not working. Am I just not being patient?

Did you set SSL/TLS to “Full (strict)”? That being set to “Flexible” is the usual cause of circular redirects for newly added domains (and you should always use “Full (Strict)” anyway).

If you have set that, then something else is redirecting https://nevis1.com to https://nevis1.com. Check for any redirects in Cloudflare here…
https://dash.cloudflare.com/?to=/:account/:zone/rules/redirect-rules (scroll down and check the bulk redirects as well)
https://dash.cloudflare.com/?to=/:account/:zone/rules/rules

Then check your Siteground configuration for the same.

1 Like

Those Siteground DNS records will have no effect, you are using Cloudflare for your DNS now.

You can temporarily set the DNS record for nevis1.com to “DNS only”. After a short while for the IP address to update, see if the problem persists. That will confirm if the redirect is in your Cloudflare settings or those on Siteground.

[add]
Actually, the redirect is gone. Your site is giving 503 (from your origin, not Cloudflare) but also returning a page.
https://cf.sjr.org.uk/tools/check?b25718f8546c44808a6239215235ba44#connection-server-https

2 Likes

Still not working. Tried numerous changes tutorials, many conflicting ideas. Should I just move all of my domains to a different registrar?

Your site was working the other day (see the link it that post) apart from your origin returning a page with a 503 HTTP code which was something you’d need to fix there.

Seems it’s more broken now (HTTP redirects to https:// - no site given) and HTTPS times out, so whatever you’ve done, going back to what you had before would be best.
https://cf-dev.sjr.org.uk/tools/check?1c96e92caba14a058a6d08cb38f4fad3#connection-worker-http

Can you show a screenshot of your Cloudflare DNS records and any redirect or page rules you have set up?

1 Like

Is it better to just remove the site and start over?

Definitely don’t remove the site. That will mess up your domain registration, and most of the old settings will probably be retained when you re-add it.

You’ll need to take this one step at a time with a few minutes between for full propagation to undo whatever you did before.

Before I chose Cloudflare as my registrar, the site was working fine…it was in maintenance mode with a plugin. Siteground hosting was fine. It was due to SqareSpace hijacking my domain from Google domains that started all of this. I had moved about 20 other domains from Siteground to Hostinger which were with Google domains to Cloudflare…every one of those worked perfectly usually within in a hour or tow.

So frustrated and confused now I don’t even know where I am. The hassle was not worth the $80.00 a year savings

Sorry to hear that.

For now, just Pause Cloudflare, so connections will go direct to Siteground.

I need to get the domains away from Siteground as they have become so expensive, and there service has waned since I signed up when you could actually speak to someone. Now it TRIES to use AI which is useless.

At some point I will have to make this move. I also am now stuck for 50 days or so with Cloudflare.

Does cloudflare have any for hire services?

You can pretty good help here for free. Start with this:

1 Like

Didn’t like that at all… :face_with_spiral_eyes:

Oops.

The site at http://nevis1.com/ has experienced a network protocol violation that cannot be repaired.

The page you are trying to view cannot be shown because an error in the data transmission was detected.

Please contact the website owners to inform them of this problem.

Did you change the IP address in DNS? Your screenshot from earlier started with 35.215, and now it resolves to 99.83...

Just did that now. I thought that pausing Cloudflare would revert back

Well now I am back to where I started 4 or 5 days ago. :rofl: I think it must be Sitegound causing the problems. Had ZERO problems with Hostinger.

It’s not completely dead. If I make a request to https://www.nevis1.com at the same IP address, WordPress tries to redirect it to non-www.

Try adding a DNS record for www with that 35.215 IP address. That should get a tiny bit of progress at least.

Non www works fine. I started this site in 1996, and started using WordPress with it in maybe 2012? Lots of crazy changes since then.

Did my first WP site in 2006 when it was for blogging only…That will be my next site I have to move…also hijacked by Squarespace