Seems like a few issues intermixed here. For a start userland proxy in docker should be false. This set however in /etc/systemd/system/docker.service.d/cloudron.conf by the cloudron startup script. On port 172.18.0.1:3003 the Cloudron docker proxy addon would listen, so this also hints at docker having an issue with the network bridge it supposed to have created. Otherwise most likely if you had a disk being 100% full situation, all bets are off, unfortunately. This is not so much related to Cloudron code but other linux services we use like mysql and docker

Thanks to everyone for the responses. I fully understand the backups now and have reported to my board that it's indeed production ready for our organization.

That worked @girish cloudron-support --troubleshoot found a certificate which does not exist and so removed a conf file nginx started promptly After which the Cloudron apps could be restarted just fine Thank you once again for your help

Could you please convert that thread into a request to remove 'Cloudron' from the mail templates as well as from translation files, please?

@nebulon I appreciate your advice. The backup server is not on the same location as the cloudron server. It isn't even on the same country (like I do with all my backups). Maybe I wasn't clear: the server has an OS disk (nvme) and a HDD for backups. The mount I showed is the HDD disk mount. It was just to check if any filesystem mount options were needed to improve performance. Thank you all.

It was not fail2ban - it was IPv6 connection which is failing, as IPv6 disabled (to ensure mail works well). Hetzner's supported provided a very quick and efficient verification / troubleshooting step: ssh -vvv -p 23 user@server - hope that will be of use for anyone else in the future.

I will close this for now since it's not meant to be run directly . We can continue in the other thread or we can open a new thread .

I think there may be an issue in the mapping between the Synology LDAP and Cloudron LDAP If you look at the first screenshot provided by imc67, we have the option to select which LDAP profile to use. If you use the standard profile, you immediately run into the issues that imc67 described. However if you change the profile to custom (see screenshot below), everything checks out fine except for the "Check server schema" which goes away if one enables CIFS plain text authentication. But then you still get stuck when the Synology tries to join the Cloudron directory. [image: 1744372954639-4e73954b-31d8-4432-a657-ccab1fd989ca-image-resized.png] [image: 1744373380929-e85d7121-05fd-4a61-9082-c2ff648d3252-image-resized.png] [image: 1744373443601-809c7691-aae3-4fc0-bfe8-cec2cc30507f-image-resized.png] I'm trying to find the logs on the synology to get more details. Here are the synology docs for how to join a Synology NAS to an external LDAP directory: https://kb.synology.com/en-me/DSM/help/DSM/AdminCenter/file_directory_service_join?version=7

@SansGuidon said in Some struggles with Cloudron migration: pebkac What? Googling . . . PEBKAC stands for "Problem Exists Between Keyboard and Chair". It's a tech support term, often used humorously or dismissively, to indicate that a problem is caused by user error rather than a technical issue. In essence, it's attributing the problem to the user's actions or lack of understanding, rather than a software or hardware malfunction. AHHHHH! I know the German version "Das Problem sitzt vor dem Bildschirm" litteral translation "The problem is sitting in front of the screen". Nice one @SansGuidon said in Some struggles with Cloudron migration: it makes actually sense to refresh the guide reader about the network requirements Good point! Just a "remember your Network setup!" with a link to the other doc would be enough. Right? @SansGuidon said in Some struggles with Cloudron migration: Also maybe not everyone is willing to rely solely on Cloudron config for the security. Hetzner gives lot more power to users and control, and Cloudron sometimes feels a bit too vague. Let me be brutally honest with you. German mode enabled. 99% of users that use Cloudron do not have the knowledge and experience to proivde that. What Cloudron provides is enough for the 99%. Generally speaking, not targeted towards you. IMO everything further is "expert mode" and the expert should know what to do. And if the expert does not know how, he should either learn or pay. @SansGuidon said in Some struggles with Cloudron migration: As a power user (DevOps) and busy dad, Cloudron feels both nice or confusing/limited at times depending what I want to do I get that That is the gilded cage experience and to some extent necessary to keep support low. If you are working in DevOps, I've built multiple customer solutions with Cloudron, Cloudron Gitlab, Cloudron DockerRegistry and the Gitlabrunner to fully automate, development, staging and production deployments. It is possible, but you need a firm grasb on what Cloudron does and how it does things. Then you can make it do some crazy things. @SansGuidon said in Some struggles with Cloudron migration: The mounts issues errors were for most related to network. The message must be clearer. Error message improvment. Everyone can benifit from that. Should there be a normal message with a button "more details" for power users like you and me? @SansGuidon said in Some struggles with Cloudron migration: I could use Hetzner for DNS but we have already a long term subscription with Hostinger for several domains so we are anyway still stuck a bit. Also I could argue that putting all my eggs on same provider is risky. I had an outage with Contabo in the past where both VPS and Backups location were impacted. this kind of situation is a pain in the ass. Egg Basket, agreed. If not Hetzner, some other supported DNS provider that fits your needs so you get rid of the manuall labor? => https://docs.cloudron.io/domains/ My top picks in no order are: https://desec.io/ Cloudflare Hetzner DigitalOcean @SansGuidon said in Some struggles with Cloudron migration: And I wanted to contribute this thread in the hope to open a debate about this and improve the overall experience. Yes please! Always and more of that. What ever you find that is "meh", report it in the forum. Everyone benefits.

I just had the issue while attempting to migrate to a new Cloudron restore, at the step of restoring a full backup and this despite following exactly the steps in Cloudron guide for restoring backups. I quickly solved it through: Reviewing unbound service status shows everything looked ok I had a doubt about the private key password being good, as the backup configuration didn't clarify that in the UI. I just put my private key password again, and attempted the restore button, this time it works. So it's good to mention maybe in the guide that the private key password should be double checked even if using a preexisting backup configuration generated from the previous Cloudron instance.

Using tgz instead of rsync did let the backup run normally, at least once right now. Let's call this a workaround for now, I'll see if this works regularly.

@potemkin_ai & @kk_cloudron On my side I was also having the issue "queryNs ETIMEOUT" , and it was because my outbound UDP port 53 was not open. I just had to add it like that on my Hetzner Cloud Firewall : [image: 1744283926608-7bf48621-4935-4413-af8d-775b9a05abe2-image-resized.png]

I use netcup too, I disabled IPv6 on the server entirely and since everything has been working with no issues. Though disabling IPv6 persistently on reboot was not straightforward and had to be done modifying netplan config, see above on the thread (https://forum.cloudron.io/post/102554).

@joseph Okay, it's solved. It works a bit differently than with Infomaniak, since Infomaniak doesn't allow you to modify outbound firewall rules yourself — for example, you have to open a support ticket to request outbound access to port 25. With Hetzner, I just had to get used to their setup: I needed to manually open the outbound port on the Hetzner Cloud firewall side. : https://docs.cloudron.io/security/#cloud-firewall Outbound ports¶ We recommend leaving all outbound ports open. Some providers like AWS EC2, Google Cloud, Digital Ocean forcefully block outbound port 25 for reducing email spam. The only way around this is to either request your server provider to unblock this port or better to setup an Email relay. It was a dumb issue hahaha omg I need some sleep.

Yes. It is.

I can't quite make out why it's crashing . @lukasgabriel if possible, can you write to support@cloudron.io and I can debug this further ?

Due diligence is as easy as checking out https://www.cloudron.io/pricing.html. Most services online make it that easy. The ones that don't, I just skip. By the way, by leaving Cloudron that must mean you've opted to use something else. I am curious what you've found, or had, that makes it worth not using Cloudron.

Thank you. That was my issue. I've followed the instructions on that thread and then truncated the syslog files which were around 50GB in size.

I am generally not in the group of AI = bad, however it likely just lacks lots of knowledge about the Cloudron internals, which make recommendations often not very useful in this area (yet). Overall I am still not sure based on this thread why DNS was involved here and given that you hit 3 different addons with apparently diverse issues, maybe something unrelated to them individually caused the trouble. We will add a few more helpers to the cloudron-support script for the future, to hopefully get down to such issues faster. If you haven't deleted the server yet, maybe we could take a closer look via SSH, since you already invested much time in debugging. If you want that, please enable remote ssh support and send a mail to support@cloudron.io with your Cloudron details.

We are reworking the notification UI for Cloudron 9 at the moment and the reboot required hint will be fixed accordingly there. It has caused quite a few misunderstandings in the past as it currently is