The documentation pipeline should really get fixed at some point.

The keepalive patch is available sine 0.9.7.

Remove spammer

Ubuntu updated to guam-0.9.8-2 and my login problem is also solved.

Update for guam on Centos 7 this morning : no more error with roundcube login.
(Guam : 0.9.8 / 2.1.el7.kolab_16)

@sicherha T6073 contain logs from my install as well as a CentOS install

In T6061#89530, @sicherha wrote:

Do Guam's log files, which can commonly be found under /var/log/guam/, provide any helpful clues as to what is going wrong here?

I opened T6073 but the packages linked by @armageddon are a work around for now. My issue is a duplicate of this one.

This is likely the same issue as T6061

In T6061#89371, @armageddon wrote:

Have a look on this repository.

I managed to restore an older backup and retrieve kolab_guam-0.9.7 and eimap-0.4.2 (Debian 9 amd64), and following @transcending.it advice I have my system up and running again. Just in case someone can benefit and save some time, I am uploading them here...

Do Guam's log files, which can commonly be found under /var/log/guam/, provide any helpful clues as to what is going wrong here?

I'm closing this in favour of T6073/T6061, both of which appear to deal with the same issue.

Actually I am also seeing the same failure as Spenneburg:

Those guam logs are different from mine, I see the following:

2020-11-10 05:29:26.321 [info] <0.350.0> Application lager started on node 'kolab_guam@127.0.0.1'
2020-11-10 05:29:26.322 [info] <0.350.0> Application eimap started on node 'kolab_guam@127.0.0.1'
2020-11-10 05:29:26.322 [info] <0.350.0> Application lager_syslog started on node 'kolab_guam@127.0.0.1'
2020-11-10 05:29:26.322 [info] <0.429.0>@kolab_guam:start:33 Starting Kolab Guam IMAP session proxy ...
2020-11-10 05:29:26.322 [info] <0.429.0>@kolab_guam:start:34     Starting the main supervisor ...
2020-11-10 05:29:26.322 [info] <0.431.0>@kolab_guam_listener:init:45 Starting listener "imap" on port 143 ([{keepalive,true},{reuseaddr,true},{active,false},inet6]) with 1 rules
2020-11-10 05:29:26.322 [info] <0.434.0>@kolab_guam_listener:init:45 Starting listener "imaps" on port 993 ([{keepalive,true},{reuseaddr,true},{active,false},inet6]) with 1 rules
2020-11-10 05:29:26.323 [info] <0.350.0> Application kolab_guam started on node 'kolab_guam@127.0.0.1'
2020-11-10 14:00:01.771 [info] <0.1615.0> TLS server: In state certify received CLIENT ALERT: Fatal - Bad Certificate

Have a look on this repository.

In T6061#88954, @transcending.it wrote:

I uploaded the previous guam 0.9.7-3 and erlang-eimap 0.4.2-2.1 here from DEBIAN 10 for those of you who don't have access anymore. But I strongly suggest to take any software only from trusted sources (i.e. your own machines - or maybe the kolab devs will upload old versions to the kolab repo so we can use apt).

I confirm the behaviour for apache2 as well.

Thanks armageddon.
It works fine.

Make a downgrade to guam 0.9.5 and erlang-eimap-0.4.0 on CentOS 7

@sven.wtal erts-10.2.4 was indeed on my system. Glad that you found a working backup.
@SebastienWeber you're wecome

transcending.it, you are my hero!

Same problem on Centos 7 (Login no longer possible after update).

I guess you do not have Ubuntu 18.04 and your guam version is compiled with other versions.
I'll see tomorrow if I find a version of one of my backups to copy it.

I'll have a look when I get back later. For now I just wanted to mention again that I'm using Debian so maybe my solution might not work at all un Ubuntu!

I made a link from erts-9.2 to erts-10.2.4 and tested

I am sorry, but I still don't get it work on my ubuntu server.