Cloudron Forum

We can not help you. You have your answer. Look for VPSes which unblock port 25. I frequent lowendtalk and lowendbox for this.

https://my.hussainwh.info works for me. Note that for https://hussainwh.info to work, you have to install an app on that domain. When there is no subdomain , it's called the bare/naked/apex/root domain .

@ReessKennedy said in Digital Ocean Issues after altering Droplet name?:

Changed name of droplet.

but this is a superficial change that I think only occurs in a Digital Ocean database just for labeling and does not impact any server config.

In DigitalOcean, the name of the droplet is also the reverse/PTR address for the IP address. Just something to remember, this is not the reason your Cloudron is unreachable though.

All systems seem like they are working fine

Can you also run cloudron-support --troubleshoot on the server?

I should have changed DO DNS to AWS before deleting it then, but I didn't quite understand how to do that either.

I guess that'll be the worry of the next person who runs into a similar situation.

ok, thank you

@luckow yes. See this comment - https://forum.cloudron.io/post/83868

https://git.cloudron.io/cloudron/box/-/commit/0dfadc59228978f82ae3aa2ba4be2b421e785e02 was the fix . You can always apply it locally in /home/yellowtent/box/src/dns/digitalocean.js . Then, systemctl restart box and renew all certs.

@girish said in Cert renewing failing:

@visuex are you the same as @cpa ?

Nope, not me!

@Lanhild I sent a reply to them again. They've finally opened the port.

Please update to Cloudron 7.6.4 where it is fixed already. The DigitalOcean API behavior had changed recently.

Setting up under the wildcard option worked. Hopefully the wider issue with DigitalOcean will get resolved.

@Recliner2042 It needs to write to DNS . You can read more at https://letsencrypt.org/docs/challenge-types/ (dns-01).

Specifically, the DO refcode is 933831d60a1e .

yes, if the backup config has a password set, the UI will expect it to be entered before you can restore.

You can use the top right menu to mark this as resolved.

@girish Thanks—seems to be working.

@foliovision Cloudron should create the DKIM records if you're using the DO API for your domains. Cloudron does not delete existing records so if you add something in manually, rest assured it won't get wiped by Cloudron.

https://docs.cloudron.io/email/#dkim

BTW, if you go to your Cloudron dashboard --> Email --> Status --> and click on "Redo DNS Setup", that should add in the required records. It should be listed as a TXT record in DO's DNS.

Example:

TXT cloudron._domainkey "v=DKIM1; t=s; p=TIDfKL7GCS...

@S0ulf3re I think the issues you are facing to related to DNS, so the box logs probably won't help.

As a first step to get the dashboard reachable again, ismy.domain.com pointing to Cloudron server IP? You can check host my.domain.com on your PC to verify what the DNS is configured as.

@girish ok i was on the initial setup and i had to click 'show advanced settings' and then set the subdomain to the zone.

a simple hint after the error with something like your message would be super helpful on that page. i'm super busy right now but could try a merge request if that would be welcome.

i appreciate the quick help, thank you.

@yusf OK, thanks, when you find time, feel free to reach on the support mailbox.

Will mark this as solved since this is a DO issue.

@bossbarnes07 It seems an 'A' record with the subdomain 'my' is missing. It should point to your IP (209.97.x.x). Cloudron should have added this automatically, I wonder why it didn't get added. Can you add an A record manually and then go to your server and do "systemctl restart box". You can then visit https://ip again and re-do the setup.