@girish don't know what happened but the auto-backups are working again

I try to avoid puttting screenshots in our docs because they become obsolete in 6 months. Given the amount of 3rd party services we integrate with, it's impossible for us to track UI changes across all the services. I just link to the docs like in https://docs.cloudron.io/backups/#linode-object-storage If something is really super popular, I make a "guide" with screenshots.

worked

@girish yes.

Looks like some collectd related failure (if those are the last log lines): readonly launchpad="https://launchpad.net/ubuntu/+source/collectd/5.12.0-9/+build/23189375/+files" cd /tmp && wget -q "${launchpad}/collectd_5.12.0-9_amd64.deb" "${launchpad}/collectd-utils_5.12.0-9_amd64.deb" "${launchpad}/collectd-core_5.12.0-9_amd64.deb" "${launchpad}/libcollectdclient1_5.12.0-9_amd64.deb" cd /tmp && apt install -y --no-install-recommends ./libcollectdclient1_5.12.0-9_amd64.deb ./collectd-core_5.12.0-9_amd64.deb ./collectd_5.12.0-9_amd64.deb ./collectd-utils_5.12.0-9_amd64.deb && rm -f /tmp/collectd_*.deb echo -e "\nLD_PRELOAD=/usr/lib/python3.10/config-3.10-x86_64-linux-gnu/libpython3.10.so" >> /etc/default/collectd Can you run the above manually line by line and check if it works ?

@avatar1024 there is crash in cert renewal indeed. A fix is coming in 7.5.2

Just to be clear though, this will just restart the box process which just takes a few seconds and its not an actual server reboot. A slightly bigger issue is, that the certs won't renew automatically until the fix is out, this can be done manually until that using the renew all certs action in the domains view. So if you are on 7.5 at the moment just click that button in the next few days.

@xarp in the past I had built a custom php app that did exactly what you’re asking for. A simple registration page for a Cloudron user. I plan on implementing some form of group allocation and eventually subscription/payments. If you’d like we can talk about me making you a custom version of the app

@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!

@girish yes, that was the issue. These links helped: https://docs.cloudron.io/troubleshooting/#unbound https://forum.cloudron.io/topic/2106/dns-status-tool-reports-null-on-all-records?

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!