Quantcast
Viewing all articles
Browse latest Browse all 6761

Zammad 6.3.1 Docekr and nginx proxy

Hello

I did upgrade a zammad 5.4 docker-compose setup to 6.3.1 (with step 6.0 in between) and it seems to run on localhost:8080 (but I get a login error).

Now I try to setup a nginx proxy like written down in .example/proxy/docker-comnpose.yml.

But as I got not much knowledge on docker, I failed.
The nginx docker came up on the port 443/80, with valid certs, but shows error “502” and doicker logs shows a non active upstream. I am a bit helpless.

The nginx default.conf tells me:
upstream ticket.dinofamilie.at {
# Container: zammad-docker-compose_zammad-nginx_1
# networks:
# proxy_2_apps (reachable)
# zammad-docker-compose_default (unreachable)
# IP address: 172.25.0.3
# exposed ports: 8080/tcp
# default port: 8080
# using port: 8080
# /!\ WARNING: Virtual port published on host. Clients
# might be able to bypass nginx-proxy and
# access the container’s server directly.
server 172.25.0.3:8080;
}
in docker-compose I got:
frontend:
image: jwilder/nginx-proxy:alpine
restart: always
ports:
- “80:80”
- “443:443”
volumes:
- ./certs:/etc/nginx/certs
- /var/run/docker.sock:/tmp/docker.sock:ro
networks:
- proxy_2_zammad

zammad-nginx:
<<: *zammad-service
command: [“zammad-nginx”]
expose:
- “${NGINX_PORT:-8080}”
ports:
- “${NGINX_EXPOSE_PORT:-8080}:${NGINX_PORT:-8080}”
depends_on:
- zammad-railsserver
environment:
- VIRTUAL_HOST=ticket.dinofamilie.at
- NGINX_SERVER_SCHEME=https
networks:
- default
- proxy_2_zammad

networks:
proxy_2_zammad:
external:
name: proxy_2_apps

proxy_2_apps:

But no valid upstream. I can ping the local 172.25.0.3 Ip (which seems to be th ezammad-backend-nginx, on telnet 172.25.0.3 8080 I get “Connectiuon refused”.

Whats wrong, which option did I forgot?

thank you,
Lars


Viewing all articles
Browse latest Browse all 6761

Trending Articles