Skip to content
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

Unable to grant access to users with spaces in username (Windows 10, Linux, macOS clients) #1018

Closed
KBlixt opened this issue Jan 14, 2019 · 25 comments

Comments

@KBlixt
Copy link

KBlixt commented Jan 14, 2019

so yeah, I'm unable to grant access to my server from my windows 10 machine because I have a space in my user name. I get prmpted to log in after pointing to my server and log in works well but then When I should click "grant access" the loading wheel just spins for ever... logging in to any account without a space in the user name works as expected.

am I missing something or is this a bug?

I'm running the latest mariadb/nexcloud docker releases on an Ubuntu 18.04 machine and trying to access it from the latest windows 10 client. I don't think that anything that I've configured on my server should affect this since I can login to my server from my android client as well as the browser client.

I'm watching the log table while the loading wheel spins and the only thing that appear there are two failed login attempts at approximately 30 seconds intervals after pressing the "grant access" button. (although I think the 30 seconds intervals is a result of that my ip address have failed too many log in attempts.)

don't know how to troubleshoot this any further.

@KBlixt KBlixt changed the title Unable to log in to users with spaces in username. (windows 10 client) Unable to grant access to users with spaces in username. (windows 10 client) Jan 14, 2019
@victorbw
Copy link

unfortunatley the reference was not the same error.

nonetheless, I can confirm this error happens on recently upgraded NC 15.0.2 and can reproduce it.

@rullzer if you need some credentials let me know.

@rullzer
Copy link
Member

rullzer commented Jan 17, 2019

Yes please 😄

@victorbw
Copy link

victorbw commented Jan 17, 2019

@rullzer meet me here: LINK DEPRECATED

@KBlixt
Copy link
Author

KBlixt commented Jan 18, 2019

I can also provide login credentials if needed.

@victorbw yeah, I saw the topic and managed to solve it for him since I had the same issue before I had this issue.

@rullzer
Copy link
Member

rullzer commented Jan 18, 2019

@KBlixt always good to have more to test. Could you send them to roeland @ nextcloud.com

@KBlixt
Copy link
Author

KBlixt commented Jan 18, 2019

I sent two logins, one with spaces in the username that isn't working and one without space which works.

@KBlixt
Copy link
Author

KBlixt commented Feb 4, 2019

@rullzer any update on this?

@nblock
Copy link

nblock commented Feb 7, 2019

This is also reproducible on Linux Mint 19.1 with

  • Nextcloud Client 2.3.3 (appimage)
  • Nextcloud Client 2.5.0 (appimage)
  • Nextcloud Client 2.5.1 (Bionic PPA)

on Server 14.0.6 and 15.0.2

@Wikinaut
Copy link

Hello Team, we (users and admins with a legal(!) space character in their user names) urgently need a fix for this issue - it is not limited to the Windows10 desktop clients, but also to Linux clients.

@Wikinaut Wikinaut changed the title Unable to grant access to users with spaces in username. (windows 10 client) Unable to grant access to users with spaces in username (Windows 10 and Linux clients) Feb 17, 2019
@Wikinaut Wikinaut changed the title Unable to grant access to users with spaces in username (Windows 10 and Linux clients) Unable to grant access to users with spaces in username (Windows 10, Linux, macOS clients) Feb 17, 2019
@AndyScherzinger
Copy link
Member

@rullzer could you reproduce this issue with a user name containing a space?

@Wikinaut
Copy link

I tested with a second instance, same issue. Desktop people, wake up and fix this regression please.

@Wikinaut
Copy link

@AndyScherzinger I don't see any progress to fix this apparent regression.

@rullzer
Copy link
Member

rullzer commented Feb 26, 2019

Did you test the latest rc https://download.nextcloud.com/desktop/prereleases/Windows/Nextcloud-2.5.2.5117-rc1-20190205.exe ?

This should be fixed in the RC. At least I have been unable to trigger it.

@Wikinaut
Copy link

@rullzer No: I use Nextcloud Desktop on Debian and LinuxMint.

@Tom31100
Copy link

Waiting for a fix, you can use OWNcloud client. It's working for the space in login names. I don't know for the space in filenames

@victorbw
Copy link

victorbw commented Feb 28, 2019

Did you test the latest rc https://download.nextcloud.com/desktop/prereleases/Windows/Nextcloud-2.5.2.5117-rc1-20190205.exe ?

This should be fixed in the RC. At least I have been unable to trigger it.

@rullzer @Tom31100 @KBlixt @Wikinaut works fine now, also with folders which have whitespace in its name.

Environment:

  • W7x64 Professional
  • Desktop Client 2.5.2.5117-rc1-20190205
  • NC 15.0.4

grafik

@Wikinaut
Copy link

I need the debian and ubuntu versions.

@victorbw
Copy link

@rullzer just got a message that MacOSx Clients are affected as well.

@victorbw
Copy link

victorbw commented Feb 28, 2019

@Wikinaut
Copy link

Wikinaut commented Mar 2, 2019

@victorbw I do not use Appimages on my machines.

@Wikinaut
Copy link

Wikinaut commented Mar 5, 2019

It seems to be fixed by 5ebee92

@camilasan
Copy link
Member

Shall I close this ticket then?

@Wikinaut
Copy link

Wikinaut commented Mar 6, 2019

This issue is not solved for users of the current release 2.5.1, I don't know your policy regarding "closing" issues (I suggest to leave it open until the 2.5.2 is released).

@victorbw
Copy link

victorbw commented Apr 5, 2019

This issue is not solved for users of the current release 2.5.1, I don't know your policy regarding "closing" issues (I suggest to leave it open until the 2.5.2 is released).

According to the repo, 2.5.2 is out: https://download.nextcloud.com/desktop/releases/Windows/Nextcloud-2.5.2-setup.exe

Ive tested the new release under Windows 7 environment, and the issue seems to be fixed in this version.

@jancborchardt
Copy link
Member

Thanks a lot for confirming @victorbw, closing hence. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants