Expected Behaviour when running flyctl certs list -a <client app name>
@kapa.ai I'm fixing an issue where my site does not load at all when prefixing with www. It loads fine without it.
I realised I was missing a CNAME record with www, so I've added one in my DNS settings, but when running flyctl certs list -a <client app name> I only get the domain without the www back. Is that expected? I have updated the DNS but it has only been a few minutes.
1 Reply
Hi @CamBlackwood. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the information provided in the knowledge sources, I can offer some insights about your situation with Fly.io certificates and custom domains. However, I don't have specific information about the expected behavior of the
flyctl certs list command.
When setting up a custom domain for your Wasp app on Fly.io, the process typically involves the following steps:
1. Adding your domain to your Fly client app using the command:
Wasp Docs - Using a Custom Domain (https://wasp-lang.dev/docs/advanced/deployment/cli#using-a-custom-domain-for-your-app)
2. Adding the DNS records (A and AAAA) for your domain as instructed by the output of the previous command.
3. Setting your domain as the WASP_WEB_CLIENT_URL environment variable for your server app.
Regarding your specific issue with the www subdomain, it's worth noting that the documentation doesn't explicitly mention setting up a separate certificate for www. The process described is for the root domain.
However, one community member mentioned a similar process for the www subdomain:
"Repeat for www (but with CNAME post on www subdomain)" Discord Support Thread (https://discord.com/channels/686873244791210014/1201898985300971540)
This suggests that you might need to create a separate certificate for the www subdomain and set up a CNAME record, which you've already done.
As for the flyctl certs list command not showing the www subdomain immediately after updating DNS, this could be due to propagation delays. DNS changes can take some time to propagate fully, sometimes up to 48 hours, although often much quicker.
If the issue persists after waiting for DNS propagation, you might want to try creating a certificate specifically for the www subdomain:
Remember to also update your server's WASP_WEB_CLIENT_URL to include both the root domain and www subdomain if you want both to work.
If you continue to face issues, it might be helpful to consult Fly.io's documentation or support channels for more specific information about their certificate management and custom domain setup.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @CamBlackwood, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?