@imc67 said in Cannot install Cloudron on Ubuntu 22.04 (DNS Issue):

I recently installed on a NetCup RS Ubuntu minimal and with Cloudron (and Netdata 😉 ) and had no single issue! Also AVX and AVX2 is supported!

Yeah, fair point, their more expensive RS (Root Server, as they call them, although they aren't dedicated but virtualised) product line works fine (I was on one until I upgraded to a dedicated server at Hetzner)

It's the cheaper vServer (VPS) product range which are currently useless for Cloudron.

@jdaviescoates said in Whoops, installed instead of restored. Do I need to start all over again?:

I'd guess @staff might perhaps add something that will prevent you updating to 7.6 either way if you don't have AVX?

Yep:

@girish said in What's coming in 7.6:

@necrevistonnezr meemo, rocketchat, ackee, wekan & nodebb need mongodb. But the way it's implemented you cannot update beyond 7.5.x . It will just error saying AVX support is needed.

via api you can do that.
POST
{{baseUrl}}/mail/:domain/mailboxes
note :domain is a variable for the mail domain.
note {{baseUrl}} is the Cloudron api url e.g. https://my.DOMAIN.TLD/api/v1

with body:

{ "name": "webmaster", "ownerId": "uid-be9dcf57-ad65-40e0-a3f8-d1c75974bf01", "ownerType": "user" }

The ownerType can be user or group. and the ownerId you need to get via either /users and for groups /groups.

The API and the API Doc is currently being reworked.
https://git.cloudron.io/cloudron/docs/-/blob/master/api/cloudron_api_swagger.yaml?ref_type=heads

@ZZIanis please never do this "solved, thanks anyways" you know what I mean...

At some point someone else will search the same issue and find this topic and has high hopes you know the solution just to read "Nvm it solved, thanks anyways" 😄

Everyone had this, in the search to solve an issue just to find a forum post where someone just wrote "solved" 🙂

So I think I've found the solution.
Modify the Proxy Host config > Advanced and paste the following:

set_real_ip_from 03.21.244.0/22; set_real_ip_from 103.22.200.0/22; set_real_ip_from 103.31.4.0/22; set_real_ip_from 104.16.0.0/13; set_real_ip_from 104.24.0.0/14; set_real_ip_from 108.162.192.0/18; set_real_ip_from 131.0.72.0/22; set_real_ip_from 141.101.64.0/18; set_real_ip_from 162.158.0.0/15; set_real_ip_from 172.64.0.0/13; set_real_ip_from 173.245.48.0/20; set_real_ip_from 188.114.96.0/20; set_real_ip_from 190.93.240.0/20; set_real_ip_from 197.234.240.0/22; set_real_ip_from 198.41.128.0/17; #use any of the following two real_ip_header CF-Connecting-IP; #real_ip_header X-Forwarded-For;

this will allow True Client IP Address to be passed to Cloudron.

@girish thanks.

BTW, the docs at https://docs.cloudron.io/installation/ still say the minimum disk space is "20GB Disk space" but I'd say that is no longer true (because the old server I'm still running Cloudron 7.3.6 on has 20GB and it isn't enough to update to the next version. Indeed, it doesn't even have enough disk space to update the single Uptime Kuma app that is installed on it!).

@girish ( ._.) I got servers with 100+ Mailboxes a global bcc all would be... better 😄
Also Cloudron is used by companies in Germany and they have to abide to the law of archiving business communication https://www.gesetze-im-internet.de/hgb/__257.html and a global BCC option would be very nice.

@robi new cloudron release

Tyvm, saved my day!

Tyvm, saved my day!

@girish Yeah, I'm thinking the same thing. ubuntu is a sudo user, and if the default password Vultr was using was exploited, then I'd have to be looking or processes run by anything. I'll migrate. Thanks again.

Thanks, everyone!

Gandi recently got sold, but so far I'm still happily with them (and they sell .coop domains which lots of other places don't seem to)

yes it is what i use finally and it works well. Thanks !

@webvsnet Ah alright 🙂 Remember that when you upgrade Cloudron, you will have to get back to CLI 5.4.0

@girish
opps, my last post was never published…

anycast.me is their geoloaction-aware DNS system.

I opened a ticket with them and after manual pushing DNS updates after disabling DNSSEC (temporarily), it worked and propagated the right entries.

there are still some false positves on spamhouse, but it's working.

Thanks for your support.

@bozza-man We haven't gotten an email from the email that you have registered in the forum with. Can you maybe send again?

@letecho Did you sort this out? We sent you a mail saying we cannot connect but got no response.

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.