A day later the app-token for the Android-Dav5x fails to work, so it might not have something to do with reboot or server outages.
It might just be a random thing or a time-based thing.
Is there such a thing as “app-tokens get invalidated after a configured time”?
No public access to this resource., Username or password was incorrect, No 'Authorization: Bearer' header found. Either the client didn't send one, or the server is mis-configured, Username or password was incorrect
The Nextcloud-App on Android:
Token is not valid: Token is too short for a generated token, should be the password during basic auth
I will leave the notify_push backend online, since I figure that only the desktop app and probably not the android app (can’t see anything in the logs that it does) use the notify_push backend, while all my other services seem to invalidate their app-tokens
I detangled the admin-account from the user-account to make sure that the account that it is happening to is not special
for no apparent changes the app-passwords dropped out of being valid one by one: NC-app on android, then Dav5x-app on android, then caldav-usage on thunderbird and NC-app on the desktop probably at the same time.
I use only separate logins to the webinterface, create a QR-Code/App-Token and then do not log out but close the (incognito/private) browser window.
I try to rule out the suspicion, that something/someone invalidates some app-token and therefore all other app-tokens that were created within the same session will also be invalid after some short timespan.