View Issue Details

IDProjectCategoryView StatusLast Update
0005535SOGoWeb Mailpublic2022-07-15 15:52
Reportermaxycay Assigned To 
PriorityurgentSeverityminorReproducibilityhave not tried
Status newResolutionopen 
PlatformLinuxOSUbuntuOS Version18.04.4
Product Version5.7.0 
Summary0005535: Unhandled error response after updated to SOGo 5.7
Description

Hi guys!

A few days ago I upgraded sogo to version 5.7. Now I'm getting an error when logging in - Unhandled error response

I have updated iRedMail 1.6.0

In Chrome console just see:

status of 502 ()
/SOGo/connect:1          Failed to load resource: the server responded with a status of 502 ()
angular.js:13692          POST https://example.com/SOGo/connect 502

What do I need to do??

Tagsubuntu

Activities

francis

francis

2022-06-27 14:03

administrator   ~0016101

Any error in your SOGo log file?

maxycay

maxycay

2022-07-05 10:25

reporter   ~0016112

There is no errors in log. What I need to do ??

Christian Mack

Christian Mack

2022-07-14 09:11

developer   ~0016121

Did you upgrade from SOGo 5.6.0 or an older version?

maxycay

maxycay

2022-07-15 15:10

reporter   ~0016131

I have 5.7 with latest updates.
I seem to have found the problem.
If I open the mail server by IP like 10.10.0.10/SOGo I can successfully login to SOGo and get no error.
If I try to access the domain like: examle.com/SOGo I only get login page. After trying to login, I see an error: ERR_CONNECTION_CLOSED

I have a proxy server on Ubuntu (nginx) currently using the following host configuration:

server {
    listen 443 ssl;

    ssl_certificate /etc/letsencrypt/live/mail.example.com/fullchain.pem; 
    ssl_certificate_key /etc/letsencrypt/live/mail.example.com/privkey.pem;

    server_name mail.example.com;
     location / {

            proxy_pass https://10.77.50.85;

            proxy_set_header Host $host;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Real-IP $remote_addr;

            proxy_buffer_size          1024k;
            proxy_buffers              8 512k;
            proxy_busy_buffers_size    1024k;

        }

server {
    listen 80;
    server_name mail.example.com;
    return 301 https://$server_name$request_uri; 
    }

}

But I can not understand why this configuration does not suit him. Any ideas?

francis

francis

2022-07-15 15:18

administrator   ~0016132

Compare you configuration with the community wiki: http://wiki.sogo.nu/nginxSettings

maxycay

maxycay

2022-07-15 15:52

reporter   ~0016133

I did it.
Unfortunately there is no result.
I just tried using this configuration again - ERR_CONNECTION_CLOSED

Issue History

Date Modified Username Field Change
2022-06-16 08:27 maxycay New Issue
2022-06-16 08:36 maxycay Tag Attached: ubuntu
2022-06-27 14:03 francis Description Updated
2022-06-27 14:03 francis Note Added: 0016101
2022-07-05 10:25 maxycay Note Added: 0016112
2022-07-14 09:11 Christian Mack Note Added: 0016121
2022-07-15 15:10 maxycay Note Added: 0016131
2022-07-15 15:18 francis Note Added: 0016132
2022-07-15 15:52 maxycay Note Added: 0016133