Kolab 3.1 SSL Chwala and Free-Busy

Josh Janszen joshjanszen at gmail.com
Thu Nov 21 16:03:17 CET 2013


I was able to get it working in roundcube by setting peer and host setting
to false, but I believe that is not the correct way. What would need to be
changed to allow host and peer to be enabled and work? I am still not able
to access via /chwala and recieve the error PHP Error: Login failed. Unable
to connect to ssl://xxx.xxxx.com:443. Error #0:  (POST)

I followed this tutorial https://gist.github.com/dhoffend/7008915

Thanks,
Josh


On Sun, Nov 17, 2013 at 3:25 PM, Josh Janszen <josh.janszen at yhnmail.com>wrote:

> All,
>
> I am struggling to get a fully functional Kolab 3.1 install on CentOS 6.4.
> I have configured httpd.conf to redirect all traffic on port 80 to
> https://website.com. Is this the correct way to configure a full https
> install? This method worked perfect for Kolab 3.0 minus the free-busy URLs.
> No on my 3.1 install the files portion does not load and I receive an error
> when accessing website.com/chwala. Also free-busy does not work correctly
> and cannot look up others free-busy urls. I have looked over
> https://issues.kolab.org/show_bug.cgi?id=2149, but all attachments/fixes
> seems to be removed. Should the stable 3.1 have these fixes incorporated?
> Bottom line is how do I correctly configure Kolab 3.1 via Https only and
> have files/free-busy working.
>
> Thanks,
> Josh
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20131121/eb47a7e2/attachment.html>


More information about the users mailing list