I did wonder earlier is a hacked instance of WordPress (or even just WordPress malicious or badly designed plugin) could potentially be the culprit. Seems worth investigating.

Usually apps are setup to log to stdout/stderr where possible, then the logging and cleanup is managed by the platform. It is possible that for some apps we have missed some configs or have to add log rotation manually within the app then. In which apps besides snipe-it do you see this behavior?

Thanks @girish In a shipping container in DE, will have to investigate once I get back Not least because I don’t understand about settings but will dive in

@SunDevil I'll keep sharing... I've tried Nextcloud on several different platforms, including JUST Nextcloud. It ALWAYS conks out on me. Always. So, my 2 cents, you'll have the same issue on Dokploy. EDIT: Have you even checked out Dokploy??? I just watched their intro video. They install their software on your VPS from their servers! What?? Sorry, I'm not letting some third party have that access to my data. You create your ssh key on their system!!! You have to create a db separate from your app!!! Good luck keeping track of all those deets. Holy smokes, the number of steps needed to get this thing running is exactly why most of us have come to Cloudron. This Dokploy is so at the opposite spectrum of Cloudron. I can't imagine anyone thinking it will be "better".

Hi @joseph , Yes, your new instructions at https://docs.cloudron.io/storage/ were very helpful! However, I still had to manually restart the services on the /services page in the Cloudron admin panel. Regarding the time it takes to reindex disk information, it happened within the same day for me. I’ll continue monitoring the system's stability over the next few days to ensure everything is running smoothly. Thank you so much for your help! Thanks to your assistance, I was finally able to resolve the issue with running out of disk space

If the system runs out of disk space, a lot of side-effects can happen, so this could very well be the root cause then.

Ok, it seemed running the /home/yellowtent/box/setup/start.sh to trigger the migration after restoring the database (because of the ERROR 1046 (3D000) at line 22: No database selected i needed to add these two lines to the dump file: CREATE DATABASE box; USE box; Then it was able to backup the database and run the migration.

Thank you @nebulon ... it's awesome timing , thanks for the share! I guess that should be considered a solved problem for the future then.

Right so we have a bunch of similar topics referencing the same problem. https://forum.cloudron.io/topic/13162/unable-to-send-emails-to-gmail https://forum.cloudron.io/topic/13145/problems-with-sending-mail https://forum.cloudron.io/topic/13122/email-sending-broken-after-updating-to-8-2-x-due-to-ipv6-issues https://forum.cloudron.io/topic/13072/gmail-ipv6-anyone-else-with-this-experience Should they all be merged and/or marked as solved? The solution is provided by @girish (here) and @jdaviescoates (here) which I'll compile and summarise here again: Activate IPv6 on Cloudron via going to Network > IPv6 > Configure > Public IP Check your IPv6 address either via reading the IPv6 address detected by Cloudron when doing 1. or via running curl https://ipv6.api.cloudron.io/api/v1/helper/public_ip on your server (via ssh). Set an IPv6 PTR record on your VPS/server provider (not your domain provider) for the above IPv6 address. The next Cloudron release will implement a check on IPv6 PTR record like it currently does for IPv4. If using Wildcard DNS then create a * AAAA record for the above IPv6 address. If things still don't work, you can go to Cloudron -> Domains -> hit Sync DNS If your VPS provider does not allow you to set IPv6 PTR, then run on your server (via ssh) sysctl -w net.ipv6.conf.ens18.disable_ipv6=1 (replace ens18) for specific interface to disable IPv6 on your server. After you do this, also disable IPv6 in Cloudron, Network -> IPv6 -> Disable.

@privsec yeah netcup says that but it may only takes a few minutes. You can check your PTR record propagated in various ways, for example: https://toolbox.googleapps.com/apps/dig/#PTR/ https://www.whatsmydns.net/#PTR

I followed the instructions, now the child sites work but the main network site isn't,

You have to install nginx and put those configs on the server where you deployed odoo . That is the correct place for putting those multiple port configs. Then nginx will then answer to a single port 80 which you can then put into cloudron.

Looks like this part does fix it (instructions for root server): [image: 1737492462373-9fbbe904-6e2e-4deb-8d7d-5d2812a54c83-image.png] Thanks to you both for the pointers!

I have added the provider by now https://git.cloudron.io/platform/box/-/blob/master/dashboard/public/js/setup.js?ref_type=heads#L71

Thanks for the information

A homemade problem. We have refactored our Ansible role. It has installed an MTA that was previously started as Cloudron's mail service. After uninstalling the MTA, everything works as expected.

Sorry, i should have checked that first. Downgrading CF proxy to DNS only does seem to fix the issue for me. Thanks @nebulon.

@luckow give postgresql more memory