W
Wasp4w ago
Sven

New deploy only on www. subdomain

I did a deploy yesterday but when i go to my app on example.com it doesnt show that deploy but when i go to www.example.com it shows all new changes... How come that? I use fly
6 Replies
kapa.ai
kapa.ai4w ago
Hi @Sven. 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, it seems that your issue might be related to how custom domains are set up with Fly.io for Wasp applications. Here's what could be happening: 1. DNS Configuration: You might have only set up the DNS records for the www subdomain, but not for the root domain (example.com). This would explain why the new changes are visible on www.example.com but not on example.com. 2. Certificate Issues: There might be a problem with the SSL certificate for the root domain. Fly.io has had some issues with certificate issuance for shared IPs in the past. To resolve this issue, you can try the following steps: 1. Ensure proper DNS configuration: - Add both A and AAAA records for the root domain (@) and the www subdomain. - If your DNS provider allows, set up a CNAME record for www pointing to your Fly.io app URL. 2. Re-issue certificates: You can try removing and recreating the certificates for both the root domain and the www subdomain. Here's how:
fly certs remove example.com -a your-app-name
fly certs create example.com -a your-app-name

fly certs remove example.com -a your-app-name
fly certs create example.com -a your-app-name

Repeat this process for www.example.com as well. 3. Update the WASP_WEB_CLIENT_URL: Make sure your server app's environment variable is set correctly:
wasp deploy fly cmd --context server secrets set WASP_WEB_CLIENT_URL=<https://example.com>

wasp deploy fly cmd --context server secrets set WASP_WEB_CLIENT_URL=<https://example.com>

4. Redeploy your application: After making these changes, redeploy your app using:
wasp deploy fly deploy

wasp deploy fly deploy

For more detailed information on setting up custom domains with Wasp and Fly.io, you can refer to the Wasp CLI deployment documentation. If these steps don't resolve the issue, you might want to check Fly.io's status page or their community forums for any ongoing issues related to custom domains or certificate issuance. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @Sven, 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?
Sven
SvenOP4w ago
Hmm dont really understand what is happening, anyone else? It was a caching issue hmm nvm when i reset cache in session (devtools) then it shows the correct page but when i then browse the site later on it shows old version again
Filip
Filip4w ago
Hey @Sven. Please provide some more details (the steps you're doing, screenshots...) and I'll help you out.
Sven
SvenOP4w ago
Yeah i will try to figure itnout myself first let me see what is going wrong here Il ipdate
Filip
Filip4w ago
Sure, let me know!
Sven
SvenOP4w ago
I think it was a caching issue oer page Per*

Did you find this page helpful?