Cloudron Forum

@girish The terminal command comes back correctly. I don't have time right now to upload a file. But I did upload a test index.html file the other day and it worked fine. I added my app locations to the child nameservers page and I'm not getting the TXT file download anymore. I'm only seeing the characters included in the app browser address if I am in the settings section of the apps. I am still getting issues loading pages if I just type in my regular domain and I get the untrusted certificate warning.

mail-config2.jpg
mail-config1.jpg

@scooke right 🙂

Also, 'wildcard' provider is just a convenient approach over the 'manual' provider. When you use, 'manual' provider, Cloudron will remind you set up these DNS entries manually (each time you add app or relocate app). With a wildcard, you don't get this reminder since a wildcard was set up.

Thanks for this.

Yes, I can see how that would make sense, however, keeping the subdomains while allowing for the domain.tld to change is I think the best of both worlds. If there needs to be a checkbox at restore to keep or discard subdomains, that would be a bonus.

Thank you all, I can finally acess my app.

@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".

Fixed in master branch

@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.

@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.

@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.

Are you also using the domain outside of Cloudron? I am surprised you hit any limit at all, Cloudron API usage is quite low.

@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.

@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.

@therealwebmaster Email -> Domain -> Status . You can click on each of the records there and it will tell you what you should setup.

image.png

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.

@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.

@jayonrails whoops, didn't notice!

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.CleanShot 2023-04-26 at 07.28.52.jpeg