SOGo Webmail access work partially throw SWAG

BisonOpiniatre

I know SWAG isn’t officialy supported but I already have a server who contain Jellyfin, NextCloud and others tools using SWAG as Reverse Proxy. So I should continue to use it with my mail server if I don’t want use another server and I don’t want.

Currently I started all mailcow container except nginx and I defined a conf file for the reverse proxy. I’m able to reach the SOGo web page but no CSS of JS seem to be loaded.

So reverse proxy seem work patially but I don’t know what I forget on the conf file to be able to load all components.
All of the return a 404 Not found.

Here my conf file:

`server {
listen 443 ssl;
listen [::]:443 ssl;

server_name mail.iceberg.quebec;

include /config/nginx/ssl.conf;

client_max_body_size 0;

location / {
    proxy_pass http://mailcowdockerized-sogo-mailcow-1:20000/;
    include /config/nginx/proxy.conf;
    include /config/nginx/resolver.conf;

    # Forward headers for SOGo
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Host $host;
    proxy_set_header X-Forwarded-Server $host;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Forwarded-Port $server_port;
}

# Location for static assets (CSS/JS/Images)
#location /SOGo/ {
#    proxy_pass http://mailcowdockerized-sogo-mailcow-1:20000/SOGo/;
#    include /config/nginx/proxy.conf;
#    include /config/nginx/resolver.conf;

#   proxy_set_header Host $host;
#    proxy_set_header X-Forwarded-Host $host;
#    proxy_set_header X-Forwarded-Server $host;
#    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
#    proxy_set_header X-Forwarded-Proto $scheme;
#    proxy_set_header X-Forwarded-Port $server_port;
#}

#location /so/ {
#    proxy_pass http://mailcowdockerized-sogo-mailcow-1:20000/so/;
#    include /config/nginx/proxy.conf;
#    include /config/nginx/resolver.conf;

#   proxy_set_header Host $host;
#    proxy_set_header X-Forwarded-Host $host;
#    proxy_set_header X-Forwarded-Server $host;
#    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
#    proxy_set_header X-Forwarded-Proto $scheme;
#    proxy_set_header X-Forwarded-Port $server_port;
#}

accolon

BisonOpiniatre Currently I started all mailcow container except nginx and I defined a conf file for the reverse proxy.

mailcow won’t work without the included nginx. Either try to adapt the mailcow reverse proxy documentation for your needs or use SWAG’s reverse proxy config example.

BisonOpiniatre

accolon Yes I understood that. I don’t know why ChatGPT ask me to replace the nginx with my reverse proxy but that don’t make sense. I requested citation but I was not able to found any reference of that on actual documentation.
Now I started mailcow with nginx and I put swag on malcow network. from my reverse proxy (SWAG) I’m able to reache the login webpage (using curl) but from the web, I receive a 400 Bad request. pretty sure is a problème with my conf file. I try tu use which one proposed on ngnix section but I need to understand which option are alredy managed by swag and which one I should use.

Also I define a TRUSTED_PROXIES value but because SWAG have an interface is same network I think isn’t necessary.

disgustipated

It looks like youre maybe trying to use swag on the same box as mailcow? are they in the same docker compose or separate stacks? having them on the same box might not be the best. i use swag and have it on another server which has the config pointed over to the mailcow server’s ip like the below. replace «mailcowip» without the port in both locations with the mailcow ip and the server_name directive to match yours, and the logging sections to where you want. I use this running on a different box through cloudflare so that the web interface isnt exposed on the same ip as the mail server. I’m guessing you have some complications with trying to point the proxy_pass to the same local box and trying to point this directly at the sogo container. maybe try pointing it at the nginx container in mailcow, this might help route things properly. the mailcow nginx should see the Host and x-forwarded-for headers and pass to the sogo container. dont forget to run docker exec swag nginx -t and then docker exec swag nginx -s reload if the -t test command checks out ok to reload your config after you make changes.

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    server_name web.servername.com;
    access_log /config/log/nginx/webclient.access.log;
    error_log /config/log/nginx/webclient.error.log;
    access_log /config/log/nginx/access.log;
    error_log /config/log/nginx/error.log;
    include /config/nginx/ssl.conf;

    location / {
        proxy_pass https://<<mailcowip>>/;
        proxy_set_header Host $http_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;
        proxy_connect_timeout 75;
        proxy_send_timeout 3650;
        proxy_read_timeout 3650;
        proxy_buffers 64 512k;
        client_body_buffer_size 512k;
        client_max_body_size 0;
    }

    location /Microsoft-Server-ActiveSync {
        proxy_pass https://<<mailcowIP>>/Microsoft-Server-ActiveSync;
        proxy_set_header Host $http_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;
        proxy_connect_timeout 75;
        proxy_send_timeout 3650;
        proxy_read_timeout 3650;
        proxy_buffers 64 512k;
        client_body_buffer_size 512k;
        client_max_body_size 0;
    }
}

BisonOpiniatre

disgustipated
No mailcow and swag is a separate compose file in separate network but I tried to bypass the nginx server from mailcow with suggestion of chatGPT. Bad idea. Now I just started mailcow like I should with a specified port to replace 80 and 443. I also use the conf file provided by LinuxServer (didn’t know it exists) and I replaced mailcow by mail. Now everything work fine to access to SOGo. Now I will configure incoming port throw my router to receive mail.

Now That work. Thanks guys for support and for the product.