Cloudron Forum

@msbt Thank you, that makes sense!

@nebulon I just added a new dns record on Namecheap manually. After this action, cloudron was able to add my second domain 😅

I solved the same symptoms by recreating Personal Access Token for Cloudron.
Screenshot 2022-01-13 at 6.18.06 PM.png
Read/Write access under Domains required.
Mine just expired after default set 6 months.

Adding a redirection made things work.

@d1rk I have added the multi domain flag to the manifest. Let me know if it works OK.

@necrevistonnezr said in Godaddy.com API is down:

unfortunately none of the Cloudron supported domain providers allow moving a DE domain…

By DE domain do you mean .de?

You can definitely register those on https://gandi.net but perhaps that's different to moving them?

@samuelbevan2000 you have to port forward port 443 in the router to the vm.

@girish Magic, that seems to have worked - thanks!

Maybe worth considering adding this advice to the email notifications?

@scooke yes, you can mix between Cloudron's automation and manual DNS changes. In fact, that's the normal and only mode of operation.

The automation is only adding and removing things that you would have to do normally outside Cloudron. For example, when you install an app, you have to setup A records. When you uninstall an app, you remove the A records. This is all the automation does. If you try to install an app in a location and there is already a DNS entry in your DNS provider, Cloudron will inform you of the same and let you 'overwrite' it or cancel the app installation.

Same goes for email stuff. It sets up things like DKIM/SPF records automatically. These are updated carefully to not collide with existing entries. The MX record is only touch if you enable incoming Cloudron Email. Even in that case, there is a checkbox to not update DNS.

@girish ok i was on the initial setup and i had to click 'show advanced settings' and then set the subdomain to the zone.

a simple hint after the error with something like your message would be super helpful on that page. i'm super busy right now but could try a merge request if that would be welcome.

i appreciate the quick help, thank you.

@scooke we have traced this down to a nodejs bug apparently with the domain in question.
The upstream issue is at https://github.com/nodejs/node/issues/39397

The CLI has indeed no way to edit domains. What you did is the correct approach - make the dashboard available via the browser and then edit from the Domains view.

(As for the CLI warnings, looks like we have to replace request module with superagent. Sigh, we actually used to use superagent before...)

@girish said in DNS: "Domain nameservers are not set to <provider>":

adding a flag to ignore the name server check should be ok. I think we still want to keep the default to checking the name server since this is general/common flow on Cloudron.

Yes please, this would be great. Definitely fair to keep it as a default to check the name servers, but a checkbox to ignore it would be fantastic! 🙂 This would help us in changing DNS providers in a fault-tolerant way by being proactive setting up the DNS records at the new provider.

@girish said in DNS: "Domain nameservers are not set to <provider>":

Did you create Feature request for this already ?

Unfortunately not, I guess I made a bad assumption this would be included from the original discussion I created, haha, I think I probably should have set this as a Feature Request instead. Sorry for not filing that earlier. I went ahead and created one though here for that: https://forum.cloudron.io/post/54948

I had the same issue and I was able to follow the steps given about setting up a redirection in Cloudron. In fact, I decided to write a full article about it to help others understand how to fix this issue step by step.
You will have to make sure you put the right DNS entries and then set up the redirection. Read this guide here and it will help you to fix this issue.

https://docs.cloudron.io/domains/#overview 😉

Yes, you can add new domains to Cloudron. Depending on where the authoritative servers are for the domain, you can use the dedicated API-based setups (i.e. AWS, DO, Namecheap, Linode, etc), or you can instead use the Wildcard setup for any other service that's not explicitly listed in the providers list.

Then once the domain is added to Cloudron, you can add redirections to the same app if you desire, in the App page: https://docs.cloudron.io/apps/#redirections

@nebulon Yes, thank you. I found it!

@austinsonger Not that you needed even more confirmations, but I can also confirm that all three links work fine from here in Canada. 🙂

@humptydumpty haha! whoops - on it - great find!!!