What I’m trying to do:
Website on custom domain for anvil app hosted/DNS through Cloudflare.
What I’ve tried and what’s not working:
Followed directions here and with cloudflare. It has only been 12 hours, but the guides seem like it could take 48 hours for the DNS info to propagate… not SSL certs…
I created the domain and made a DNS entry with cloudflare, pointing the site to 52.56.203.177. I also chose the “strict” rules on
Sorry for the impatient questions, but it is my first “production” app I am publishing using anvil. Just making sure I’m not waiting for something when I should be doing something
Here is the error I am getting (and that you will get if you visit Texasfluteguild.net)
Excited to get this going: this is only the infomational part of the webpage. I am building sections where customers can have their own account and track progress of repair, get quotes, etc…
After trying to learn some other frameworks, anvil really did make the “building a reactive” website quite easy. Thanks for what you guys are doing.
Let me know if I should just wait, or if someone in the Anvil Crystalline tower needs to flip a switch…
For many domain registers it usually takes up to 48 h as you mentioned, so just sit tight.
Once the dns record has propagated Anvil will take care of the SSL certificate.
PS
I’m just a regular anvil user, but I hope my answer are helpful!
Sorry I haven’t used cloudflare my myself.
But from my experience the www record seems correct.
I think your first record (where it says texasfluteguild.net) should just be @.
I am not quite sure about the proxy option. I looked at a YouTube video and there they had the proxy option unchecked.
Check with Anvil support to see if they can work with the proxied option. Alternatively, change it to DNS only and then the outside world will see Anvil’s IP address and everything should work as intended.
If it is easier on them, I can turn off the proxy, but if I am reading it correctly, it says they can handle it either way with cloudflare ({unless i am reading it wrong)
If I “accept the risk” it goes through fine… I wonder if this is a temp thing with the SLL certs (will update support) or if there is something else I need to do on my end
(Just updating everyone for completeness: I know, the first time you do something is always the hardest)