Using CloudFlare DNS with Weebly

[hoWIWeb]

Would anyone mind sharing a screencap or telling me how their A records are setup if they are using CloudFlare for DNS with Weebly. I've tried multiple things and still get publising errors on Weebly's side. Thanks.

[hoWIWeb · Accepted solution]

This is now resolved. CloudFlare uses proxies by default so when trying to setup Google Apps and other services that are looking for Weebly IPs it is seeing CloudFlare IPs. I don't have to use CF for this particular site so I can just update my registrar directly with Weebly IPs.

Thanks Adam for offering to help.

[Adam7]

What errors are you getting, @hoWIWeb? I know there are people using Cloudflare with us, although I don't know what instructions they followed or how they have things set up.

[hoWIWeb · Accepted solution]

This is now resolved. CloudFlare uses proxies by default so when trying to setup Google Apps and other services that are looking for Weebly IPs it is seeing CloudFlare IPs. I don't have to use CF for this particular site so I can just update my registrar directly with Weebly IPs.

Thanks Adam for offering to help.

[Adam7]

Ahh, that makes sense. Thanks for the update.

[stevenching]

Hi, I'm currently using Cloudflare with Weebly. and my site is saying that my A Records is not pointing to Weebly when it is actually is and protected by Cloudflare proxy. How do I resolve this issue?

[Queso]

Hello! Where are you receiving these messages currently?

[JIZZYDAWG]

this is UNBELIEVABLE!! seems like this same issue is going around and still no god damm answer! someone above said ti was solved with NO answer! No help from weebly on this either! I been going back and forth with them! they keep saying make sure the A record is pointed at weebly and IT IS! the site appears dosent it ! yes but the functions dont all work as they are not getting the correct inputs concerning ip address or somthbing that weebly should god damm well be able to explain! complete BS! 

[Adam7]

Which of your domains are you trying to use with Cloudflare? Using CF is a non-standard DNS setup, so it's a little more complicated to get working.

[hankchanocd]

Hi Adam,

I have the same issue here. I had my website nicely set up and the domain nicely pointed to Weebly IP. But when I decided to use the free SSL features provided by Cloudflare and followed their insturctions on changing the nameservers to Cloudflare, the same error message keeps popping up on my weebly account when I clicked published.

The website still functions as usual, but the error message pop ups everytime I publish the website on weebly. And by the way, the SSL feature provided by Cloudflare doesn't function either.

[Adam7]

That error shows up because the editor checks to see if your site is using one of our IP addresses for its DNS records. Since it's using Cloudflare it thinks the domain isn't pointed to us. You can safely ignore the message since you have everything set up properly with Cloudflare.

[awisechoicecomm]

Adam,

Thanks for assuring us Cloudflare users that the scary red message in the Weebly "publish" window isn't anything to worry about since we're set up correctly on the Cloudflare side. Could you please address the second part of that previous user's post? He said that his Weebly site is not showing under https, despite being set up correctly in Cloudflare. I am having the same problem. If I type https:// in front of my domain (https://awisechoicecommunications.com), it still presents as a non-secure site with the "i" in a circle. Is this on the Weebly side or Cloudflare side? Please advise so I may follow up with the appropriate party to understand what I have to do to get the green lock next to my URL. Thanks. 

P.S. I wish I could have avoided Cloudflare, but Weebly does not offer free encryption through Let's Encrypt like every other major CMS/host. Surprising and disappointing. I've always considered Weebly the most user-friendly among the myriad CMS options, and recommended them to several clients for this reason. But this fail has forced me to pursue other options. Unfortunately, my own site is on Weebly, and I'm trying to make do with some form of free encryption until I have time to move to another platform. Would prefer to stay with Weebly, but feel I have no choice as the Business plan is cost-prohibitive.  

[Queso]

Hey there! That aspect may be something you'd want to check with CloudFlare with first, yes. On a lighter note, we are indeed on track to expand options for SSL, which should make things a lot simpler going forward.

[awisechoicecomm]

Thanks, Queso. I didn't see your post before responding to my own post. Thanks for the update. Yes, it was an issue on the Cloudflare side. Appreciate your response.

[awisechoicecomm · Accepted solution]

Update: I solved the problem. It was on the Cloudflare side. For others who are having this problem, you may need to change your SSL setting under the "Crypto" tab in Cloudflare. 

[Adam7]

Thanks for sharing what solved it for you, @awisechoicecomm.

[Alex51]

Could you write the steps that should be taken, please? Because I'd beed trying to do something for about an hour and nothing positive had happened. Also, how are you dealing with the sitemap now? Did you simply provide redirection for every address from http to https or there is something else?

Thank you

[Sibren]

Hi! I had the same issue as you all did, and hope to resolve it here for you:

• Try going to https://[your domain name] to see if your website is properly configured on Cloudflare, if so it displays your website, or a 404 Page not found [if unpublished].

Always good to check:

1. Go to Cloudflare and go to its Crypto tab, check if its SSL certificate is on FULL or FULL (strict) and change accordingly [You may want to use FULL instead of FULL (strict) if you have issues].
2. Go to Cloudflare and go to its Crypto tab, check to see if "Always use HTTPS" is ON. If this is off, all requests refer to an unsafe version of your website, regardless if you set it up correctly.
3. Go to Cloudflare and go to its DNS tab, check if all AAAA Records have been removed, and all A records have a orange cloud to them. Click on the area where a cloud should appear until an orange cloud appears.
   
   
4. Go to your Domain provider and go to its DNS options, Check to see if All records have been removed. If there are still any records, check if Cloudflare has the same record, and remove it on your Domain provider's end. If you have DNS records by your Domain provider, they will not go through Cloudflare, and consequently not their protection services!

NOTE:

You may encounter an issue where your website resolves in a redirect loop, I have no fix for it... What you can try to do is change the SSL Certificate on CloudFlare to Flexible instead. The redirect loop is probaply cause of an already existent certificate not beeing recognized on Weebly itself. » Do keep in mind that the Flexible SSL is only a Partial security, and does not secure content between Cloudflare and your host. In this case Weebly.

It is advised NOT to use a flexible SSL, as it does not provide the protection a proper SSL has, and is consequently still vulnerable to attacks. You should only use it if you want to gain your users trust, and you have no way of people inputting sensitive information, like passwords or addresses.

[Adam7]

Thanks for sharing that information, @Sibren!

[groblerpaul]

Please mark this response as the solve for the problem. Thanks

[nchiles]

---

NOTE:

You may encounter an issue where your website resolves in a redirect loop, I have no fix for it... What you can try to do is change the SSL Certificate on CloudFlare to Flexible instead. The redirect loop is probaply cause of an already existent certificate not beeing recognized on Weebly itself. » Do keep in mind that the Flexible SSL is only a Partial security, and does not secure content between Cloudflare and your host. In this case Weebly.

It is advised NOT to use a flexible SSL, as it does not provide the protection a proper SSL has, and is consequently still vulnerable to attacks. You should only use it if you want to gain your users trust, and you have no way of people inputting sensitive information, like passwords or addresses.

---

Has anyone figured out a fix for this, besides changing the certificate to flexible? I'm running into the redirect loop as well. Thanks for any advice.

[paidfocusgroups]

I have had the exact same problem when I used full or full strict SSL on CF, and had to resort down to flexible in order to serve out without the direct loop.  That was back when I had this 3 way setup with my domain registrar, CF, and Weebly, where  my DNS was served THROUGH CF.  I recently moved my domain to CF as my registrar, and dropped the old registrar. (it is also alot cheaper)

I havent tried changing my SSL level since then, but I am thinking that with just two parties invloved now instead of three, we might have more control over that in CF.

There is a waiting period, but they are slowly onboarding people who want this function. I am now paying about 1/4 the price that I was with my original registrar.

More info: blog.cloudflare.com/using-cloudflare-registrar