Re: [SOGo] Web-Login not working after upgrading to 2.3.2

2015-09-17 Thread Peter Beck
On 09/17/2015 02:28 AM, Ludovic Marcotte wrote: > Try to delete all sessions from the table specified by > OCSSessionsFolderURL (/etc/sogo/sogo.conf), restart memcached and give > it an other try. Hi Ludovic, just removed everything from sogo_session_folders with "delete from

Re: [SOGo] Web-Login not working after upgrading to 2.3.2

2015-09-17 Thread Peter Beck
On 09/17/2015 02:40 PM, Peter Beck wrote: > So maybe there is some problem within my multi domain setup, this is the > only difference to the others server setup. Hi Ludovic, just found the issue: first I've commented all domains except a single domain and login to the webmail was working. Then

Re: [SOGo] Web-Login not working after upgrading to 2.3.2

2015-09-16 Thread Ludovic Marcotte
On 16/09/2015 20:16, Peter Beck wrote: Any other hints ? On top of my head, not really. Try to delete all sessions from the table specified by OCSSessionsFolderURL (/etc/sogo/sogo.conf), restart memcached and give it an other try. -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630

[SOGo] Web-Login not working after upgrading to 2.3.2

2015-09-16 Thread Peter Beck
Hi there, i've just updated to SOGo 2.3.2 on Debian Jessie 8.2 (Stable) and now I am unable (with any user) to log into the web interface. Thunderbird and EAS are still working with the same user accounts, no errors there. I have a multi-domain setup and none of the domains (all connected to the

Re: [SOGo] Web-Login not working after upgrading to 2.3.2

2015-09-16 Thread Ludovic Marcotte
On 16/09/2015 19:42, Peter Beck wrote: Anybody else with similar issues or knowledge how to solve ? Unless you forgot to copy/paste it, your authentication source is missing the IDFieldName parameter. That will result in unexpected behaviors. -- Ludovic Marcotte lmarco...@inverse.ca ::

Re: [SOGo] Web-Login not working after upgrading to 2.3.2

2015-09-16 Thread Peter Beck
On 09/17/2015 01:51 AM, Ludovic Marcotte wrote: > Unless you forgot to copy/paste it, your authentication source is > missing the IDFieldName parameter. That will result in unexpected > behaviors. Hi Ludovic, thanks for the fast response. I didn't had the IDFieldName set until now and it was