Tobias Knöppler

It's possible, but not easy, because we would have to fetch all available nextcloud server versions. However, the update mechanism of NCP will probably change over the course of the...

Sounds like the underlying issue that prevented you from logging in is, that you had too many ssh keys lying around on your machine. SSH will attempt to login with...

Please don't expose Telegram users publicly (because those aren't public data) :) Sorry for editing the issue. One of the users you are looking for is @Pant - I don't...

Good find, thank you

Please run an earlier docker container (e.g. 1.49.1) and upgrade your nextcloud from there. I'm working on a way to prevent this situation.

Compare https://github.com/nextcloud/nextcloudpi/issues/1628

Okay looks like your container was corrupted in some way by the update. Please try the following: 1. restore from a backup with the image version v1.49.1 2. upgrade nextcloud...

Thank you. Btw, I noticed that the token transferred during registration via Github has a slightly different key than mentioned in the error message (`federatedToken` instead of `federated_token`).

This will be fixed in the next release, thanks to @m-breitbach

Do you have a (manually created) swap file inside your nextcloud directory?