I tested with Apache2 with success.
I test it with the same result of white page.
For more information, I'm using:
Debian 12.6 with kernel 6.1.99
nginx 1.26.1-2 with repositories from nginx.org
mariadb 10.11.6 from debian repositories
sogo 5.11.0 nightly builds
Now I switch to apache to see if there some difference.
Am 23.08.24 um 22:25 schrieb Odhiambo Washington (odhia...@gmail.com):
I don't see much difference between mine and yours and mine loads the
Web UI perfectly. Can you pls try it and tell us if it also fails?
```
# SOGo
server {
listen 443;
root /usr/lib/GNUstep/SOGo/WebServerResources/;
server_name webmail.example.com <http://webmail.example.com/>;
server_tokens off;
client_max_body_size 100M;
index index.php index.html index.htm;
autoindex off;
# SSL parameters
ssl_certificate /etc/letsencrypt/webmail/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/webmail/privkey.pem;
ssl_dhparam /etc/ssl/certs/dhparam.pem;
add_header Strict-Transport-Security "max-age=31536000" always;
# log files
access_log /var/log/nginx/webmail_access.log;
error_log /var/log/nginx/webmail_error.log warn;
location = / {
rewrite ^ https://$server_name/SOGo/;
allow all;
}
location = /principals/ {
rewrite ^ https://$server_name/SOGo/dav;
allow all;
}
location ^~/SOGo {
proxy_pass http://127.0.0.1:20000;
proxy_redirect http://127.0.0.1:20000 default;
# forward user's IP address
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For
$proxy_add_x_forwarded_for;
proxy_set_header Host $host;
proxy_set_header x-webobjects-server-protocol HTTP/1.0;
proxy_set_header x-webobjects-remote-host 127.0.0.1;
proxy_set_header x-webobjects-server-name $server_name;
proxy_set_header x-webobjects-server-url $scheme://$host;
proxy_connect_timeout 90;
proxy_send_timeout 90;
proxy_read_timeout 90;
proxy_buffer_size 512k;
proxy_buffers 8 128k;
proxy_busy_buffers_size 512k;
proxy_temp_file_write_size 512k;
client_max_body_size 100m;
client_body_buffer_size 128k;
break;
}
location /SOGo.woa/WebServerResources/ {
alias /usr/lib/GNUstep/SOGo/WebServerResources/;
allow all;
}
location /SOGo/WebServerResources/ {
alias /usr/lib/GNUstep/SOGo/WebServerResources/;
allow all;
}
location ^/SOGo/so/ControlPanel/Products/([^/]*)/Resources/(.*)$ {
alias /usr/lib/GNUstep/SOGo/$1.SOGo/Resources/$2;
}
location
^/SOGo/so/ControlPanel/Products/[^/]*UI/Resources/.*\.(jpg|png|gif|css|js)$
{
alias /usr/lib/GNUstep/SOGo/$1.SOGo/Resources/$2;
}
}
```
On Fri, Aug 23, 2024 at 8:32 PM "Christian@Mail" <users@sogo.nu> wrote:
OK,
my nginx config looks like:
server {
listen 443 ssl;
listen [::]:443 ssl;
http2 on;
server_name webmail.example.com <http://webmail.example.com>;
ssl_certificate /etc/letsencrypt/webmail/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/webmail/privkey.pem;
ssl_dhparam /etc/ssl/certs/dhparam.pem;
add_header Strict-Transport-Security max-age=15768000;
error_log /var/log/nginx/webmail-error.log;
access_log /var/log/nginx/webmail-access.log;
# SOGo
root /usr/lib/GNUstep/SOGo/WebServerResources/;
# requirement to create new calendars in Thunderbird #
proxy_http_version 1.1;
# Message size limit #
client_max_body_size 50m;
client_body_buffer_size 128k;
location = / {
if ( $args ) {
return 404;
}
rewrite ^ https://$server_name/SOGo;
allow all;
}
# For iOS 7
location = /principals/
{
rewrite ^ `https://$server_name/SOGo/dav`;
allow all;
}
location ^~/SOGo {
proxy_pass http://127.0.0.1:20000;
#proxy_redirect http://127.0.0.1:20000 default;
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_set_header X-Forwarded-Proto $scheme;
# forward user's IP address
proxy_set_header x-webobjects-server-protocol HTTP/1.0;
proxy_set_header x-webobjects-remote-host 127.0.0.1;
proxy_set_header x-webobjects-server-name $server_name;
proxy_set_header x-webobjects-server-url $scheme://$host;
proxy_set_header x-webobjects-server-port $server_port;
proxy_connect_timeout 90;
proxy_send_timeout 90;
proxy_read_timeout 90;
proxy_buffer_size 8k;
proxy_buffers 4 64k;
proxy_busy_buffers_size 64k;
proxy_temp_file_write_size 64k;
break;
}
location /SOGo.woa/WebServerResources/ {
alias /usr/lib/GNUstep/SOGo/WebServerResources/;
allow all;
expires max;
}
location /SOGo/WebServerResources/ {
alias /usr/lib/GNUstep/SOGo/WebServerResources/;
allow all;
expires max;
}
location
(^/SOGo/so/ControlPanel/Products/([^/]*)/Resources/(.*)$) {
alias /usr/lib/GNUstep/SOGo/$1.SOGo/Resources/$2;
expires max;
}
location
(^/SOGo/so/ControlPanel/Products/[^/]*UI/Resources/.*\.(jpg|png|gif|css|js)$)
{
alias /usr/lib/GNUstep/SOGo/$1.SOGo/Resources/$2;
expires max;
}
if ($ssl_protocol = "") {
return 301 https://$server_name$request_uri;
}
}
These config is running on another system since a couple of years.
That's the reason for my trouble.
Thanks for all
Christian
Am 23.08.24 um 16:07 schrieb Odhiambo Washington (odhia...@gmail.com):
On Fri, Aug 23, 2024 at 4:01 PM "Christian@Mail" <users@sogo.nu>
wrote:
Hi everybody,
after new install from scratch the WebUI doesn't start
completely. I got
white page only instead of login page.
System: Debian 12, nginx, mariadb, sogo
The sogo.log looks like:
sogod [187495]: <0x0x55a6c4cf67f0[SOGoProductLoader]> SOGo
products
loaded from '/usr/lib/GNUstep/SOGo':
sogod [187495]: <0x0x55a6c4cf67f0[SOGoProductLoader]>
CommonUI.SOGo,
MainUI.SOGo, ActiveSync.SOGo, Appointments.SOGo, Mailer.SOGo,
SchedulerUI.SOGo, MailerUI.SOGo, MailPartViewers.SOGo,
ContactsUI.SOGo,
PreferencesUI.SOGo, Contacts.SOGo, AdministrationUI.SOGo
sogod [187495]: All products loaded - current memory usage at
98 MB
I can see only one error:
sogod[187501:187501] EXCEPTION: <NSException: 0x55a6c4eecfb0>
NAME:NSInvalidArgumentException REASON:Tried to add nil value
for key
'directory' to dictionary INFO:{}
By any chance any ideas how can I fix that?
Thanks
Christian
IMHO, by all means, the web UI should start, but login should
then be the issue.
The web UI is handled by Nginx then the rest is where the
interaction with IMAP server comes in.
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
In an Internet failure case, the #1 suspect is a constant: DNS.
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
[How to ask smart questions:
http://www.catb.org/~esr/faqs/smart-questions.html]
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
In an Internet failure case, the #1 suspect is a constant: DNS.
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
[How to ask smart questions:
http://www.catb.org/~esr/faqs/smart-questions.html]
