@girish I have mine in France. I've been able to install Cloudron since, I guess the problem was with the OS they provided, but I still don't understand why apt update only worked after 1 day.

@foliovision you can also try docker system prune -a --volumes but generally I have never succeeded in making that reclaimable space be less than 2GB in any server using docker (even without Cloudron).

@girish said in Information in docs changed regarding branding: @andreasdueren passwordreset.html and setupaccount.html already use app branding. notfound.html and appstatus.html are really more backend things . They have to be usable even when Cloudron is down and thus the API cannot be accessed to get the branding information. Of course, one can statically generate them each time branding is changed... I see, makes sense!

Yeah, thanks. I thought thats posible, but i will do it like our adivise

@skeats do you need help patching it?

At least they can copy/paste from the log file!!

@bloops are you saying you created a Domain called mail.domain.tld ? This is not needed. I think the certificate issue could simply be a matter of DNS propagation. Especially, with manual DNS, depending on your provider, this can take a while and Cloudron has no way to check . In such cases, it will start using a self signed certificate initially. There is a nightly cron job to renew certs and that would kick in and get a certificate eventually.

Yes, looks like you are asking for a multi-tenant setup. See https://forum.cloudron.io/topic/9258/request-for-change-rfc

@DualOSWinWiz it was Storage issue which i resolved as it was 100% had to increase VM disk space then did bunch of ubuntu commands but it worked. i would recommend having an auto option to delete unwanted packaged related to Coudron. What's inside Docker 42.08GB OLD Backups [image: 1700103248634-aad5bebe-9f09-458b-83cc-76d090645232-image-resized.png]

@Adhok Don't forget to consider the opposite possibility. Push vs Pull.

The issue here was DNS related. my.domain.com was not pointing to the public IP.

This is fixed with https://git.cloudron.io/cloudron/box/-/commit/fe1c483b7819404d4531fd34323bc2fc18534b85 now

@Kubernetes thanks for reporting!

@mhgcic said in Zoho ZeptoMail: Thanks, but seems to be working fine now. I think it was their verification process. I started using zeptomail when it first came out but was very unstable. Now works well, we have been using it up till now elasticmail. However, we found that too much abuse from robots signing people up to our mailing list caused issues with being reported as spam, now we have moved our newsletters to zoho campaigns and transactional emails to Zeptomail. Yes, I completely agree -- they rebranded from Transmail to Zeptomail and it had seemed like it wasn't done properly, so months of issues. I do occasionally have issues with domain verification and at random (normally fixed within a few minutes to hours) it seems to "drop" the verification. But over the past 6-8 months, that also seems to have been fixed. For reference, if anyone else comes by this topic -- we have it configured in Cloudron as follows: Cloudron Configuration External SMTP Server SMTP Host: smtp.zeptomail.com SMTP Port: 587 Username: emailapikey Password: *{zeptomail-smtp-api-key} * Retrieve / Create SMTP API Key Zeptomail Console Mail Agents > {mail-agent-name} Setup Info > SMTP > "Send Mail API Token #"

I will mark this as solved but feel free to open a feature request post.

@zen-xen3 ah I see, you have to ask upstream about other deployments.

@jdaviescoates A fresh install of Ubuntu does not have docker, nginx or nodejs. We install specific version of these , so we need to make sure it's not already installed. I would take a step back: where are you creating the server? If it's a VPS provider, I can test out Cloudron installation there. Otherwise, can you tell me more about your server installation?

@girish probably can yes just hadn't even thought of trying that! Will give it a go when I get the chance...