deploying to custom URL does not work consistently
hey folks,
I bought a domain off squarespace, and I am trying to deploy my app there, it seems to work on an off, sometimes the app is there, sometimes auth works (login button shows), and sometimes it doesnt. here are the steps I've taken.
my domain is yellowbirdapp.com
1. Followed the fly.io cutom domain deployment (https://wasp-lang.dev/docs/advanced/deployment/cli)
2. Ensured my google o auth is set up (as in the screenshot)
3. Verified the domains
4. Added the A and AAAA and CNAME records for domain verification to my square space DNS dashboard (screenshot)
so going to yellowbirdapp.com shows me an under construction page, but if I go to https://yellowbird-client.fly.dev/ my page works, but the login button appears and then disappears, but if i login, it takes my to a callback as shown in the screen shot
I am at a loss as to figure out how to consistently keep my app deployed and auth working.
Thanks!
Deploying with the Wasp CLI | Wasp
Wasp CLI can deploy your full-stack application with only a single command.
My Open SaaS App
I made a SaaS App. Buy my stuff.
4 Replies
Wohooo @haarismian, you just became a Waspeteer level 3!
Hi @haarismian. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry to hear that you're having trouble with deploying your app to a custom domain and with the authentication. Let's try to troubleshoot this.
1. Custom Domain: You mentioned that you've followed the steps in the Wasp documentation (https://wasp-lang.dev/docs/advanced/deployment/cli#using-a-custom-domain-for-your-app) to set up a custom domain. If you're seeing an "under construction" page, it might be that the DNS records haven't fully propagated yet. This can sometimes take up to 48 hours. You can check the status of your DNS records using a tool like DNS Checker (https://dnschecker.org/).
2. Authentication: The disappearing login button and the callback issue might be related to the
WASP_WEB_CLIENT_URL environment variable. This variable should be set to your custom domain. If you haven't done this yet, you can do it by running the following command:
This is necessary to keep the CORS configuration up to date. If the WASP_WEB_CLIENT_URL is not set correctly, it could cause issues with the authentication.
3. Debugging: If the issues persist, you can try to debug them by checking the logs in your Fly dashboard and the browser's console. In a Discord support thread (https://discord.com/channels/686873244791210014/1217941277979574315), a community member had a similar issue and was able to resolve it by redeploying the app. You might want to try this as well.
4. Wasp Version: Make sure you're using the latest version of Wasp. In another Discord support thread (https://discord.com/channels/686873244791210014/1201898985300971540), a community member was able to resolve a similar issue by upgrading to the latest Wasp version.
I hope this helps! If you're still having trouble, please don't hesitate to ask for more help.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @haarismian, 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?I solved hte problem, it turned out i wasnt using the correct v6 AAAA record. I guess I deployed and it changed or something along the way and I didn't update the dns in square space
Awesome, glad to hear that got solved!