After authenticating once with the browser based scheme it should remember the credentials and use that when starting the client the next time.
It always asks for credentials at start.
Client version: 2.6.2
Operating system: Fedora 31
OS language: English
Qt version used by client package (Linux only, see also Settings dialog): Qt 5.13.2
Client package (From Nextcloud or distro) (Linux only): nextcloud-client-2.6.2-1.fc31.src.rpm
Installation path of client: /usr/bin/nextcloud
Nextcloud version: 17.0.2.1
Storage backend (external storage):
Client logfile: https://gist.github.com/epsilontheta/6ddfd7b1057e19562a57e061a7f4abb6
Web server error log:
Server logfile: nextcloud log (data/nextcloud.log):
This has been troubling me too for the past two weeks or so, although sometimes it does work.
Server version: 15.0.13
Client version: 2.6.2
Distro: elementary OS
Sanitised client log: https://gist.github.com/veddox/9e294ef45b61cf9510b8e53b247eab0b
Both log files contain the error Unable to read "user_clientCaCertificatePEM0:https://cloud.example.com/:0" chunk "0"
In my case, the app segfaults immediately after login.
I have similar behaviour on Windows 10 with Client 2.6.2
I don't need to login after every single client restart, but every 1-2 day or so
This didn't happen with older Nextcloud client versions
This issue is known for long time and devs claimed it was fixed in 2.6.2 (so they closed these issues), but problem was never fixed:
https://github.com/nextcloud/desktop/issues/1292
https://github.com/nextcloud/desktop/issues/1655
Hopefully it will be fixed...
I'm having the same issue on Linux Mint 19.3 (Xfce if that matters in any case) which is based on Ubuntu 18.04.1. After every reboot Nextcloud is asking for authentication. libgnome-keyring0(was a dependency so it came preinstalled) and libgnome-keyring-common won't fix it. Didn't try the AppImage yet but that's not really an alternative for me. If you need any further details (logfiles e.g.) let me know.
Can confirm with
Version 2.6.2git. For more information please click here.
This release was supplied by Nextcloud GmbH
Built from Git revision 1d7455 on Dec 24 2019, 12:35:56 using Qt 5.14.0, OpenSSL 1.1.1d 10 Sep 2019
on
Archlinux / Xfce
I have the same problem.
Does not happen on my other machine (Arch) also running 2.6.2git but with the difference that I set it up using an older client and server version.
Same issue here on macOS.
Client version: 2.6.2
Server version: 18.0.0.10
Same issue, Windows 10. Happens every 1-2 days. Started once server was updated from 16 to 17, although it could still be tied to client version.
Client version: 2.6.3
Server version: 17.0.3
Also upgraded from 2.6.2 to 2.6.3, problem still exists.
Same here with KDE neon 5.18.2, clients 2.6.3 and 2.6.4. I have 5 accounts at the moment and need to re-authorize those at each and every boot - can we upvote this as "Most Annoying Bug"?
It was debugged some time ago https://github.com/nextcloud/desktop/issues/1292#issuecomment-560008811, but it seemed to be fixed only in Fedora.
It certainly is a very annoying bug, pretty extended.. It may be worthwhile investing a little more time on it :)
Honestly, I already lost hope on this... :)
In the meantime i was able to mitigate this problem by installing gnome-keyring - anyway, not certain which side effects this might have.
I am having this problem on Arch Linux machine, while everything is ok on 2 Win10 machines.
Client version 2.6.3
@epsilontheta and the others, can you confirm that this is a duplicate of #1292?
I'm no longer getting this issue, most likely since update 17.0.4.
How about the others? Most seemed to be using Linux setups.
Still have the same problem on all (3) KDE machines.
I don't know actually.
The behaviour of my application seems a little bit different. My app shows simply "signed out from mydomain.tld as user" after few days of use (no restart of computer).
I cannot reproduce this issue currently.
OS: macOS
Client Version: 2.6.4 (updated from 2.6.2)
Server Version: 18.0.0.10
KDE key storage seems to differ frome GNOME. Might be Nextcloud only handles the GNOME way correctly. This would explain why installing GNOME packages seems to solve the problem. Correct me, if I'm wrong.
@claell yes that is the same bug except that I did not have this delay where it shows "no connection". After installing libgnome-keyring the problem seems to be gone for my setup.
The same here (gnome-keyring "fixes" the problem) - https://github.com/nextcloud/desktop/issues/1292#issuecomment-609370244 - but I really don't want to install this stuff on my KDE system just for NC to work.
Hm, I am not sure how to track this, as it might have a different cause than #1292. Currently it seems unclear, whether #1292 was actually fixed but there are issues with other environments (then it might be closed and the issue on other environments can be tracked here) or whether #1292 was not fixed properly (then this would be a duplicate and all should be tracked in #1292). I will leave both issues open for now.
Can confirm the problem for both of my systems.
One is a Arch Linux setup using the newest sync-client.
The other one is a Windows10 Computer also using the newest version of the client.
Same issue with Gentoo Linux and i3 WindowManager. Extremely annoying.
I observe this issue with the latest version of the Nextcloud client on Windows 10, Debian Buster with KDE Plasma, and macOS 10.13. It is a very annoying behaviour. I never experienced this behaviour with the OwnCloud client, where I could explicitly specify the app-specific credentials in the client.
Please, give us an option to store credentials encrypted inside the application.
KDE key storage seems to differ frome GNOME. Might be Nextcloud only handles the GNOME way correctly. This would explain why installing GNOME packages seems to solve the problem. Correct me, if I'm wrong.
Confirm this. I've just switched from elementary OS (with the Pantheon desktop) to Ubuntu 20.04 (with GNOME), and the issue is gone.
Same issue on Manjaro Stable (Fluxbox Desktop).
Installing gnome-keyring solved the problem. . . but this is not a suitable fix for me.
Tried with kwallet-manager but didn't work.
Win10 with desktop client v2.6.4stable-Win64 (build 20200303); NC v18.0.4 and the problem persist
Most helpful comment
This issue is known for long time and devs claimed it was fixed in 2.6.2 (so they closed these issues), but problem was never fixed:
https://github.com/nextcloud/desktop/issues/1292
https://github.com/nextcloud/desktop/issues/1655
Hopefully it will be fixed...