I’ve been using Cloudflare as dns. I changed my server IP address recently and my domain cannot connect to the website in Hostinger. Hostinger surpport told me the Cloudflare proxy is preventing my domain to connect with their server.
What steps have you taken to resolve the issue?
I have contacted Hostinger surpport for help. First they told me to Pause Cloudflare on Site, and the domain could connect to the website after that. But everytime I un-pause Couldflare, the domain couldn’t connect. Then Hostinger surpport told me in this case, the reason behind this is the proxy from Cloudlfare. To ensure that the website is working after I unpaused the cloudflare, they asked me to edit the 2 DNS records and disable the proxy, and to check with Cloudflare to fix the proxy issues afterwards.
Follow the instructions on hostingers website under the Websites / Dashboard / Domain (Action Required) page lower section of the page where it states “Using the A record method” and they connect happily - I have quite a few Cloudflare & Hostinger domains all using Cloudflare nameservers and protection
Ignore hostingers silly error message:
This message is incorrect and, if you were cynical like me, is just a clear attempt to get you to use their name servers and them as your registrar - all my domains have this message displayed, and ignored, in their dashboards and the message can be completely ignored
One thing to watch - when you want to use the Security / SSL add certificate you need to set the domain as DNS only in Cloudflare, click the option to add hostingers SSL, then change it back to Proxied
Ignore any help you get from the stupid AI help bot as its absolutely useless
But my website can not open when Hostinger shows this error message, so I cannot ignore it.
My setting was DNS only with one A record and one CNAME record, but once I turn on the proxy, the Hostinger error message shows up later.
If you follow hostingers instructions you should have;
TWO proxied A records: one for @ and one for www
FIVE DNS only CNAME records: autoconfig, autodiscover, and one each for a, b, and c DKIM,
TWO DNS only MX records
and FOUR TXT records: _dmarc, _domainkey, hostingermail1._domainkey, and a spf record
Dont rely on hostingers support for technical support
The silly “Domain isnt connected” message can be completely ignored as its just because the way they “check” your domain is connected is to use either a blank User Agent, which gets them blocked, or go-http, which gets them blocked, or foreign countries with a less than stellar reputation to check from, which gets them blocked, so they then give the silly “not connected” message
And the silly message makes absolutely no difference to whether your domain will work or not - I have mail only websites with no A or CNAME records, all of the show “Disconnected” and, when hostingers email actually stays working, they work as email only
My other websites & email domains work using the setting just copied from hostinger when all of them display that message
What is the actual issue?
Does the site not work or is it that you just get their silly message?
I think you are right that is an SSL issue. I turned off the proxy and set as DNS only as you suggested, then I followed the instructions here Troubleshooting Cloudflare Universal SSL | Hostinger Help Center. After it, I changed back to proxied. Hostinger again shows the error message, but my website is back online. So far the website is still running.
Hostingers instructions are incomplete and they should include that in the adding an SSL step
Their support is almost non-existent, probably based on their low pricing, and they dont seem to know the basics of how their own systems work
Biggest issue for us and our customers is that hostingers mail servers fail regularly - that said their hosting is pretty good and has plenty of options but their mail systems are an absolute joke, and appear to be unsupported judging by my recent experience
As above, ignore their silly “disconnected” message as its just a sales thing
