Unhandled error response SOGo

James

My system has been running without issues. I updated yesterday and now face the issue that I can’t log into SOGo Webmail anymore.

If I enter a wrong password I get the appropriate Wrong user/password massage. When I enter a right combination I get
a red ‘Unhandled error response’ message.

In the logs I can see a successful login event ’SOGoRootPage successful login from ‘xxx.xxx.xxx.xxx’ for user ‘xxx@yyy.zz’ - expire = -1 grace = -1′

Working in tech myself I hate ’I did nothing and after the update it doesn’t work anymore’ messages but that’s what has happened.

I can still login into the SOGo mailbox via the SOGo button in the admin interface, just native login via SOGo login screen stoppd working and I can’t find any log entries other than the successful login one. IMAP also works without issue

Greetings

pkernstock

Where did you check the logs? (UI, docker?)

Just to be sure: When you reproduce the issue, can you see any (helpful) logs when doing docker logs on your SOGo container?

James

[WARN] <0×0×7fe4fb023f60[WOxElemBuilder]> could not locate builders: WOxExtElemBuilder,WOxExtElemBuilder
SOGoRootPage successful login from ‘xxx.xxx.xxx.xxx’ for user ‘xxx@xxx’ - expire = -1 grace = -1
xxx.xxx.xxx.xxx “POST /SOGo/connect HTTP/1.0” 200 51/104 0.086 - - 1M - 14

These 3 are the only logs related to the failed login attempt in the docker log. The WOxExtElemBuilder seems to be the issue

accolon

Just guessing, but do you have an nginx reverse proxy in front of your mailcow webserver?

In this case, make sure to also increase the proxy buffer size as someone described here:
mailcow/mailcow-dockerized4537

James

accolon

Adding

proxy_buffer_size 128k;
proxy_buffers 64 512k;
proxy_busy_buffers_size 512k;

to my nginx reverse proxy config and changing the ActiveSynch Proxy buffer to 512k fixed the issue. Thanks!