-
Notifications
You must be signed in to change notification settings - Fork 763
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Desktop client gets stuck in loop when trying to authenticate on Linux #1192
Comments
I get the same problem on the OSX release (2.5.2 via Edit edit edit: Disabling E2E encryption fixes it - seems to be the same bug as here: #977 |
Now fixed by setting sudo nextcloud.occ config:system:set overwriteprotocol --value="https" For anyone following this, I'm prefixing In my case, SSL is being handled by Cloudflare so Nextcloud was unaware that it was being used. At least, that's what I've gathered by reading https://help.nextcloud.com/t/stuck-in-a-login-loop-when-logging-in-from-sync-client-on-linux/47549/6 It would be great if the desktop client provided more feedback as to why it's not connecting successfully rather than saying nothing and looping the login procedure. |
Nice, thanks! I have Nextcloud behind a Caddy reverse proxy so that explains it for me, too. Re-enabled E2E and all is well with the world again. |
Expected behaviour
The desktop client authenticates with the remote Nextcloud instance and I progress to whatever the next stage of the wizard is.
Actual behaviour
I get stuck in a loop of being asked to authenticate.
Steps to reproduce
I then get stuck in a loop of the last 3 screens.
Client configuration
Client version:
2.5.2git
Operating system:
KDE Neon 5.15
OS language:
?
Qt version used by client package (Linux only, see also Settings dialog):
I don't see this.
Client package (From Nextcloud or distro) (Linux only):
nextcloud-client
viappa:nextcloud-devs/client
Installation path of client:
Server configuration
Installed via
snap
.Operating system: Ubuntu 18.04
Nextcloud version: 15.0.5
The text was updated successfully, but these errors were encountered: