Hi this behavior is normal.

This request check of the password recovery feature is enabled for a user. 403 means it's not enabled (forbidden).

Sebastien

But in the frontend I get this error message:

Unhandled error response

So if the 403 is the correct response then the bug is in the frontend.

Please post sogo logs. It should not be related to this 403.

Those are the three log entries from this time:

Dec 12 16:11:46 sogod [3158]: SOGoRootPage successful login from '1.1.1.1' for user 'XXXXX@XXXXXX.com' - expire = -1 grace = -1
Dec 12 16:11:46 sogod [3158]: 1.1.1.1 "POST /SOGo/connect HTTP/1.0" 200 48/90 0.016 - - 0 - 15
Dec 12 16:11:47 sogod [3158]: 1.1.1.1 "POST /SOGo/so/passwordRecoveryEnabled HTTP/1.0" 403 0/50 0.001 - - 0 - 15

I don't understand your issue.
You said "now the users can not login anymore over the web interface" however in your logs the /connect endpoint returns a 200 so the user shall be connected.
The 403 error in your browser dev tools is normal.

What is the problem exactly ? What is the browser ? Did you reproduced on demo.sogo.nu ?

We have it with all types of browsers and operating systems. You see in the attached screenshot what all users get after entering username and password. The problem does not exist on your demo website.

Screenshot from 2022-12-12 17-52-23.png (13,081 bytes)   

Screenshot from 2022-12-12 17-52-23.png (13,081 bytes)   

Ok I see it must be related to a slow network and timing issue. I'll take a look on that

I digged now deeper and found the problem. In-between SOGo and the browser is an nginx. nginx got from SOGo all correct with a 200 status code but send then to the client a 502 status code because of this error:

[error] 1706#1706: *21865 upstream sent too big header while reading response header from upstream, client: 1.1.1.1, server: _, request: "POST /SOGo/connect HTTP/1.1", upstream: "http://127.0.0.1:20000/SOGo/connect"

After implementing the parameters mentioned here it works again:
https://www.cyberciti.biz/faq/nginx-upstream-sent-too-big-header-while-reading-response-header-from-upstream/

I didn't find anything in the sogo documentation about nginx. Maybe it would be good to add a small section about this specific problem. Else you can close the issue.

Hi thanks for updating.
If anybody got time to update documentation in https://github.com/Alinto/sogo/blob/master/Documentation/SOGoInstallationGuide.asciidoc, add nginx configuration part and do a pull request ;)

Sebastien

If you're running iRedMail-1.5.1 or earlier versions, you can follow this tutorial to fix the issue by updating Nginx config file:
https://docs.iredmail.org/upgrade.iredmail.1.5.1-1.5.2.html#nginx-increase-proxy-buffer-size-so-that-user-can-login-to-sogo-webmail

You can close this issue. Once I have an answer for https://bugs.sogo.nu/view.php?id=5661 I will update the documentation and do a pull request as you ask for.

Thanks @modir !