<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with digitalocean]]></title><description><![CDATA[A list of topics that have been tagged with digitalocean]]></description><link>https://forum.cloudron.io/tags/digitalocean</link><generator>RSS for Node</generator><lastBuildDate>Fri, 16 Oct 2026 08:03:09 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/tags/digitalocean.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 12 Feb 2026 10:15:10 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Backup Region (DigitalOcean Spaces) not available]]></title><description><![CDATA[Thanks, fixed - https://git.cloudron.io/platform/box/-/commit/51e02da277d972d1d8b514dc15256f88e2fbe201
]]></description><link>https://forum.cloudron.io/topic/15058/backup-region-digitalocean-spaces-not-available</link><guid isPermaLink="true">https://forum.cloudron.io/topic/15058/backup-region-digitalocean-spaces-not-available</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Thu, 12 Feb 2026 10:15:10 GMT</pubDate></item><item><title><![CDATA[DNS A Record is not synced yet: ETRYAGAIN]]></title><description><![CDATA[Nevermind, it was just a matter of being patient. Everything was set up correctly.
For anyone else using Namecheap, it takes a minute for the DNS to sync. Give it some time (quite a bit more than you think) and it'll work.
]]></description><link>https://forum.cloudron.io/topic/14393/dns-a-record-is-not-synced-yet-etryagain</link><guid isPermaLink="true">https://forum.cloudron.io/topic/14393/dns-a-record-is-not-synced-yet-etryagain</guid><dc:creator><![CDATA[slfhstng]]></dc:creator><pubDate>Fri, 10 Oct 2025 21:54:15 GMT</pubDate></item><item><title><![CDATA[inherited old system, trying to figure out upgrading solutions (ubuntu 18.04, cloudron v7.4.3)]]></title><description><![CDATA[hey @CadeHenschen there are very specific documentations and step-by-step guides for distribution upgrades:
See here: https://docs.cloudron.io/guides/upgrade-ubuntu-20/
]]></description><link>https://forum.cloudron.io/topic/13809/inherited-old-system-trying-to-figure-out-upgrading-solutions-ubuntu-18.04-cloudron-v7.4.3</link><guid isPermaLink="true">https://forum.cloudron.io/topic/13809/inherited-old-system-trying-to-figure-out-upgrading-solutions-ubuntu-18.04-cloudron-v7.4.3</guid><dc:creator><![CDATA[BrutalBirdie]]></dc:creator><pubDate>Tue, 20 May 2025 02:26:08 GMT</pubDate></item><item><title><![CDATA[Mounting error for restore during server migration]]></title><description><![CDATA[Thank you for this. I ended up creating a DO Spaces bucket, putting the backup there, and then restoring from that. To make it work, I had to use the Dry Run option and then manually sync the DNS. But now it is working.
I wish that Hostinger had something akin to DO Spaces, but it doesn't, so I am still trying to figure out my strategy for offsite backups.
Thanks @nebulon for your help!
]]></description><link>https://forum.cloudron.io/topic/12964/mounting-error-for-restore-during-server-migration</link><guid isPermaLink="true">https://forum.cloudron.io/topic/12964/mounting-error-for-restore-during-server-migration</guid><dc:creator><![CDATA[ntnsndr]]></dc:creator><pubDate>Thu, 19 Dec 2024 05:49:46 GMT</pubDate></item><item><title><![CDATA[DigitalOcean port 25 unblocking]]></title><description><![CDATA[We can not help you. You have your answer. Look for VPSes which unblock port 25. I frequent lowendtalk and lowendbox for this.
]]></description><link>https://forum.cloudron.io/topic/12802/digitalocean-port-25-unblocking</link><guid isPermaLink="true">https://forum.cloudron.io/topic/12802/digitalocean-port-25-unblocking</guid><dc:creator><![CDATA[scooke]]></dc:creator><pubDate>Thu, 14 Nov 2024 13:14:34 GMT</pubDate></item><item><title><![CDATA[trying to connect my domain]]></title><description><![CDATA[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 .
]]></description><link>https://forum.cloudron.io/topic/11950/trying-to-connect-my-domain</link><guid isPermaLink="true">https://forum.cloudron.io/topic/11950/trying-to-connect-my-domain</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Thu, 20 Jun 2024 18:48:47 GMT</pubDate></item><item><title><![CDATA[Digital Ocean Issues after altering Droplet name?]]></title><description><![CDATA[@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?
]]></description><link>https://forum.cloudron.io/topic/11892/digital-ocean-issues-after-altering-droplet-name</link><guid isPermaLink="true">https://forum.cloudron.io/topic/11892/digital-ocean-issues-after-altering-droplet-name</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Tue, 11 Jun 2024 14:06:06 GMT</pubDate></item><item><title><![CDATA[Error when restoring whole Cloudron - box:dns/waitfordns Attempt X failed. Will retry: queryNs ENOTFOUND]]></title><description><![CDATA[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.
]]></description><link>https://forum.cloudron.io/topic/11887/error-when-restoring-whole-cloudron-box-dns-waitfordns-attempt-x-failed-will-retry-queryns-enotfound</link><guid isPermaLink="true">https://forum.cloudron.io/topic/11887/error-when-restoring-whole-cloudron-box-dns-waitfordns-attempt-x-failed-will-retry-queryns-enotfound</guid><dc:creator><![CDATA[AmbroiseUnly]]></dc:creator><pubDate>Mon, 10 Jun 2024 17:26:03 GMT</pubDate></item><item><title><![CDATA[Cloudron on DigitalOcean one-click issue]]></title><description><![CDATA[ok, thank you
]]></description><link>https://forum.cloudron.io/topic/11467/cloudron-on-digitalocean-one-click-issue</link><guid isPermaLink="true">https://forum.cloudron.io/topic/11467/cloudron-on-digitalocean-one-click-issue</guid><dc:creator><![CDATA[zodiacstar123]]></dc:creator><pubDate>Wed, 03 Apr 2024 15:12:00 GMT</pubDate></item><item><title><![CDATA[DO managed DNS on Cloudron v7.5.2]]></title><description><![CDATA[@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.
]]></description><link>https://forum.cloudron.io/topic/11191/do-managed-dns-on-cloudron-v7-5-2</link><guid isPermaLink="true">https://forum.cloudron.io/topic/11191/do-managed-dns-on-cloudron-v7-5-2</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Mon, 26 Feb 2024 23:19:06 GMT</pubDate></item><item><title><![CDATA[Cert renewing failing]]></title><description><![CDATA[@girish said in Cert renewing failing:

@visuex are you the same as @cpa ?

Nope, not me!
]]></description><link>https://forum.cloudron.io/topic/11171/cert-renewing-failing</link><guid isPermaLink="true">https://forum.cloudron.io/topic/11171/cert-renewing-failing</guid><dc:creator><![CDATA[cpa]]></dc:creator><pubDate>Fri, 23 Feb 2024 15:14:36 GMT</pubDate></item><item><title><![CDATA[DigitalOcean port 25 unblocking]]></title><description><![CDATA[@Lanhild I sent a reply to them again. They've finally opened the port.
]]></description><link>https://forum.cloudron.io/topic/11155/digitalocean-port-25-unblocking</link><guid isPermaLink="true">https://forum.cloudron.io/topic/11155/digitalocean-port-25-unblocking</guid><dc:creator><![CDATA[Lanhild]]></dc:creator><pubDate>Wed, 21 Feb 2024 18:13:27 GMT</pubDate></item><item><title><![CDATA[Bug in DO DNS propgation]]></title><description><![CDATA[Please update to Cloudron 7.6.4 where it is fixed already. The DigitalOcean API behavior had changed recently.
]]></description><link>https://forum.cloudron.io/topic/10974/bug-in-do-dns-propgation</link><guid isPermaLink="true">https://forum.cloudron.io/topic/10974/bug-in-do-dns-propgation</guid><dc:creator><![CDATA[nebulon]]></dc:creator><pubDate>Mon, 29 Jan 2024 06:40:42 GMT</pubDate></item><item><title><![CDATA[Installation Stuck at "Waiting for propagation of"]]></title><description><![CDATA[Setting up under the wildcard option worked. Hopefully the wider issue with DigitalOcean will get resolved.
]]></description><link>https://forum.cloudron.io/topic/10875/installation-stuck-at-waiting-for-propagation-of</link><guid isPermaLink="true">https://forum.cloudron.io/topic/10875/installation-stuck-at-waiting-for-propagation-of</guid><dc:creator><![CDATA[Alex-GWC]]></dc:creator><pubDate>Tue, 16 Jan 2024 03:23:48 GMT</pubDate></item><item><title><![CDATA[Certiticate renewal issue]]></title><description><![CDATA[@Recliner2042 It needs to write to DNS . You can read more at https://letsencrypt.org/docs/challenge-types/ (dns-01).
]]></description><link>https://forum.cloudron.io/topic/8910/certiticate-renewal-issue</link><guid isPermaLink="true">https://forum.cloudron.io/topic/8910/certiticate-renewal-issue</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Thu, 30 Mar 2023 19:28:10 GMT</pubDate></item><item><title><![CDATA[DigitalOcean Discount or Credit Link from Cloudron?]]></title><description><![CDATA[Specifically, the DO refcode is 933831d60a1e .
]]></description><link>https://forum.cloudron.io/topic/8841/digitalocean-discount-or-credit-link-from-cloudron</link><guid isPermaLink="true">https://forum.cloudron.io/topic/8841/digitalocean-discount-or-credit-link-from-cloudron</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Sun, 19 Mar 2023 01:36:50 GMT</pubDate></item><item><title><![CDATA[Cannot Restore from Cloudron Backup on Digital Ocean Spaces]]></title><description><![CDATA[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.
]]></description><link>https://forum.cloudron.io/topic/8230/cannot-restore-from-cloudron-backup-on-digital-ocean-spaces</link><guid isPermaLink="true">https://forum.cloudron.io/topic/8230/cannot-restore-from-cloudron-backup-on-digital-ocean-spaces</guid><dc:creator><![CDATA[robi]]></dc:creator><pubDate>Sat, 17 Dec 2022 23:28:19 GMT</pubDate></item><item><title><![CDATA[DigitalOcean token management change]]></title><description><![CDATA[@girish Thanks—seems to be working.
]]></description><link>https://forum.cloudron.io/topic/8115/digitalocean-token-management-change</link><guid isPermaLink="true">https://forum.cloudron.io/topic/8115/digitalocean-token-management-change</guid><dc:creator><![CDATA[ntnsndr]]></dc:creator><pubDate>Tue, 29 Nov 2022 21:49:32 GMT</pubDate></item><item><title><![CDATA[DKIM setup for Cloudron]]></title><description><![CDATA[@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 --&gt; Email --&gt; Status --&gt; 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...

]]></description><link>https://forum.cloudron.io/topic/7434/dkim-setup-for-cloudron</link><guid isPermaLink="true">https://forum.cloudron.io/topic/7434/dkim-setup-for-cloudron</guid><dc:creator><![CDATA[humpty]]></dc:creator><pubDate>Thu, 28 Jul 2022 10:52:16 GMT</pubDate></item><item><title><![CDATA[Cloudron digitalocean instance can't access the dashboard after adding a new domain]]></title><description><![CDATA[@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.
]]></description><link>https://forum.cloudron.io/topic/7015/cloudron-digitalocean-instance-can-t-access-the-dashboard-after-adding-a-new-domain</link><guid isPermaLink="true">https://forum.cloudron.io/topic/7015/cloudron-digitalocean-instance-can-t-access-the-dashboard-after-adding-a-new-domain</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Fri, 13 May 2022 01:03:20 GMT</pubDate></item><item><title><![CDATA[Domain nameservers are not set to DigitalOcean]]></title><description><![CDATA[@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.
]]></description><link>https://forum.cloudron.io/topic/5343/domain-nameservers-are-not-set-to-digitalocean</link><guid isPermaLink="true">https://forum.cloudron.io/topic/5343/domain-nameservers-are-not-set-to-digitalocean</guid><dc:creator><![CDATA[rosano]]></dc:creator><pubDate>Mon, 12 Jul 2021 20:00:17 GMT</pubDate></item><item><title><![CDATA[Backup import fails on new Cloudron instance]]></title><description><![CDATA[@yusf OK, thanks, when you find time, feel free to reach on the support mailbox.
]]></description><link>https://forum.cloudron.io/topic/4296/backup-import-fails-on-new-cloudron-instance</link><guid isPermaLink="true">https://forum.cloudron.io/topic/4296/backup-import-fails-on-new-cloudron-instance</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Thu, 28 Jan 2021 12:40:26 GMT</pubDate></item><item><title><![CDATA[DigitalOcean Space Backup Failed - SlowDown: Reduce your request rate.]]></title><description><![CDATA[Will mark this as solved since this is a DO issue.
]]></description><link>https://forum.cloudron.io/topic/3762/digitalocean-space-backup-failed-slowdown-reduce-your-request-rate</link><guid isPermaLink="true">https://forum.cloudron.io/topic/3762/digitalocean-space-backup-failed-slowdown-reduce-your-request-rate</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Fri, 20 Nov 2020 19:05:38 GMT</pubDate></item><item><title><![CDATA[Namecheap and Digital Ocean  DNS Problems.]]></title><description><![CDATA[@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.
]]></description><link>https://forum.cloudron.io/topic/3420/namecheap-and-digital-ocean-dns-problems</link><guid isPermaLink="true">https://forum.cloudron.io/topic/3420/namecheap-and-digital-ocean-dns-problems</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Wed, 14 Oct 2020 20:22:24 GMT</pubDate></item><item><title><![CDATA[VPC networking on digital ocean]]></title><description><![CDATA[@greycloud said in VPC networking on digital ocean:

I kind of had assumed that they would continue working, if I did nothing. But would they stop working if I enable VPC?

My understanding is there is nothing to enable. The existing droplets simply get assigned a pre-built default VPC.

Presumably if I setup a new cloudron it would be automatically wrapped in the VPC by default, but there would be no particular advantages.

Yes, I think so as well.
]]></description><link>https://forum.cloudron.io/topic/3101/vpc-networking-on-digital-ocean</link><guid isPermaLink="true">https://forum.cloudron.io/topic/3101/vpc-networking-on-digital-ocean</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Mon, 31 Aug 2020 09:43:17 GMT</pubDate></item><item><title><![CDATA[Certificate renewals and app updates fail -- D.O. API expired]]></title><description><![CDATA[@girish Will do. It's actually not the first time I've run into the problem and a re-fresh of the API credentials solved the problem, although this is the first time I specifically observed that it was a 500 error vs. a 401.
]]></description><link>https://forum.cloudron.io/topic/2401/certificate-renewals-and-app-updates-fail-d-o-api-expired</link><guid isPermaLink="true">https://forum.cloudron.io/topic/2401/certificate-renewals-and-app-updates-fail-d-o-api-expired</guid><dc:creator><![CDATA[jegillikin]]></dc:creator><pubDate>Tue, 28 Apr 2020 21:09:05 GMT</pubDate></item><item><title><![CDATA[Restarting a DO Droplet]]></title><description><![CDATA[@imouthesmp You can just restart the droplet. No need to stop/shutdown apps. All the apps and Cloudron dashboard will start automatically after a reboot. You can also resize the droplet (CPU/Disk/RAM) as you see fit and Cloudron will adapt automatically.
]]></description><link>https://forum.cloudron.io/topic/2152/restarting-a-do-droplet</link><guid isPermaLink="true">https://forum.cloudron.io/topic/2152/restarting-a-do-droplet</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Tue, 11 Feb 2020 00:15:58 GMT</pubDate></item><item><title><![CDATA[Easiest VPS for Cloudron with one click install.]]></title><description><![CDATA[@marcusquinn Yeah. I was in a fraternity when I was in college. It was like the movie Animal House... but worse. Looking back on it I'm embarrassed by what I did. But it was fun at the time. College itself was a big waste of time for me.
]]></description><link>https://forum.cloudron.io/topic/2027/easiest-vps-for-cloudron-with-one-click-install</link><guid isPermaLink="true">https://forum.cloudron.io/topic/2027/easiest-vps-for-cloudron-with-one-click-install</guid><dc:creator><![CDATA[yeku]]></dc:creator><pubDate>Mon, 09 Dec 2019 00:09:12 GMT</pubDate></item><item><title><![CDATA[Accessing MongoDB using Compass]]></title><description><![CDATA[Compass guide is here - https://docs.cloudron.io/guides/connect-mongodb/#mongodb-compass
]]></description><link>https://forum.cloudron.io/topic/1967/accessing-mongodb-using-compass</link><guid isPermaLink="true">https://forum.cloudron.io/topic/1967/accessing-mongodb-using-compass</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Wed, 23 Oct 2019 19:54:44 GMT</pubDate></item><item><title><![CDATA[How does Cloudron handle DigitalOcean Floating IP addresses?]]></title><description><![CDATA[Okay, that makes sense. Thank you for the quick reply. 
I wonder if it would make sense to add a feature where we can set the IP address to accommodate floating IP's in providers like DigitalOcean, so that the DNS records automatically setup by Cloudron in DigitalOcean would be using the floating IP instead. Without such a feature, it kind of removes the ability to have a sort-of manual failover method which is one of the main purposes of a floating IP from DigitalOcean (along with a secondary use-case of setting up a new server to replace an old one and moving the floating IP to the new one when ready, eliminating the need to update a whole bunch of DNS records). It would be nice, I think, to have Cloudron use a floating IP that we give it even if it means we have to set it manually in Cloudron first since it can't detect it automatically. The main reason for this is that whenever I switch a server, for example, nothing really needs to be changed at all, leaving downtime to a minimum if it exists at all during a server switch.
]]></description><link>https://forum.cloudron.io/topic/1812/how-does-cloudron-handle-digitalocean-floating-ip-addresses</link><guid isPermaLink="true">https://forum.cloudron.io/topic/1812/how-does-cloudron-handle-digitalocean-floating-ip-addresses</guid><dc:creator><![CDATA[d19dotca]]></dc:creator><pubDate>Wed, 19 Jun 2019 00:28:56 GMT</pubDate></item></channel></rss>