Cloudron Forum

Had to move my cloudron to different server. I was on 20.04 running 7.5.2. Initially I provisioned an Ubuntu 24.04 server but when I tried to install cloudron I got the error:

Cloudron >= 8.0.0 required for installation on Ubuntu 24.04

So I killed that server and provisioned an Ubuntu 22.04 server and restored my Cloudron to that.

Now that I've updated my Cloudron on the Ubuntu 22.04 server to V8 is it worth it to move it again to an Ubuntu 24.04 server? Or leave well enough alone?

I'm leaning yes to restoring again to 24.04 while I've got the restore procedure in my head. I might as well get a couple extra years before having to remember how to do this again.

Your thoughts?

Thx. How will I access the control panel on the original server because the dns for the control panel url will have been moved to the new server?

So I just got this error:

Cloudron >= 8.0.0 required for installation on Ubuntu 24.04

Do I migrate twice? First to Ubuntu 22.04 in order to update the Cloudron software and then to the desired 24.04?

I'm planning to move my 14-app Cloudron to a new server.

All of the apps use Cloudron's amazing automated remote DNS record creation/deletion service... except for one app.

There could be a delay of a few days or a week before I can get the person who has access to the DNS records for me to walk him through changing the DNS for the one manual app..

I don't want to wait a week to migrate.

Can I have 13 apps running on the new server and the 1 app running on the old server for a week. Will that work? Thoughts?

I found that I was using that domain name as an alias for another app.

So I'm trying to uninstall an app. Some time ago I used the alias feature so that the app could be accessed via a second domain name.

I no longer own that second domain name. So when I try to uninstall the app, the Cloudron DNS is trying to un-register it via the API to Namecheap where the DNS is but alas my account there doesn't have any access to that domain which I let go. But that error stops the whole uninstall process.

What do I do?

Thanks.

When I try to remove a domain from /#/domains I'm getting the error message,
Domain is in use in an app's location

But it is not being used as an app's location.

What do I do now?

Thanks

I am moving my whole Cloudron to a new server.

In the restore Cloudron docs it says:

Install Cloudron on a new server with Ubuntu LTS (20.04/22.04/24.04)

My current Cloudron is installed on an Ubuntu 20.04 server.

I'd like to run Ubuntu 24.04 on my new server.

Is it okay to restore my Cloudron which is currently running on Ubuntu 20.04 to an Ubuntu 24.04 server?

(I understand that my Cloudron backup needs to be restored to a server that is running the same version of Cloudron -- in my case 7.5.2.)

I've got some questions.

My current set-up:

• Cloudron v7.5.2 (Ubuntu 20.04.2 LTS) on dedicated server with 12GB memory and 100GB of disk space. I'm currently using 65GB of disk. I can't upgrade Cloudron because my server doesn't have AVX; 7.6.1 requires AVX support. (My current web host --small excellent company-- sold to an owner who has ghosted the customers. No support of any kind. I fear every day my server will stop running; so I've got some urgency.)
• 15 apps: 6 Drupal, 4 Wordpress, Nextcloud, yourls, urls, Sogo Mail, Surfer (none of the sites have a lot of traffic) All the apps are up-to-date

I'm planning to move to Linode (Akamai).
I'm considering these two plans for the moment:

1. Dedicated CPU, 8 GB Ram $72/mo 4cpus 160 GB storage
2. High Memory Plan 24 GB Ram $70/mo 2cpus 20 GB + 100GB attached volume

I've had terrible experience with shared CPUs in the past. I know the technology is better now (I've been on a dedicated CPU for 10 years) but I'm still very hesitant even thought there isn't a ton of traffic on the sites I host.

I'd really appreciate any advice y'all could give.

I'm getting this error when trying to clone an app:

DNS Error: DNS A Record is not synced yet: ETRYAGAIN

The original is on test.example.com and I'm trying to clone to example.com

No other app is set to example.com.

Before attempting the clone I ran "Sync DNS" at /#/domains

Thanks.

@girish
Yes.

Thanks @girish. Won't restart after the recommended edit of config.php. Here is the error:

=> Healtheck error: Error: connect ECONNREFUSED 172.18.17.145:80
OCP\HintException: [0]: Downgrading is not supported and is likely to cause unpredictable issues (from 30.0.4 to 29.0.3.4) ()

@girish followed your instruction but I'm getting the following in the logs after a restart of the Nextcloud App says "Not responding":

An unhandled exception has been thrown:
Jan 11 22:12:08OCP\HintException: [0]: Downgrading is not supported and is likely to cause unpredictable issues (from 30.0.4.1 to 29.0.3.4) ()code_text

Ideas?

Yes, really stupid, there were reasons which I don't want to go into here.

This seems to happen to me every couple of years... I fill the hard drive and it crashes Nextcloud and I have a hard time restarting Nextcloud. I have read through the previous threads I've started on this topic.
I removed lots of file allowing for plenty of hard drive space. I dealt with the unbound issue and restarted that service.
In terms of replacing config/config.php with a version from a backup, the most recent version I had was from 2023, oops. I got an error from that file about it being an old version. So then I just tried inserting

  'installed' => true,

into the current version. The error messages I'm getting now after clicking on "Start app" are

OCP\HintException: [0]: Configuration was not read or initialized correctly, not overwriting /app/code/config/config.php ()

and

Jan 09 17:30:43=> Healtheck error: Error: connect EHOSTUNREACH 172.18.17.145:80

I'd really appreciate help in getting my Nextcloud running again. Thank you.

p.s. @girish Do you think I need to worry that I installed unbound on my Proxmox server when it wasn't already installed. Would it be best to uninstall it? So far that server is behaving normally. (Understood that this question is better for Proxmox support, but since I'm here I thought I'd ask.)

@girish

unbound-anchor -a /var/lib/unbound/root.key
systemctl restart unbound

That solved it. Thank you.

Actually when I said that unbound had disappeared I was wrong. I was logging into proxmox and not into the vm instance that Cloudron is installed on.

So here is what I get when I run sudo systemctl status unbound

unbound.service - Unbound DNS Resolver
     Loaded: loaded (/etc/systemd/system/unbound.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2023-11-07 19:57:26 UTC; 1 day 18h ago
    Process: 136690 ExecStart=/usr/sbin/unbound -d (code=exited, status=1/FAILURE)
   Main PID: 136690 (code=exited, status=1/FAILURE)

Here is the results when I run sudo journalctl -xe

-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The unit unbound.service has entered the 'failed' state with result 'exit-code'.
Nov 09 14:48:01 cloudron systemd[1]: Failed to start Unbound DNS Resolver.
-- Subject: A start job for unit unbound.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit unbound.service has finished with a failure.
-- 
-- The job identifier is 6829 and the job result is failed.
Nov 09 14:48:01 cloudron systemd[1]: unbound-resolvconf.service: Start request repeated too quickly.
Nov 09 14:48:01 cloudron systemd[1]: unbound-resolvconf.service: Failed with result 'start-limit-hit'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The unit unbound-resolvconf.service has entered the 'failed' state with result 'start-limit-hit'.
Nov 09 14:48:01 cloudron systemd[1]: Failed to start Unbound DNS server via resolvconf.
-- Subject: A start job for unit unbound-resolvconf.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit unbound-resolvconf.service has finished with a failure.
-- 
-- The job identifier is 6914 and the job result is failed.
Nov 09 14:48:02 cloudron dockerd[1027]: time="2023-11-09T14:48:02.273332749Z" level=warning msg="[resolver] failed t>
Nov 09 14:48:02 cloudron dockerd[1027]: time="2023-11-09T14:48:02.273332829Z" level=warning msg="[resolver] failed t>
Nov 09 14:48:02 cloudron kernel: Packet dropped: IN=ens18 OUT= MAC=be:b5:b4:54:73:5d:cc:16:7e:fe:d5:bc:08:00 SRC=77.>
Nov 09 14:48:04 cloudron sshd[975466]: Invalid user ubuntu from 157.245.248.106 port 32892
Nov 09 14:48:04 cloudron sshd[975466]: Received disconnect from 157.245.248.106 port 32892:11: Bye Bye [preauth]
Nov 09 14:48:04 cloudron sshd[975466]: Disconnected from invalid user ubuntu 157.245.248.106 port 32892 [preauth]
Nov 09 14:48:07 cloudron containerd[751]: time="2023-11-09T14:48:07.033719922Z" level=info msg="loading plugin \"io.>
Nov 09 14:48:07 cloudron containerd[751]: time="2023-11-09T14:48:07.033820380Z" level=info msg="loading plugin \"io.>
Nov 09 14:48:07 cloudron containerd[751]: time="2023-11-09T14:48:07.033864607Z" level=info msg="loading plugin \"io.>
Nov 09 14:48:07 cloudron containerd[751]: time="2023-11-09T14:48:07.034526543Z" level=info msg="starting signal loop>
Nov 09 14:48:07 cloudron dockerd[1027]: time="2023-11-09T14:48:07.272761873Z" level=warning msg="[resolver] failed t>
Nov 09 14:48:08 cloudron containerd[751]: time="2023-11-09T14:48:08.041835032Z" level=info msg="loading plugin \"io.>
Nov 09 14:48:08 cloudron containerd[751]: time="2023-11-09T14:48:08.042041883Z" level=info msg="loading plugin \"io.>
Nov 09 14:48:08 cloudron containerd[751]: time="2023-11-09T14:48:08.042101487Z" level=info msg="loading plugin \"io.>
Nov 09 14:48:08 cloudron containerd[751]: time="2023-11-09T14:48:08.042903266Z" level=info msg="starting signal loop>
Nov 09 14:48:08 cloudron systemd[135408]: run-docker-runtime\x2drunc-moby-41a3b7fe444b03e8b7a7c6ed9cc3f5a06ce241b926>
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The unit UNIT has successfully entered the 'dead' state.
Nov 09 14:48:08 cloudron systemd[1]: run-docker-runtime\x2drunc-moby-41a3b7fe444b03e8b7a7c6ed9cc3f5a06ce241b9265d33e>
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The unit run-docker-runtime\x2drunc-moby-41a3b7fe444b03e8b7a7c6ed9cc3f5a06ce241b9265d33e4aa4fea9710e24e8c-runc.v1>
Nov 09 14:48:08 cloudron dockerd[1027]: time="2023-11-09T14:48:08.272658447Z" level=warning msg="[resolver] failed t>
Nov 09 14:48:08 cloudron dockerd[1027]: time="2023-11-09T14:48:08.292878947Z" level=info msg="ignoring event" contai>
Nov 09 14:48:08 cloudron containerd[751]: time="2023-11-09T14:48:08.294448724Z" level=info msg="shim disconnected" i>
Nov 09 14:48:08 cloudron containerd[751]: time="2023-11-09T14:48:08.294665687Z" level=warning msg="cleaning up after>
Nov 09 14:48:08 cloudron containerd[751]: time="2023-11-09T14:48:08.294743528Z" level=info msg="cleaning up dead shi>
Nov 09 14:48:08 cloudron containerd[751]: time="2023-11-09T14:48:08.306205120Z" level=warning msg="cleanup warnings >
Nov 09 14:48:08 cloudron systemd[1]: var-lib-docker-overlay2-25495d74de46f857703deef2058f832b14629672cc9db85d0768eea>
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The unit var-lib-docker-overlay2-25495d74de46f857703deef2058f832b14629672cc9db85d0768eea86a9c00a9-merged.mount ha>
Nov 09 14:48:08 cloudron systemd[135408]: var-lib-docker-overlay2-25495d74de46f857703deef2058f832b14629672cc9db85d07>
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The unit UNIT has successfully entered the 'dead' state.
Nov 09 14:48:09 cloudron dockerd[1027]: time="2023-11-09T14:48:09.218626204Z" level=info msg="ignoring event" contai>
Nov 09 14:48:09 cloudron containerd[751]: time="2023-11-09T14:48:09.218884187Z" level=info msg="shim disconnected" i>
Nov 09 14:48:09 cloudron containerd[751]: time="2023-11-09T14:48:09.218933362Z" level=warning msg="cleaning up after>
Nov 09 14:48:09 cloudron containerd[751]: time="2023-11-09T14:48:09.218944895Z" level=info msg="cleaning up dead shi>
Nov 09 14:48:09 cloudron containerd[751]: time="2023-11-09T14:48:09.229177162Z" level=warning msg="cleanup warnings >
Nov 09 14:48:09 cloudron systemd[135408]: var-lib-docker-overlay2-051dda0fdf9706bfcac8ed411508452ce3341b8a86abc30702>
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The unit UNIT has successfully entered the 'dead' state.
Nov 09 14:48:09 cloudron systemd[1]: var-lib-docker-overlay2-051dda0fdf9706bfcac8ed411508452ce3341b8a86abc30702a6591>
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The unit var-lib-docker-overlay2-051dda0fdf9706bfcac8ed411508452ce3341b8a86abc30702a6591e2ccda6ba-merged.mount ha>
Nov 09 14:48:10 cloudron dockerd[1027]: time="2023-11-09T14:48:10.272757872Z" level=warning msg="[resolver] failed t>
Nov 09 14:48:11 cloudron dockerd[1027]: time="2023-11-09T14:48:11.272730404Z" level=warning msg="[resolver] failed t>
Nov 09 14:48:11 cloudron dockerd[1027]: time="2023-11-09T14:48:11.272887082Z" level=warning msg="[resolver] failed t>
Nov 09 14:48:12 cloudron qemu-ga[733]: info: guest-ping called
Nov 09 14:48:13 cloudron dockerd[1027]: time="2023-11-09T14:48:13.272687634Z" level=warning msg="[resolver] failed t>
Nov 09 14:48:13 cloudron dockerd[1027]: time="2023-11-09T14:48:13.551502650Z" level=warning msg="[resolver] failed t>
Nov 09 14:48:14 cloudron dockerd[1027]: time="2023-11-09T14:48:14.068411675Z" level=warning msg="[resolver] failed t>
Nov 09 14:48:14 cloudron dockerd[1027]: time="2023-11-09T14:48:14.272804479Z" level=warning msg="[resolver] failed t>
Nov 09 14:48:17 cloudron dockerd[1027]: time="2023-11-09T14:48:17.272802505Z" level=warning msg="[resolver] failed t>
Nov 09 14:48:18 cloudron dockerd[1027]: time="2023-11-09T14:48:18.272898282Z" level=warning msg="[resolver] failed t>
Nov 09 14:48:19 cloudron dockerd[1027]: time="2023-11-09T14:48:19.272776359Z" level=warning msg="[resolver] failed t>
Nov 09 14:48:19 cloudron dockerd[1027]: time="2023-11-09T14:48:19.272790874Z" level=warning msg="[resolver] failed t>
Nov 09 14:48:21 cloudron sshd[975637]: Invalid user ubuntu from 157.122.157.198 port 36022
Nov 09 14:48:21 cloudron sshd[975637]: Received disconnect from 157.122.157.198 port 36022:11: Bye Bye [preauth]
Nov 09 14:48:21 cloudron sshd[975637]: Disconnected from invalid user ubuntu 157.122.157.198 port 36022 [preauth]
Nov 09 14:48:21 cloudron sudo[975639]: pam_unix(sudo:session): session opened for user root by cece(uid=0)

Thanks in advance for the help on my next step.

SSH, unbound seems to be completely gone. nothing at /etc/unbound