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

@Shai yeah, better to remove it. On ubuntu, installing packages also enables them. So, this might cause problems in the future.

@bmann Yeah, in that case, I'd say just use a provider that allows you to buy extra storage inexpensively and mount it as a volume. BuyVM is the one that comes to mind honestly. You can also use CIFS or NFS, but I don't know how well I'd trust them as primary storage for an app. Also, as said, some apps support external S3 (although that limits your capability to fully encapsulate your backups).

Thanks for the reply. I just doubled from 15 to 30. Lets see if this helps.

I'll give it a try. Thank you very much for your help and explanations.

@mdc773 yes. next time around, you can download the backup config that prefills all this - https://docs.cloudron.io/backups/#restore-cloudron

@girish Nice. Wish Cloudron could fix all the other mistakes I make.

Yes I have DKIM setup. Thanks for the “relaxed” incantation. I’ll try that.

@girish said in resolvconf failed by Install to Cloudron: Did I understand correctly, that cloudron-setup is failing and that the error you posted is from /var/log/cloudron-setup.log ? What's the log lines before the error ? See if you can fix those errors manually and run cloudron-setup --redo . It's not me this time, but I've hit this before yes cloudron-setup does not work at all on Netcup VPS vServers because they are running some custom minimized version of Ubuntu. See also this previous thread https://forum.cloudron.io/post/74252 Netcup said on Twitter they would look into it here https://twitter.com/netcup/status/1711394283347960098 but presumably they haven't fixed it.

@d19dotca I also suspect it's a problem with the iDrive storage. Because the backup problem is not a regular one. If he writes to iDrive support please let me know.

For these kind of setups, it's easiest if you use one of the automated DNS options (i.e not manual or wildcard). Setup service1.domain.tld as one of the automated DNS options. Not sure where domain.tld is already hosted but it's not one of the options we support, you can always create a zone called service1.domain.tld and put host the zone is one of the DNS services. In your proxy, forward https://service1.domain.tld AND ``https://*.service1.domain.tld` (hope it supports wildcard) to Cloudron VM. It should work with valid certs with the above setup.

@genies305 you can just email us at support@cloudron.io

To close the thread here, the issue was simply that update to 7.5 was failing because @squareclouds 's cloudron is still on ubuntu 18 . One must upgade to Ubuntu 20 first before updating to 7.5.

Yay ! [image: 1698858691667-screenshot-2023-11-01-at-17.10.55.png]

@girish Ha ok, makes sense, will try setting up the relay and update the thread. Thx!