Cloudron Forum

Thank you, that has resolved the issue!

Perfect @BrutalBirdie .. Thanks a lot Man! What's this error? And how can we prevent this moving forward. Thanks!

It seems to be indeed the long volume names. This also explains the strange connection between setting up a backup and the changing view. Thanks for the explanation. I have not seen this connection...

@flaxxain RainLoop app is long deprecated . Consider using SnappyMail , Roundcube or SOGo

Cloudron will call the app locally by the URL http://${app.containerIp}:${manifest.httpPort}${manifest.healthCheckPath} so by local container IP at the specified httpPort and healthCheckPath specified in the CloudronManifest.json. Any response with a 200 status code will be accepted.

@daixiwen Even better, they HAVE already allowed for specific backup persistence: [image: 1745912539127-704862fe-911a-4719-960b-94f162df1e64-image.png] I'm going to go try that out. The wording definitely makes it sound like at least one backup, "the latest backup", should be available, but my point still stands. As perfect as Cloudron is, I've bumped into hiccups with backups myself, too. And so I pay close attention to them. In the situation you mentioned, you can either let your stopped app backups keep disappearing while you wait for a solution, or you can realize it needs a bit of your help. EDIT: I see you wrote " I'll now try having at least one manual backup set up as persistent and see in two says if it's still there, but ideally this should occur automatically." so good on you for taking it into your own hands. Let us know what happens!

Think of each as a SaaS, I think the "correct" approach is to upload files in one app. That app exposes an API. Other apps then consume the photos API to do whatever . The whole sharing files approach is a relic of times when files were hosted on the same server and no sandboxing. But modern deployment/orchestration tech uses sandboxing, containers, docker compose, multiple servers . In such situations, sharing files assuming it's all code runs in same file system doesn't work well. app permissions/owner issues aside, most apps also have a database to track files and store extra metadata . If you remove and delete files from the filesystem without the app's knowledge, it all breaks. apps have to be written with all this in mind and most apps aren't written this way . lychee/nextcloud etc all have their own db and cannot share fs with others.

I changed the mail server here. The DNS was updated and no SSL errors.

Is this happening midway and has there already been some data restored at /home/yellowtent/boxdata/mail/... or is this the first file which fails there? Also what are the permissions and owner for /home/yellowtent/boxdata/ ?

Nevermind, I did a rollback and fixed it

@msbt Great, already got it running. Thank you!!

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.