After deploying, my wasp app says "This site can’t be reached" - it was previously working
I had my wasp app working as expected after deploying to my domain last week, but now when I try and visit it (https://www.microinfluencer.club/), I get this error - www.microinfluencer.club’s server IP address could not be found.
It was working last week, and I noticed the app says it is suspended on fly (but the client app is accessible on fly). The domain itself was previously configured to vercel, but as far as I know I removed everything related to that in my DNS settings.
8 Replies
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 you've provided, it seems like there might be an issue with your domain configuration. Here are a few steps you can take to troubleshoot this issue:
1. Check your DNS settings: Ensure that your DNS settings are correctly configured to point to your Fly.io app. You can use a tool like DNS Checker (https://dnschecker.org/) to verify your domain's DNS records.
2. Check your Fly.io configuration: Make sure that your domain is correctly added to your Fly.io client app. You can do this by running the following command, replacing
mycoolapp.com with your domain:
This command will output instructions to add the DNS records to your domain. Follow these instructions to ensure your domain is correctly configured.
3. Set your domain as the WASP_WEB_CLIENT_URL environment variable: You need to set your domain as the WASP_WEB_CLIENT_URL environment variable for your server app. You can do this by running the following command, replacing mycoolapp.com with your domain:
This step is necessary to keep your CORS configuration up to date.
4. Redeploy your app: If you've made changes to your DNS or Fly.io configuration, you may need to redeploy your app for these changes to take effect. You can do this by running wasp deploy fly deploy.
If you're still experiencing issues after following these steps, it might be helpful to check the logs for your Fly.io app to see if there are any error messages that could provide more information about what's going wrong.
For more detailed instructions, you can refer to the Wasp deployment documentation (https://wasp-lang.dev/docs/advanced/deployment/cli#using-a-custom-domain-for-your-app).
Sources: Wasp Deployment Documentation (https://wasp-lang.dev/docs/advanced/deployment/cli#using-a-custom-domain-for-your-app), Discord Support Thread (https://discord.com/channels/686873244791210014/1201898985300971540)
----------------------
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?Thanks @kapa.ai , after trying the site mentioned I get failures, so I suppose it's a DNS issue. I'll try and redeploy via the CLI
Let me check the knowledge base for you. One moment! :books:
----------------------
You're welcome! If you suspect it's a DNS issue, you might want to double-check your DNS settings and ensure they match the instructions provided by the
wasp deploy fly cmd --context client certs create mycoolapp.com command.
Once you've confirmed your DNS settings, you can redeploy your app using the Wasp CLI with the wasp deploy fly deploy command. This command pushes your client and server live and updates your deployed app with the latest changes.
Here's the command for reference:
If you're still encountering issues after redeploying, don't hesitate to reach out for further assistance.
Sources: Wasp Deployment Documentation (https://wasp-lang.dev/docs/advanced/deployment/cli#deploy), Wasp CLI Reference (https://wasp-lang.dev/docs/general/cli#overview)
----------------------
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?Hey @CamBlackwood, yeah, sounds like a DNS issue. Any luck fixing it? Can we do anything else to help?
@Filip just at the day job atm so can't action, but I'll keep you updated 🙂 Pretty sure I must've messed something up moving it from vercel, weird that it worked for a few days though! Thanks
@Filip I was able to do a redeploy and it's all online now - must've been some renemants left over from vercel somewhere
@CamBlackwood I would advise setting up a monitor here: https://uptimerobot.com/ -> you can set up basic monitor for free, and what it does is send you an email if your web app goes down. I found it super useful in the past, so you avoid these situations where app has been down for an hour or a day and you didn't know about it.
UptimeRobot: Free Website Monitoring Service
Start monitoring in 30 seconds. Use advanced SSL, keyword and cron monitoring. Get notified by email, SMS, Slack and more. Get 50 monitors for FREE!
Two more advices regarding Fly:
1. It has an option to automatically suspend the machine if it has not been used for some time. I think it is called autoscale or sometihng, and if min number of mchines is 0, it can suspend it completely. I would make sure you your server configured so it doesn't happen. Fly docs are the way to go here, this is not Wasp specific.
2. Fly has this thing where by default it hosts your machine with shared IP, meaning there are some other machines behind the same IP. You don't want to go with that option, because if one of them does anything malicious, you might get up tagged by antivirus because your IP -> your domain will get tagged. We had that happen with opensaas.sh, it took quite some time to get out of that. So make sure to upgrade your IP to be a dedicated IP. It is something little, like 2 USD per month, but if you don't know it, and have a custom domain, you can get this in situation where your custom domain gets flagged by Avast and similar. We need to add this to the docs, next to custom domain.
Ah that’s awesome thanks Martin, hadn’t seen this before