Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • 0 Votes
    8 Posts
    1k Views
    marcusquinnM
    @girish Magic, that seems to have worked - thanks! Maybe worth considering adding this advice to the email notifications?
  • 0 Votes
    5 Posts
    831 Views
    girishG
    @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.
  • Domain nameservers are not set to DigitalOcean

    Solved Support digitalocean domains
    3
    0 Votes
    3 Posts
    966 Views
    rosanoR
    @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.
  • 0 Votes
    19 Posts
    2k Views
    nebulonN
    @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
  • 0 Votes
    5 Posts
    1k Views
    girishG
    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...)
  • DNS: "Domain nameservers are not set to <provider>"

    Discuss domains
    11
    0 Votes
    11 Posts
    1k Views
    d19dotcaD
    @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
  • DNS CNAME and Cloudron Redirect for WWW

    Solved Support domains dns
    7
    0 Votes
    7 Posts
    2k Views
    U
    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.
  • How to add an extra domain after installing

    Discuss domains redirect
    2
    0 Votes
    2 Posts
    1k Views
    d19dotcaD
    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
  • BitMitigate.com integration (DNS API)

    Feature Requests dns domains
    1
    0 Votes
    1 Posts
    317 Views
    No one has replied
  • Root domain as blog domain?

    Solved Support domains
    5
    0 Votes
    5 Posts
    1k Views
    A
    @nebulon Yes, thank you. I found it!
  • 0 Votes
    4 Posts
    804 Views
    d19dotcaD
    @austinsonger Not that you needed even more confirmations, but I can also confirm that all three links work fine from here in Canada.
  • Renew all Certs

    Solved Support domains certificates
    3
    1
    0 Votes
    3 Posts
    714 Views
    doodlemania2D
    @humptydumpty haha! whoops - on it - great find!!!
  • Single domain, multiple cloudrons?

    Solved Support installation domains
    5
    1 Votes
    5 Posts
    1k Views
    girishG
    @guyds said in Single domain, multiple cloudrons?: I suppose each Cloudron needs a unique domain name because of the DNS records that are being created when installing a Cloudron: DKIM, SPF, DMARC? Yes, and also because we need a unique location to access the dashboard. what if the domain that's being used for a Cloudron already has e-mail related DNS records, for example when it's already configured for use with G Suite or Office 365? Will Cloudron modify those records, override them or just ignore them? If you have an existing DMARC, it don't touch it. Otherwise, it will put the default strict DMARC policy. DKIM uses a unique selector domain, so it won't affect other DKIM entries. The SPF is modified with "a: my.<domain.com" into the existing SPF.
  • reinstall doesn't work

    Solved Support nginx domains
    7
    0 Votes
    7 Posts
    2k Views
    D
    @nebulon there was no error reported by cloudron. The issue was that if I tried to curl, there was nothing returned back (I don't remember the exact reply -- sorry for that). Basically it was like nginx was not routing properly, as if nothing was running at the subdomain.
  • Cloudns.net DNS support

    Feature Requests domains dns
    4
    5 Votes
    4 Posts
    856 Views
    G
    I'm sorry I missed that post. Maybe both can be merged, since my post provides an actual link to the API documentation?
  • 1 Votes
    6 Posts
    2k Views
    girishG
    @infogulch said in Changing from wildcard to provider-based dns configuration left apps and my.example.com unassigned after wildcard was deleted: That makes a lot of sense. Curious, does Cloudron log when it encounters an existing DNS record that it should not overwrite? It will show the error in the UI. If you try to install an app into a subdomain that has a DNS entry, it will error and give you an option to "overwrite" the DNS record.
  • Namecheap API and Home server with Public IP HELP

    Solved Support domains namecheap
    11
    0 Votes
    11 Posts
    3k Views
    girishG
    @Advika58 Are you a bot?
  • Emoji Domains

    Discuss domains
    16
    4 Votes
    16 Posts
    3k Views
    S
    Did not know this was existing till now... thanks man
  • 0 Votes
    10 Posts
    1k Views
    J
    @andreasdueren said in Cloudron can't uninstall apps after access to domain got denied: Sep 26 10:49:40 box:dns unregisterLocation: Error unregistering location A. retryable: false. message: Invalid access token statusCode: 403 code:9109 The directory message is just a warning can be ignored. The above message is the real error. Are you sure you are not using any other domain in the app which in turn uses some DNS provider? Are all the DNS providers manual ?
  • 0 Votes
    12 Posts
    2k Views
    marcusquinnM
    @robi yeah, with ecommerce being our primary business, we're invested in this. We have 12 very experienced devs on the team but just a few of them have had time to start looking at Cloudron this week. In this for the long-term though so I'm sure you'll start to see our work filtering through very soon.