Kolab using SeaFile as an add-on

Mon Jan 11 16:54:48 CET 2016

HI,

Am 10.01.2016 um 23:44 schrieb Erika Mustermann:
> I am currently trying to configure Kolab using SeaFile as an add-on. 
> To this point, I seem to have successfully setup SeaFile, and when 
> using the documentation 
> <https://docs.kolab.org/howtos/use-seafile-with-chwala.html>, I 
> succeed in configuring it to interface with LDAP. After changing the 
> configuration of Roundcube in "/etc/roundcubemail/config.inc.php", an 
> option appears in the "FILES" section enabling me with the possibility 
> to add SeaFile storage, but when I try to add it, I get the error 
> "Unable to authenticate user".
>
> The corresponding entries in "/var/log/chwala/errors" resp. 
> "/var/log/chwala/console" are:
>
> "[10-Jan-2016 14:37:21,000000 +0100]: <l4kor3pp> PHP Error: Unable to 
> connect to ssl://example.org:443 <http://example.org:443>. Error: 
> Connection timed out in 
> /usr/share/pear/HTTP/Request2/SocketWrapper.php on line 108 (POST 
> /chwala//api/?method=folder_create?_task=&_action=)"
>
> "[10-Jan-2016 14:37:11,000000 +0100]: <l4kor3pp> SeaFile POST: 
> https://example.org/api2/auth-token/, POST: 
> {"username":"john.doe at example.org 
> <mailto:john.doe at example.org>","password":"*"}
> [10-Jan-2016 14:37:21,000000 +0100]: <l4kor3pp> SeaFile Response [550]: "
>
I got the same problem on a system where the kolab services are not 
secured and have the same idea like you. But at the moment i didn´t have 
the time to change the config to secure services.
> I initially thought that this might be linked to the fact that I 
> hadn't secured the services and I therefore first went on with that. 
> However, the only change I got was that the error in 
> "/var/log/chwala/console" now states:
> "[10-Jan-2016 17:31:40,000000 +0100]: <l4kor3pp> SeaFile POST: 
> https://example.org/api2/auth-token/, POST: 
> {"username":"john.doe at example.org 
> <mailto:john.doe at example.org>","password":"*"}
> [10-Jan-2016 17:31:40,000000 +0100]: <l4kor3pp> SeaFile Response 
> [404]: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> <html><head>
> <title>404 Not Found</title>
> </head><body>
> <h1>Not Found</h1>
> <p>The requested URL /api2/auth-token/ was not found on this server.</p>
> </body></html>"
>
> Is anyone able to succeed with the configuration?
>
>
> Thanks for any help provided!
>
>
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users

-------------- n?chster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: <http://lists.kolab.org/pipermail/users/attachments/20160111/02c53643/attachment.html>