The only problem here is that your domain http://readyreview.cf/ is not pointing to InfinityFree, take a look yourself here:
Go to the Cloudflare Dashboard (located here: dash.cloudflare.com).
Head to your domain and then click on “SSL/TLS”.
Make sure you have the SSL Mode “Flexible” selected, Full & Full (strict) will break your website (throw are like the one above).
The setting should look like this:
I want to remove cloudflare from my website it causes many error and the main is sitemap couldn’t fetch on Google if cloudflare is joined so that’s why I deleted my website from cloudflare completely and change the name server from the origin of domain…to infinity servername… And I receiving this error hope u understand this time…
The reason why Cloudflare is causing errors, is because it is misconfigured. To fix this, change the setting I showed above.
If you want to remove Cloudflare, go to the Cloudflare dashboard, click on the domain property and go to “Remove Website from Cloudflare” OR go to the panel, click on Cloudflare, select your domain and click on “Alter Cloudflare” and then on disable Cloudflare.
It could take some time until Cloudflare is fully removed from your site.
Men… I already told you I removed my website from cloudflare and I changed the name server… to infinity host name server and it’s already 36 hr my website not opening and other hand I know how to add ssl in website through cloudflare… But now I wanted to remove and I did but after that website not opening
Which website are you talking about? You have sent to different links above.
I am sorry I am talking about reviewforsale.cf
Okay, so the problem with this domain is that it does not point to InfinityFree.
You can take a look yourself here:
So how can I point brother… I already done and it’s already more than. 36™hr… please guide me …and I didn’t understand that website that u suggest
Go to your domain registrar, and edit your nameservers to:
ns1.byet.org
ns2.byet.org
ns3.byet.org
ns4.byet.org
ns5.byet.org
Please note that some domain registrars require you to make changes at your host before you can edit the nameservers; these will not work with the free hosting platform.
For me it points to the right nameservers (either Epizy or Byet nameservers are the same, but for the SSL certificates tool to work it’s better to leave Epizy nameservers), as shown from this dig output:
; <<>> DiG 9.16.1 <<>> ns +trace reviewforsale.cf @1.1.1.1
;; global options: +cmd
. 509613 IN NS a.root-servers.net.
. 509613 IN NS b.root-servers.net.
. 509613 IN NS c.root-servers.net.
. 509613 IN NS d.root-servers.net.
. 509613 IN NS e.root-servers.net.
. 509613 IN NS f.root-servers.net.
. 509613 IN NS g.root-servers.net.
. 509613 IN NS h.root-servers.net.
. 509613 IN NS i.root-servers.net.
. 509613 IN NS j.root-servers.net.
. 509613 IN NS k.root-servers.net.
. 509613 IN NS l.root-servers.net.
. 509613 IN NS m.root-servers.net.
. 509613 IN RRSIG NS 8 0 518400 20200429050000 20200416040000 48903 . B8ZA0RN46DQZ9JybsaAyboyfbICqhACobd/ziLyZuLD7gdYUCtuh0qqi RLS6kGqSc10P0T4QiguFGP7MJxvsFNBaRXaqLqNXbqqGgFZQEjCrtIGw nnTqSOG2CLxDLcLTITXKu/0pb+6lQRRnkrgiRu8ObBVh8hwWuuxBAga3 nsZCA+AkkN0K5NQ7NCKhipvtpFTfctFxpym6l3NrbbEoz1+laNu4b+63 PkxnDNPQXvTpFqtawSajnplVxJp5b+Z9UKiNkNEMiEVAM1ROJaRbS/7l gE44nl/Elr0AKldORfEJO/F8BrzK+gDytJ918GTTXCEasKv2dWu2eE8Q DfuA1w==
;; Received 525 bytes from 1.1.1.1#53(1.1.1.1) in 40 ms
cf. 172800 IN NS a.ns.cf.
cf. 172800 IN NS b.ns.cf.
cf. 172800 IN NS c.ns.cf.
cf. 172800 IN NS d.ns.cf.
cf. 86400 IN NSEC cfa. NS RRSIG NSEC
cf. 86400 IN RRSIG NSEC 8 1 86400 20200429050000 20200416040000 48903 . OiL4Qsm+oFAllJYQpgueVR2ge2V/jXZL3GtZP+oJw1pL+WZ4a7mNMj3V HodBKPPUZ+tjhKOkvXRzLD25nlJ6Y7/U78NQx1DO9+gey9P4sVHQia3B opud6z3IM5rRv7fdLK9sdmbgYuQy8MB8dERbuh2f4gK4X8U6N6RWgrpu q71/E4aEnOoy7pbMYqand/jJu0Ok2TmkeI4zIjxLYCYnvqMfr242AmFk 9fcSHe01JLq94oUWSUfGngK4DFBgxNoJ1Xx/SE+dwIfx7VrPKKzwsJRS 88UmFGDRoamm2H+2F4KKImpxRtpXgtgq9OAAjc9cPNqJYOZfWUtkHXca KJD8kQ==
;; Received 600 bytes from 199.7.91.13#53(d.root-servers.net) in 49 ms
reviewforsale.cf. 300 IN NS ns1.epizy.com.
reviewforsale.cf. 300 IN NS ns2.epizy.com.
;; Received 90 bytes from 185.21.168.17#53(a.ns.cf) in 79 ms
reviewforsale.cf. 86400 IN SOA ns2.epizy.com. support.reviewforsale.cf. 2006112402 28800 7200 604800 86400
;; Received 102 bytes from 185.27.134.7#53(ns1.epizy.com) in 109 ms
but it shows a SSL protocol error. To replicate my same result, try to put “Trace” on DigWebInterface too.
@Jatin9911 To fix the SSL protocol error try to install a SSL certificate for your domain on your hosting account. To generate one you can use the “SSL Certificates” section of the Client Area for that. After generating the SSL certificate, you need to install it on your hosting account, and the KB article shown on the generated certificate page helps you do that.
I don’t wanna install ssl any alternative way … or should I again go back to cloudflare
Then change the URL from HTTPS to HTTP from your database’s phpMyAdmin. For WordPress that’s explained here, even though this article has a different error than yours, but this article lets you also fix different SSL errors.
Thanks alot after changing url my site open after 1 hour…
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.