[SOGo] Ideal Nginx config for sogo?

[f***@garbage-juice.com]

Hello again,

the sogo wiki has an nginx config last updated in 2014. is this config
still ideal in sogo v3 with current nginx (1.9.12) and centos 7 in mind?

- Fabe S.

[mayak]

Post by f***@garbage-juice.com
Hello again,
the sogo wiki has an nginx config last updated in 2014. is this config still ideal in sogo v3 with current nginx (1.9.12) and centos 7 in mind?
- Fabe S.

HI Fabe,

Sure. This assumes you want https://sogo.domain.com that passes traffic to your sogo running at localhost:20000

Enjoy

M.

<pre>
server {
listen 443;
server_name sogo.domain.com;
rewrite ^/$ https://sogo.domain.com/SOGo;
access_log /var/log/nginx/sogo-access.log;
error_log /var/log/nginx/sogo-error.log;


client_max_body_size 20m;
client_body_buffer_size 512k;
client_header_timeout 360;
client_body_timeout 360;
send_timeout 360;


location ^~ /SOGo {
proxy_pass http://127.0.0.1:20000/SOGo;
proxy_redirect http://127.0.0.1:20000/SOGo /;

proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host sogo.domain.com;
proxy_set_header x-webobjects-server-protocol HTTP/1.0;
proxy_set_header x-webobjects-remote-host sogo.domain.com;
proxy_set_header x-webobjects-server-name sogo.domain.com;
proxy_set_header x-webobjects-server-url https://sogo.domain.com;

proxy_connect_timeout 360;
proxy_send_timeout 360;
proxy_read_timeout 360;
proxy_buffer_size 4k;
proxy_buffers 16 64k;
proxy_busy_buffers_size 64k;
proxy_temp_file_write_size 64k;
}

location /.woa/WebServerResources/ {
alias /usr/lib64/GNUstep/SOGo/WebServerResources/;
}

location /SOGo.woa/WebServerResources/ {
alias /usr/lib64/GNUstep/SOGo/WebServerResources/;
}

location /SOGo/WebServerResources/ {
alias /usr/lib64/GNUstep/SOGo/WebServerResources/;
}

location ^/SOGo/so/ControlPanel/Products/([^/]*)/Resources/(.*)$ {
alias /usr/lib64/GNUstep/SOGo/$1.SOGo/Resources/$2;
}
}
</pre>

[mayak]

Post by f***@garbage-juice.com
Hello again,
the sogo wiki has an nginx config last updated in 2014. is this config still ideal in sogo v3 with current nginx (1.9.12) and centos 7 in mind?
- Fabe S.

And for mobile users:

<pre>
server {
listen 443;
server_name m.domain.com;

client_max_body_size 16m;
client_body_buffer_size 32k;
client_header_timeout 360;
client_body_timeout 360;
send_timeout 360;

location ^~ /Microsoft-Server-ActiveSync {
access_log /var/log/nginx/activesync.log;
error_log /var/log/nginx/activesync-error.log;
resolver your.dns-server.ip.address;

proxy_connect_timeout 360;
proxy_send_timeout 360;
proxy_read_timeout 360;
proxy_buffers 64 256k;

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

proxy_pass http://127.0.0.1:20000/SOGo/Microsoft-Server-ActiveSync;
proxy_redirect http://127.0.0.1:20000/SOGo/Microsoft-Server-ActiveSync /;
}

}
</pre>