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


Skip to content
  • Removing a domain produces an SQL error

    Solved Support domains
    5
    1
    1 Votes
    5 Posts
    934 Views
    scookeS
    @ChicagoGregg said in Removing a domain produces an SQL error: Low of the totem pole. Low of the totem pole. Just use "least significant/important/crucial".
  • Hetzner: Support more nameservers

    Solved Support domains hetzner
    3
    2 Votes
    3 Posts
    690 Views
    girishG
    Fixed in master branch
  • 1 Votes
    7 Posts
    2k Views
    girishG
    @supashot said in [Noob]Access denied: OVH DNS error 403 This call has not been granted: @girish ls -al /home/yellowtent/appsdata total 8 drwxr-xr-x 2 yellowtent yellowtent 4096 Nov 29 14:02 . drwxr-xr-x 6 yellowtent yellowtent 4096 Nov 29 14:02 .. I think I understand. Hastebin probably has not finished installation / has error installing ? This is why that directory is empty . If so, that's normal.
  • 5 Votes
    7 Posts
    2k Views
    girishG
    @dsp76 indeed, thanks for reporting. The error message should read Hetzner instead of OVH when you select Hetzner. I have fixed this for the next release.
  • what happens if you change your domain dns settings on cloudron

    Solved Support domains dns
    2
    1 Votes
    2 Posts
    432 Views
    girishG
    @pixeltablet as long as the DNS settings are copied over to cloudflare, everything will continue to work. You can also make Cloudron add the DNS entries into Cloudflare by first switching to cloudflare and then sync DNS - https://docs.cloudron.io/domains/#sync-dns . Just so you don't hit any DNS issues, you can add the 'my' subdomain record manually into Cloudflare.
  • How to remove domain adding rate limit

    Support cloudflare domains
    3
    1
    1 Votes
    3 Posts
    360 Views
    girishG
    Are you also using the domain outside of Cloudron? I am surprised you hit any limit at all, Cloudron API usage is quite low.
  • 0 Votes
    7 Posts
    1k Views
    jdaviescoatesJ
    @Reveller said in Rudimentary question about how domains work in Cloudron: @jdaviescoates Thanks. Overthinking is one of my unfortunate specialties. But the docs are very clear that the apps are installed on subdomains - https://docs.cloudron.io/installation/ I see what you mean, I think @staff ought to update this part of the docs which give the wrong impression: Domain Setup Provide a domain like example.com. The way Cloudron works is that the dashboard gets installed at my.example.com, and apps are installed under subdomains that you specify like git.example.com, chat.example.com, and so on. @Reveller said in Rudimentary question about how domains work in Cloudron: But by looking closer at the demo, I can see how the location can be changed (app's location tab) - so I assume that's how it's done. Yes, you can always change location there, but you can also just directly install on the root domain in the first instance too.
  • List all domains, don't paginate them

    Feature Requests domains
    1
    2 Votes
    1 Posts
    101 Views
    No one has replied
  • aws route 53 domain set up

    Solved Support domains route53
    3
    1 Votes
    3 Posts
    596 Views
    ShaiS
    @nebulon Thanks. Ohh, I was so close last night. Your post gave me the courage to plunge back in. The username I gave to the user who owns the policy was a really wierd choice several years ago. So when I went to the aws users page, I didn't think of exploring there. Also the ID and secret were in a file on my local machine, filed well with a good file name. Last night I just wasn't careful in looking for it. So I'm all good now.
  • DKIM and SPF infos for wilcard or manual DNS setup

    Solved Support domains mail
    3
    1
    1 Votes
    3 Posts
    582 Views
    girishG
    @therealwebmaster Email -> Domain -> Status . You can click on each of the records there and it will tell you what you should setup. [image: 1687095241687-ca0ac153-5ead-4795-b574-f48f6c741393-image-resized.png]
  • Difference between manual and wilcard domain config?

    Solved Support domains
    7
    1
    1 Votes
    7 Posts
    1k Views
    girishG
    Wildcard - In wildcard, you setup subdomains to point to the server IP. So, when you install an app or change it's location, Cloudron won't remind you to point the DNS to the server IP. Manual - When installing an app or changing it's location, Cloudron will remind you to point the DNS to the server IP. Why prefer one over the other? Wildcard is one time setup. Manual is something you have to do on each app install. People also sometimes ignore the "instructions" it shows to adjust the DNS and click Install. Depending on your DNS provider, DNS propagation can take long. So, let's say if it takes 15 mins or something, then when installing the app, Cloudron will be unable to get certs. This can lead to a bad UX.
  • add deSEC as DNS Provider

    Solved Feature Requests dns domains
    10
    4 Votes
    10 Posts
    2k Views
    H
    @girish said in add deSEC as DNS Provider: deSEC integration is implemented for next release. That is the best message of the day. Thank you!
  • Cheap Domain Names: $0.84/year with renewal

    Off-topic tld domains namecheap xyz
    5
    3 Votes
    5 Posts
    1k Views
    L
    @robi It might not be advertised. Also, I think it isn't a sale, and the renewal price is the same, though I may be mistaken.
  • Adding domains with an "ö" is not supported?

    Solved Support domains punycode
    13
    1 Votes
    13 Posts
    2k Views
    girishG
    @jayonrails whoops, didn't notice!
  • Problem with Domain Setup

    Solved Support gcdns domains
    5
    0 Votes
    5 Posts
    947 Views
    S
    I had a similar problem recently. Here's what I had to do in order to be able to programmatically update DNS records for a domain in Google Cloud DNS: verify domain ownership: https://cloud.google.com/endpoints/docs/openapi/verify-domain-name. I did this by inputting a special DNS TXT record into DNS for the domain. in my case, I was using a Google Cloud Service Account with Terraform (not Cloudron) to modify DNS records in Google Cloud DNS, so in additional to verifying domain ownership, I had to actually add the Service Account I created as a verified owner of the domain as well. After doing these two things, I was able to programmatically update DNS records for the domain using the Service Account. So, assuming you've created a Service Account at Google, given it the "DNS Administrator" role, and added the Service Account email as a verified owner of the domain, you should be good to go. I just tested it with my Cloudron and it all worked. I'm attaching a screenshot of the Google domain verification screen showing where I added the Service Account as a domain owner. Hope this helps.[image: 1682509131953-cleanshot-2023-04-26-at-07.28.52-resized.jpeg]
  • DNS address could not be found

    Solved Support domains cloudflare linode dns
    2
    0 Votes
    2 Posts
    545 Views
    girishG
    @j_vmess your domain works just fine for me here. Maybe it's a browser cache issue? Have you tried another browser or after clearing the browser cache? I removed your domain from the original post, since it was showing the setup screen.
  • 0 Votes
    9 Posts
    2k Views
    girishG
    @scooke yes, it won't remove your existing records and won't touch things outside scope of Cloudron (which is basically app records and email records).
  • Setup with Hetzner DNS not working

    Solved Support domains nameserver hetzner
    9
    0 Votes
    9 Posts
    3k Views
    girishG
    @Fabix thanks. Strange stuff... I will put it in our docs that we only support Robot.
  • I cant acess my cloudron through the domain

    Solved Support domains troubleshooting
    2
    0 Votes
    2 Posts
    470 Views
    girishG
    @DAMO11-coder see https://docs.cloudron.io/troubleshooting/#expired-domain
  • Domain Configuration: External Site on Root Domain

    Solved Support domains
    3
    0 Votes
    3 Posts
    680 Views
    S
    I just jumped the gun. It was just DNS taking a while to propagate. All good now.