Gitlab Integration

Infos:

  • Used Zammad version: 3.2.x
  • Used Zammad installation source: (source, package, …): docker-compose
  • Operating system: Linux / Mac
  • Browser + version: Chrome 78

on Zammad 3.0 i have no Problems with gitlab

Expected behavior:

  • Redirect to my GitLab Installation

Actual behavior:

Steps to reproduce the behavior:

@thorsteneckel thx for your help

40

@monotek - can you please point me to the nginx configuration of our docker-compose image? I think this issue somehow affects the docker-compose setup as well…

Hey @cyberrranger - is there any other service in front of your NGINX that handles SSL for you? Like a loadbalancer, proxy, application firewall etc. ?

@thorsteneckel i use an nginx in front off https://github.com/zammad/zammad-docker-compose with this settings:

upstream ticket2-****-websocket {
server 172.17.0.1:8101;
}

upstream ticket2-****{
server 172.17.0.1:8100;
}

server {
listen 443 ssl;
server_name ticket2.****;

    ssl_certificate /etc/nginx/ssl/****.crt.pem;
    ssl_certificate_key /etc/nginx/ssl/****.key.pem;

    location /ws {
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "Upgrade";
            proxy_set_header CLIENT_IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

            proxy_set_header X-Forwarded-Proto https;

            proxy_read_timeout 86400;
            proxy_pass http://ticket2-****-websocket;
    }

    location / {
            proxy_set_header Host $http_host;
            proxy_set_header CLIENT_IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

            proxy_set_header X-Forwarded-Proto https;

            proxy_read_timeout 180;
            proxy_pass http://ticket2-****;
            gzip on;
            gzip_types text/plain text/xml text/css image/svg+xml application/javascript application/x-javascript application/json application/xml;
            gzip_proxied any;
    }

}

server {
listen 80;
server_name ticket2.****;

    location / {
            return 301 https://ticket2.****/;
    }

}

I guess that’s the thing. I assume that the HTTPS protocol information is somehow not passed to the zammad-nginx. Usually it should. It uses the default nginx config which passes the proto to the application. Please SSH into the zammad-nginx container and change the proxy_set_header X-Forwarded-Proto $scheme; lines to proxy_set_header X-Forwarded-Proto https;.

I will check in the next few days and then report me again, you certainly mean SSL and not SSH or?

I mean connect into the container to be able to configure the internal config of that NGINX.

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.