Checking certs for custom domain
WSL , latest wasp version
Trying to figure out how to check my A and AAAA records for a domain I've chosen after the initial set up. (stuck to https://wasp-lang.dev/docs/advanced/deployment/cli#using-a-custom-domain-for-your-app)
I realized, that on my domain host it had the original DNS still there with the new, which I think stopped my custom domain from going up.
Though... I didn't document my A & AAAA,
When I re-run the code I get the error
Error: Hostname already exists on app
And am struggling to get the certs to reappear (I'm sure it's a simple command) or I have to remove it and then reinitiate it (which I also couldn't find clear direction on)
Thanks!
Deploying with the Wasp CLI | Wasp
Wasp CLI can deploy your full-stack application with only a single command.
7 Replies
Hi @Joshua. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
To check your A and AAAA records, you would typically use a DNS lookup tool or check directly with your domain provider. However, if you're trying to retrieve the original A and AAAA records provided by Wasp during the setup, and you're encountering an error when trying to re-run the command, you might need to remove the existing certificate and create a new one.
Here are the steps to do that:
1. Remove the old certificate:
2. Create a new certificate:
This should output the instructions to add the DNS records to your domain again, including the A and AAAA records.
Remember to replace
mycoolapp.com with your domain.
Please note that these steps were derived from a Discord support thread (https://discord.com/channels/686873244791210014/1201898985300971540) and might not be directly documented in the official Wasp documentation. Always proceed with caution when modifying DNS records and SSL certificates.
If you continue to encounter issues, I recommend reaching out to the Wasp community on their Discord server (https://discord.com/channels/686873244791210014/1201898985300971540) for further assistance.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Joshua, 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?perfect!
@kapa.ai
After using wasp deploy fly cmd --context client certs remove gulearn.com
I got the response Error: prompt: non interactive
And then when I tried to wasp deploy fly cmd --context client certs create gulearn.com
I got the same error Error: Hostname already exists on app
Let me check the knowledge base for you. One moment! :books:
----------------------
The error
Error: prompt: non interactive suggests that the command is trying to prompt for input, but it's being run in a non-interactive environment. This issue was discussed in a Github issue (https://github.com/wasp-lang/wasp/issues/1320) where a user encountered a similar problem. The solution was to add the --org option to the command, specifying the organization.
Try running the commands like this:
Replace <myorg> with your organization name.
If you're still encountering the Error: Hostname already exists on app error, it suggests that the hostname is already associated with an app on Fly. You might need to remove the existing app or use a different hostname.
If these steps don't resolve your issue, I recommend reaching out to the Wasp community on their Discord server (https://discord.com/channels/686873244791210014/1201898985300971540) for further assistance.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Joshua, 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?Nevermind... stil have access
Ignore this thread, sorry! (bot was useful), still playing around!
Hey @Joshua did you figure it out?
Btw you can also access
fly directly for stuff like this, so doing these command with flyctl instead of wasp deploy fly as a prefix would probably bring you closer to what you want to achieve.
because wasp deploy fly runs flyctl in the background but makes it harder to answer to any questions flyctl might be asking.Yes this was resolved! Thanks for checking in!
I'll be tackling the other problems when I get home from work tonight! Will update that thread when I get to it, ty for help!
Awesome! Anything we should learn from this, something we can improve on the Wasp side, be it docs, implementation, anything?