For some reason my users that were set up through the webconfig cant access owncloud. Any user for owncloud must be created separately in the owncloud admin web page.
Am I doing something wrong? The users are enabled but its not taking the username and password for the user
Am I doing something wrong? The users are enabled but its not taking the username and password for the user
In Groupware
Share this post:
Responses (24)
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Using Internet explorer 10, browse tohttps://yourdomain/owncloud
Accept the self-signed certificate warning, click the 'certificate error' in the address bar on the right hand side. Click view certificates > install certificate. Then go through the wizard but choose specific store location to install (don't let it automatically guess), and select trusted root certificates.
You can check with the 'certmgr.msc' snap-in first? -
Accepted Answer
-
Accepted Answer
I eventually managed to connect via Windows7 explorer using WebDAV. i made the registry change, imported the webserver certificate into the trusted root certificates, and then connected using only the hostname... for some reason it didn't like using the FQDN
net use X: https://hostname/owncloud/remote.php/webdav /user:user1 password1
-
Accepted Answer
Looks like it's an SSL negotiation issue with Windows 7. IE has better TLSv1.2 support than the legacy WinHTTP code which is only SSL or TLSv1.0. You'll need to import your servers certificate into your trusted root certificate authorities (Start -> run -> certmgr.msc).
https://forum.owncloud.org/viewtopic.php?f=17&t=21656
https://forum.owncloud.org/viewtopic.php?f=23&t=11246&sid=6a27183e7ac9b73a77c777083138820b -
Accepted Answer
Been there, done that
It gets as far as presenting a certificate and then fails (in the GUI), The command line map gives the 1244 error. It's possible to connect using IE and the same map command - that gves you the option to store the certificate (again!), but the 'map network drive' from Explorer doesn't. I think I've tried every possibility and - until I know otherwise - I think it's a Windows issue .. certainly Google is awash with people complaining that they can't get a webdav drive mapped. I haven't tried a Linux map yet, but CyberDuck works fine so long as the trailing '/' is specified. -
Accepted Answer
I'll try and replicate it
Have you seen the following?
http://doc.owncloud.org/server/7.0/user_manual/files/files.html -
Accepted Answer
I'm still getting a problem with Webdav access. I can connect using cyberduck or the owncloud desktop client, but not using Windows 7 network drive mapping (net use) - that still reports a 1244 and not authenticated.
The owncloud installation went through an upgrade, so I repeated your init-ldap command, but with the same effect. -
Accepted Answer
OK, thanks, will patch the install to cope with this scenario, but more importantly did manually running the script fix your user login issue?
FYI the webconfig users are all stored in LDAP, so if the owncloud LDAP config is now updated you should be able to login. Don't forget to enable owncloud for the user first via the webconfig users menu
EDIT: our posts crossed, great! thanks for your feedback, have pushed the patched version to the build system -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
This is the outpu i got and i can access Owncloud web interface with no problem:
[root@clearos ~]# /usr/clearos/apps/owncloud/deploy/install
Updating privileges
Updating existing config.php with system database settings
Call to owncloud URL failed - is the webserver running? - rerun install
[root@clearos ~]# -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Same problem here with a fresh install of Owncloud the option in enabled in the user properties but i'm unable to log in with the user only the built in admin user is working. Here is the output of my Owncloud version:
app-owncloud-core-1.3.6-1.v6.noarch
app-owncloud-extension-core-1.1.1-1.v6.noarch
owncloud-7.0.2-1.v6.noarch
app-owncloud-1.3.6-1.v6.noarch
owncloud-3rdparty-7.0.2-1.v6.noarch -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Hi, that's not right the webconfig users should be able to access owncloud - sounds like the LDAP installation isn't configured properly
What version of Owncloud are you using? 'rpm -qa | grep -I owncloud'
If you have installed from the marketplace you can try rerunning the setup script with the following and post the output
/usr/clearos/apps/owncloud/deploy/install
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »