Is the question whether this is allowed? If so, yes. As @jdaviescoates said, the Cloudron version needs to match. The OS version can be different. As a precautionary measure take a VPS snapshot of your old 22.04 install before migrating.

@girish Thank you very much for the info. I didn’t manage to reply earlier, but I saved the backup configuration again and the morning backup completed successfully. I’ll also try upgrading to 9.0.15.

@dylightful If we can have access to your setup, can you write to me at support@cloudron.io ? Would love to debug and figure out why it's failing . Is this reproducible easily - meaning if you take a backup and restore, it fails?

@nebulon That's great. Apart from that, it seems to be running smoothly; it still takes time to propagate the usage stats, but that doesn't really affect us.

@archos said in Old system backups are not listed: and restoring an older app backup fails with the fsmetadata.json ENOENT error. Does this file exist in the storage?

There is no look-into-it. There is only do-it.

Hello @imc67 Now we can start analysing. Edit the file /home/yellowtent/platformdata/mysql/custom.cnf and add the following lines: [mysqld] general_log = 1 slow_query_log = 1 Restart the MySQL service in the Cloudron Dashboard. The log files are stored at /home/yellowtent/platformdata/mysql/mysql.log and /home/yellowtent/platformdata/mysql/mysql-slow.log. Let it run for a day or more. Then you can download the log files and see what queries run very often causing disk I/O.

@joseph ~~Now I have reseted the router and I still have the same problem. I guess it's my ISPs Cgnat that is the problem. It's strange. It has been working for almost a year with the same ISP and the Cgnat but suddenly it stopped to work. I guess it's the Cgnat that make it impossible to ping the public ip too. My apps with Cloudflare tunnels is working but the tunnel I created to the Cloudron dashboard gets bad gateway and host error from Cloudflare. What am I missing?~~ Now it's working. It was simple when I found it. I had forgot to activate No TLS Verify for the tunnel. Now it's working. Thank you for your help.

Ok, I reached out to Vultr Wednesday about it and they instructed me to contact Ya'll directly. Did a fresh install and it installed 8.0. Glad to see it's updated.

@philkunz said in Backups still not verified or what?: But that points to how important the e2e read back step is. absolutely, that is why we are adding the validation in the first place. Having checksums of what we expect is the first step, next then will be the task (can be quite heavy task, so this won't be automatic probably) to read back and recalculate the hashes.

I investigated this on support@ . The issue was that the server had an incredibly slow disk and the iops was really bad (like 30MB/s) . The VPS provider is fixing their raid configuration .

@james Your support is always unbelievably great - thank you so much!

The schema is documented in this file - https://git.cloudron.io/platform/box/-/blob/master/migrations/schema.sql?ref_type=heads . completed BOOLEAN DEFAULT false The id has to be unique in oidcClients table. Can you check why you have a duplicate? Maybe you can delete the dup entry and run the migration again.

Apologies, I got hung up on your point about the 'combination of search and filters' since I'm experiencing only getting the amount of entries that's set in the per_page value even when using only the search box without any additional filters active. I'm really looking forward to the rework then because right now even basic stuff like checking if a specific email was delivered or if a specific user logged in is a bit of a pain since I have to unfold the details of the first entries just to make the scrollbar appear to load more.

@joseph oh geez, ok thx ️

I had this happen at a recent upgrade to Cloudron 9. All apps but Vaultwarden were working, and the "Cloudron has no app configured for this domain" message was showing. Indeed, it was just a hard refresh to solve it in Zen / Firefox (how odd!)

We will show the domain, for which the API call failed, in the error message for a start with next release. https://git.cloudron.io/platform/box/-/commit/f421fd771ff0e0550381d012414a6c35c8fd2afe

@girish Thank you, girish for the update!

@girish Thanks ! I replaced the /home/yellowtent/box/src/storage/gcs.js with the patched version and don't get the "old backup not found" error. the backup is listed in System backups. everything seems to be fine ! Thanks a lot for your help !