hello
I downloaded the NC Desktop client on two laptops within 1 hour.
I noticed that
a) both have different versions
b) the one from laptop1 does not connect automatically
DEB packages are no longer maintained by Nextcloud. Compiling from source is possible, but not worth the trouble.
Regarding the issue that Laptop1 does not connect automatically:
That’s a known issue in older client versions. Switch to the latest version (AppImage or Flatpak), and check if autostart is enabled in the client settings.
If you’re using KDE, verify under System Settings > Startup and Shutdown > Autostart.
hello @vawaver
i found out to have also older deb file on my computer - i deinstalled and use now the appimage (it show now also Nextcloud Desktop-Client Version 3.16.6 (Debian)
but still after a reboot - the client will not connect with the server.
if i push it a link to the browser open then i have to log in then the sync works again!
hello @vawaver
there is no entry into the kdewallet for nextcloud client.
when the laptop reboot it open direct the browser and have to enter the password to enter
If KWallet itself is running but no token is written after you log in, you’re probably hitting the well-known bug introduced in client 3.14: the AppImage sometimes fails to hand its OAuth token to the keyring, so every reboot opens the browser again.(GitHub, Nextcloud community)
What you can try
Option
Effect
Enable auto-unlock
sudo apt install kwallet-pam → log out/in. This unlocks KWallet during login; for some users the token finally sticks.(Arch Linux Forums)
That screen is Nextcloud’s normal OAuth / device-flow login page.
It appears whenever a desktop client (in this case the one identifying itself as “worker2 (Desktop Client – Linux)”) asks the server for a new access token.
“Anmelden” = enter your username / password (or an app-password).
“Zugriff gewähren” = grant the client permission to access your files.
The yellow box is just a security reminder: if you didn’t start the client, don’t grant access.
Because your token isn’t being saved (nothing lands in KWallet), the client has to repeat this step every reboot. Once KWallet stores the token correctly you’ll stop seeing this page.
Side note: I don’t speak German myself, so I’m reading that dialog through an online translator—apologies if I miss any nuance.
I have not a link for Appimage that you requested.
i found the file - downloaded - exchange it - reconfigured it - startet - and works as expexted!
have done a couple of reboot each time it just connects to my Server.
Now the App just complain because it is old and there is a new version, but thats OK
If you want the latest version on Debian 12, you have two main options:
