@girish Yes, all sorted, thank you for asking. Thanks to @robi's suggestion all we needed to do was the following: in terminal window for our WordPress app, at /app/code/wp-content/uploads we created a symlink (ln -s /media/ovitest ovitest) and then updated its permissions, just in case (chown -R www-data:www-data ovitest) then we could access the mp4 at https://<our_web_domain>/wp-content/uploads/ovitest/Red-cloud.mp4 Thank you very much all; we did enjoy finding the fix in the end. And of course we will make good use of it as we can now keep 10-20 GB of data, or even more, outside the WordPress data container, so out of the backup, but still reference this content on our website, which is great.

Just wanted to say I've also hit just this issue. Cleaning up the nginx app config files did the trick but I wonder if this can be avoided in the future? Or may be it has already be addressed and I'm only hitting it because of some legacy stuff from previous Cloudron version? (this instance is currently running 7.5.0 but hasn't had a fresh install in a long while).

@3246 very strange, I just tried a restore of Cloudron with SSFS now and it works. Not sure what's the best way to proceed here, but if you are blocked by this, can you write to support@cloudron.io and we can debug fruther ?

Not sure if relevant to your situation, but to bypass specific DNS entries you can also do: local-zone: example.com typetransparent local-data: "my.example.com A 172.18.0.1"

Thank you for your help. Website filing is to register the services provided by this server to improve network security. When I tried to use servers in other countries, it was very successful, thank you for your help, and wish you success in your work!

Many thanks for this. The function is not actually activated but for some reasons the client seem to apply some kind of spam filter (even though when I open my spam folder it explicitly says that spam filtering is not done by the client but by the server). Anyway I definitely know where to look now so THANK YOU for your help and sorry for the tangent as this is not a Cloudron issue

@girish oh my! The memory is not what it used to be I guest there is not much demand for this feature

@ghstandard that feature is coming in 7.5.1 which we will stage tomorrow.

I am still confused why they demand an answer from you, if your website is getting abused...

@warg Actually, I found a whole bunch of apps - https://paste.cloudron.io/pecoleyaqo.xml . I will fix the published ones.

Backups are fine now. it created a backup in the night and it succeeded. Only the backup from yesterday is broken according to the log and I still see the old (non existing) backup logs in the dropdown. So just a tiny bug and the backup system itself works fine. Thanks for confirming this and explaining how it works in the background!

@girish Thanks!

Fixed in 7.5.1

Right, the historic graphs data is not retained since it's all very server specific. And most likely won't even map properly to the new server. I can put a note in the docs.

@girish perhaps include printing memory usage as part of the stats in the logs

@nebulon said in App snapshot created but backup progress still pending: The tooltip should be shown in the progressbar in the apps grid. By now the progress status in the app configure view is directly displayed. I guess the UI has changed a bit since this topic was created few years ago. Aha it's shown in the apps grid, not the app page itself. [image: 1692197427840-f809cbef-c66c-45d7-9054-0369eb0ea542-image.png] OK, thats still helpful. Thanks @nebulon.

Not sure what a good solution to this is, but one reason why we have a memory limit, is that such processes are tamed to a certain extent and don't start accumulating memory caches until they take resources away from other apps.

@girish worked on the 20.x instance

Thanks for reporting. That is fixed with 7.5.1

@girish said in Database Access & Backups?: @sarah-white Good, was just checking since your comment got flagged as spam by the forum. Sounds much like replies produced by asking ChatGPT to me!