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

Windows 7 / Mac install login dialog don't work #81

Closed
MTRichards opened this issue Nov 14, 2012 · 2 comments
Closed

Windows 7 / Mac install login dialog don't work #81

MTRichards opened this issue Nov 14, 2012 · 2 comments
Assignees
Labels

Comments

@MTRichards
Copy link

Install ownCloud 1.1.2 pre on Windows 7. At the end, a nice little checkbox asks if I want to "run ownCloud" So I check that. This brings up a "welcome to ownCloud" windows. However, once you are in this windows, if you try to connect to the server using this wizard, it will NOT work. Even with the proper accounts.

Also tested on Mac 10.7 and the same thing happened.

The client says:
Trying to connect to ownCloud at http://192.168.1.44/owncloud...
Successfully connected to http://192.168.1.44/owncloud: ownCloud version 4.5.2 (4.90.3)

Local sync folder C:/Users/Matt\ownCloud already exists, setting it up for sync.

Remote folder creation failed probably because the provided credentials are wrong.
Please go back and check your credentials.
Connection to ownCloud could not be established. Please check again.

However, if you click finish at this point, and then right click on the system tray and select configure, you can now use the SAME credentials and access ownCloud. I tried it 4 times on Windows 7 just to be sure, and it is repeated every time.

ownCloud 4.5.2, desktop client 1.1.2 pre (Wed morning version).

@ghost ghost assigned dragotin Nov 14, 2012
@danimo
Copy link
Contributor

danimo commented Nov 14, 2012

I can reproduce this. This only happens on the very first start after a new installation (settings dir purged) and is probably related to the new credentials store: mirall (csync) basically seems to send an empty base64 string as basic auth. Restart the client: all is peachy, but obviously because the credentials did not work, no folder gets set up. However, login works now.

@dragotin
Copy link
Contributor

This is fixed with 01e8c9d

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

No branches or pull requests

3 participants