@phsc Please try the command at https://forum.cloudron.io/topic/10087/cloudron-shows-domain-setup-page-after-a-possible-crash/5 . You can also reach out to us on support@cloudron.io and we can do that for you. After you run the command, run the start.sh again and it should work.

@ekevu123 For that error:

rm /home/yellowtent/platformdata/update/* systemctl restart box Then, in the dashboard check for updates.

It looks like it has cached the wrong update information somehow.

Please check if it's any better with CLI 5.4.1

@girish said in trying to use cloudron openid connect with cloudflare0trust:

@

ok i tryed that.
only problem, it keeps changing the token, the zero-trust does. everytime i put it in, it puts like 34more bullets (what i hear on the screen reader when trying to enter) in the tokens field.

@zylstra I think you are asking how to relay email . See https://docs.cloudron.io/email/#relay-outbound-mails

@saikarthik said in Incoming email not being received:

I had to re-add the entry for netlify load balancer in my DNS.

Maybe next time lead with that. The use of „netlify load balancer“ seems to be some vital information while people are trying to guess-troubleshoot your DNS problems….

@girish i'm not exactly sure how i would go about relaying incoming mail. i do have outbound mail relayed, though.

@girish ctrl+shift+v works, thank you!

aw.
well, it told me witch post, but it didn't say witch post in particular in this particular topic. unless you can upvote the topic itself

@nebulon thanks! 🙂

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

@jdaviescoates said in Cloudron install error (dpkg error):

I've got as far as selecting the Ubuntu DVD but now I can't login!

Aha, I found this https://ubikann.com/2021/09/21/installing-ubuntu-server-20-04-lts-on-a-netcup-root-server/ which directed me towards installing the DVD using the VNC screen via the Netcup Server Control Panel.

I managed to use that (but you're right, not exactly simple) to install full Ubuntu and am now installing Cloudron...

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!).

The issue was a clash in sftp keys in the blobs table. Solution here was to purge those blobs from the database to let the migration succeed. The consecutive box restart will ensure keys again and puts them into the database correctly.

For reference, to purge those keys, the following command can be run via SSH (of course use with caution or better contact us about it first):

mysql -uroot -ppassword box -e "delete from blobs where id='sftp_private_key' OR id='sftp_public_key'"