Oops! An Error Occurred - The server returned a 404 Not Found (custom domain)
-
Hello - I tried to publish my site using a custom domain. Moved the DNS servers from GoDaddy to Cloudflare.
Added the CNAME for the .brizy.site as directed & Added the A record with the IP address as directed.
Cloudflare and GoDaddy are showing the changes as active. Brizy is rendering the error message.
It goes back : forth from 404 server error to page can't open because of too many redirects.
I've published using the custom domain before with NO problem. Please help - thank you.
0 -
Hi,
Could you send us the URL link of the site you receive this problem?
Did you delete all record from GoDaddy before uploading them to the Cloudflare? On the Cloudflare did you deactivate the proxy? At the moment the Brizy Cloud sites can't work on the proxied DNS and therefore you have to activate the grey-cloud. Could you please send us a screenshot with how did you set-up the Cname and A record on the Cloudflare?Thanks!
Best regards,
Sandra0 -
Yes, GoDaddy records were deleted prior to uploading to Cloudflare and a GoDaddy confirmation email received.
NOTE: It would be really helpful if you guys Update your publish steps to show Brizy Cloud sites can't work on the proxied DNS and therefore you have to activate the grey-cloud. That step is super important.
DNS only will reflect the site is NOT-Secure.
Basically, we wasted a full day building it out and waiting for it to replicate, having the error message, making the DNS only change it works, however, the site shows as NOT-Secure.
0 -
Hi,
At the moment we are working to improve this aspect and in the future, we plan to add this possibility and let users publish their sites with proxied DNS settings.
If you notice that the site is now non-secure, could you please send us the URL link of the site and a screenshot with how did you set-up the Cname and A record on the Cloudflare? Do you have set-up only these records? Could you check if you don't have an AAAA record?
Thanks!
Best regards,
Sandra0
Please sign in to leave a comment.
Comments
4 comments