View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0005515SOGoGUIpublic2022-05-06 07:232022-05-17 13:11
Reporterdaduke Assigned To 
PriorityhighSeverityminorReproducibilityalways
Status closedResolutionno change required 
PlatformLinuxOSDebianOS Versionbullseye
Product Version5.6.0 
Summary0005515: dreaded 'Internal server error' returns with 5.6.0
Description

In bug 0005449 we struggled with an 'Internal server error', preventing us from logging into the GUI. Turned out it was caused by the apache proxy settings. We have since changed to nginx and Sogo has been working fine. However, with 5.6.0 we now get the same error on nginx. Login might still succeed, but after some minutes the error appears and the only way out is to force a logout via an edited address book URL, after which you can relogin and again use Sogo for a few minutes.
We did adapt the nginx proxy settings (scraped together from https://github.com/cha87de/sogo-docker/blob/master/config/nginx.conf.tmpl, https://mailcow.github.io/mailcow-dockerized-docs/manual-guides/Nginx/u_e-nginx_custom/ and https://github.com/mailcow/mailcow-dockerized/issues/4537):

    location ^~/SOGo {
....
       client_max_body_size 0;
       proxy_buffer_size 128k;
       proxy_buffers 64 512k;
       proxy_busy_buffers_size 512k;
       #proxy_temp_file_write_size 64k;
       break;
    }

any ideas?

thanks,
-Christian

Steps To Reproduce
  • upgrade from 5.5.1 to 5.6.0
  • use it for a few minutes
TagsNo tags attached.

Activities

daduke

daduke

2022-05-06 07:25

reporter   ~0016034

sorry about the config format...
francis

francis

2022-05-09 18:53

administrator   ~0016040

You could try the proposed configuration from the wiki.
jan

jan

2022-05-10 10:44

reporter   ~0016047

I have the same problem with Apache too. After logging in to the GUI, the message "Request failed" appears after a few minutes (2-3 minutes) and I get Error 500 in the log file. Logging out still works and logging in again also works. This behaviour only occurred after the upgrade to 5.6.0.
daduke

daduke

2022-05-10 10:51

reporter   ~0016048

I implemented the 'new' values from the wiki on the test server and so far I see no issues on 5.6.0. Tomorrow I'll update the production server and see how it goes.
francis

francis

2022-05-10 11:59

administrator   ~0016049

@jan Any error in your sogod log file?
jan

jan

2022-05-10 12:10

reporter   ~0016050

Last edited: 2022-05-16 14:26

@francis I just see this in the Log File:

May 10 14:05:07 sogod [22739]: 217.224.70.78 "POST /SOGo/so/jan@***.net/Mail/0/folderINBOX/changes HTTP/1.1" 200 508/74 0.512 - - 0 - 14
May 10 14:08:20 sogod [22739]: 217.224.70.78 "POST /SOGo/so/jan@***.net/Mail/0/folderINBOX/changes HTTP/1.1" 500 36/152 0.226 - - 0 - 15
May 10 14:08:20 sogod [22742]: 217.224.70.78 "POST /SOGo/so/jan@***.net/Mail/0/folderINBOX/changes HTTP/1.1" 500 36/74 0.214 - - 0 - 15
May 10 14:08:24 sogod [22742]: 217.224.70.78 "POST /SOGo/so/jan@***.net/Mail/0/folderINBOX/changes HTTP/1.1" 500 36/152 0.219 - - 0 - 15
May 10 14:08:24 sogod [22739]: 217.224.70.78 "POST /SOGo/so/jan@***.net/Mail/0/folderINBOX/changes HTTP/1.1" 500 36/74 0.229 - - 0 - 15
jan

jan

2022-05-13 07:36

reporter   ~0016055

@francis do you need any aditional logfiles or can I do something else?
SlavekB

SlavekB

2022-05-16 17:01

reporter   ~0016060

I can confirm the same behavior (version 5.6.0 on Debian Stretch) after a few minutes of use regardless of activity or inactivity, it seems as if the session becomes invalid. Without any other symptoms, it starts to report code 500. It is necessary to either log out (if possible) or manually remove cookies. With version 5.5.x it didn't happen.
Christian Mack

Christian Mack

2022-05-17 09:06

developer   ~0016062

@SLavekB
Did you run the database script /usr/share/doc/sogo/sql-update-5.5.1_to_5.6.0.sh after upgrade?
jan

jan

2022-05-17 09:26

reporter   ~0016063

@Christian, I missed the database script. THX
SlavekB

SlavekB

2022-05-17 10:33

reporter   ~0016064

Thanks @Christian! I can confirm that I also overlooked a new script, and after its application the problem is no longer manifested.

Issue History

Date Modified Username Field Change
2022-05-06 07:23 daduke New Issue
2022-05-06 07:25 daduke Note Added: 0016034
2022-05-09 13:11 Christian Mack Description Updated
2022-05-09 18:53 francis Note Added: 0016040
2022-05-10 10:44 jan Note Added: 0016047
2022-05-10 10:51 daduke Note Added: 0016048
2022-05-10 11:59 francis Note Added: 0016049
2022-05-10 12:10 jan Note Added: 0016050
2022-05-13 07:36 jan Note Added: 0016055
2022-05-16 14:26 Christian Mack Note Edited: 0016050
2022-05-16 17:01 SlavekB Note Added: 0016060
2022-05-17 09:06 Christian Mack Note Added: 0016062
2022-05-17 09:26 jan Note Added: 0016063
2022-05-17 10:33 SlavekB Note Added: 0016064
2022-05-17 13:11 francis Status new => closed
2022-05-17 13:11 francis Resolution open => no change required