-
Notifications
You must be signed in to change notification settings - Fork 804
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
Comments
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. |
Yes please 😄 |
@rullzer meet me here: LINK DEPRECATED |
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. |
@KBlixt always good to have more to test. Could you send them to |
I sent two logins, one with spaces in the username that isn't working and one without space which works. |
@rullzer any update on this? |
This is also reproducible on Linux Mint 19.1 with
on Server 14.0.6 and 15.0.2 |
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. |
@rullzer could you reproduce this issue with a user name containing a space? |
I tested with a second instance, same issue. Desktop people, wake up and fix this regression please. |
@AndyScherzinger I don't see any progress to fix this apparent regression. |
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 No: I use Nextcloud Desktop on Debian and LinuxMint. |
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 |
@rullzer @Tom31100 @KBlixt @Wikinaut works fine now, also with folders which have whitespace in its name. Environment:
|
I need the debian and ubuntu versions. |
@rullzer just got a message that MacOSx Clients are affected as well. |
@Wikinaut there you go: https://download.nextcloud.com/desktop/prereleases/Linux/Nextcloud-2.5.2.20190205-rc1-x86_64.AppImage |
@victorbw I do not use Appimages on my machines. |
It seems to be fixed by 5ebee92 |
Shall I close this ticket then? |
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. |
Thanks a lot for confirming @victorbw, closing hence. :) |
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.
The text was updated successfully, but these errors were encountered: