Cloudron Forum

@sebastienserre it's probably the ipv6 reverse DNS aka rDNS aka PTR which you set via your VPS provider and not by your DNS provider

@sebastienserre said:

Any idea what is happening ?

likely your ipv6 issue I'd guess

@mononym it's actuall really easy to install this using the LAMP app, just follow these simple steps from @gengar :

https://forum.cloudron.io/post/115931

You literally copy paste each of the 6 blocks of code one by one and then it's done.

@james said:

Hello @jdaviescoates
The ooc tool is called this way https://docs.cloudron.io/packages/nextcloud#running-occ-tool

sudo -u www-data php -f /app/code/occ $COMMAND

Thanks, that worked.

@james I'd like to get to the bottom of why my rsync Nextcloud and Jellyfin backups always fail the integrity check.

I'm pretty certain it's not something happen during the backup process because if that were the case it'd only happen on some rare occasions when I'm active during the backup process, but it is literally every single rsync back up with both of these apps.

Nextcloud always seems to say:

Failed to verify 2026-05-31-000001-449/app_office.uniteddiversity.coop_v5.8.2: Cannot read properties of undefined (reading 'size')

and

Jellyfin similarly always seems to say:

Failed to verify 2026-05-31-000001-449/app_media.uniteddiversity.coop_v1.13.7: Cannot read properties of undefined (reading 'size')

So both seem to be having the same issue:

Cannot read properties of undefined (reading 'size')

It doesn't happen on my other Nextcloud instance.

Any idea how we might get to the bottom of it?

BTW: out of interest I figured I'd try doing what you suggested previously (even though I don't really see how that'd help us work out what's going on) I tried to put the Nextcloud into maintenance mode using this command as per https://docs.nextcloud.com/server/stable/admin_manual/maintenance/backup.html#maintenance-mode

$ sudo -E -u www-data php occ maintenance:mode --on

But that just returned:

bash: $: command not found

@Beardmancer said:

PV6 checks are not green (is that an issue?):

Yes, quite possibly.

@james I'm on mobile on a train.

It obviously is trying to do OIDC because that actual URL it's at is https://my.uniteddiversity.coop/openid/interaction/gBxXyLN46NPdakIokzKWVMhLaCWOHERhmVZpX0nUQeh

I'd guess the issue is with Nextcloud OIDC plugin.

I'm also unable to login to my Nextlouds and I'm still on 9.17

I don't get the screen you get though, just the standard login screen with a passkey option but no OIDC.

I had also previously changed some config somewhere so that the standard login screen wasn't displayed and it only have OIDC option, which normally meant it just logged in without doing anything as I'm already logged into Cloudron

Ah, I'm using Firefox not Brave, I guess that's why it's all OK for me.

It's working for me. But often I find after an OnlyOffice update I need to go back into /settings/admin/onlyoffice in Nextcloud and re-save the settings in there. Give that a try?

thanks, one of my instances seemed to be effected by this

@james said:

With the Dry run restore when taking this path you can also ensure that everything is working as intended reducing possible downtimes.

Exactly

@james said:

Upgrade Ubuntu 20 to 22

Follow the guide https://docs.cloudron.io/guides/upgrade-ubuntu-22

If everything worked out upgrade to 24
Upgrade Ubuntu 22 to 24

Follow the guide https://docs.cloudron.io/guides/upgrade-ubuntu-24

If everything worked out, perfect.

Just to say, personally rather than doing this, I tend to just spin up a new server with the new version on and then restore the back-up to the new server. Quicker and less prone to issues imho but also not always an option.

Also the standard "hack" to skip versions (you can't) is to set auto-updates to happen ever hour until it's caught up.

I just tried them too - so easy! Can literally copy paste it all as is and then it's done! @gengar

@alwynispat https://docs.cloudron.io/server#default-data-directory

@james said:

Please follow these steps if you have this issue:

Can this script be run on the working version I reverted to, or do I need to update to the broken version and then run it?

Edit: yes, it seems fixing the db and then updating also works fine.

I also had a not responding app and have reverted. Guess I need to look at that guide...

@davejgreen said:

I tried again with a fresh install of Ubuntu 24.04

@davejgreen said:

Maybe different versions of Ubuntu do it differently?

I think the only time I've had issues with migrations was when the provider of my VPS (I think it was Netcup) began using stripped down versions of Ubuntu that had stuff Cloudron needs missing.

But I'm guessing you're pulling Ubuntu directly from Ubuntu?

jdaviescoates said:

@LoudLemur said:

@jdaviescoates RustFS is available in unstable now. Would that suit?

I think someone has packaged Garage too.

I don't know if either would suit, but hopefully.

SeaweedFS is available now too

https://forum.cloudron.io/topic/15435/seaweedfs-is-now-available

@davejgreen said:

on the new server, I created my user before installing cloudron

FYI, afaict all the issues you've faced were caused by you doing something that isn't needed

e.g. the above creating a user, plus editing hosts files stuff mentioned previously.

I've migrated my Cloudron server probably 3 or 4 times without any issues