Closed thomsbe closed 1 year ago
Yours is a special case because you're putting other reverse-proxies in front of Traefik.
Given that you're fronting Traefik (matrix-traefik
) with another webserver, you may wish to migrate over some of the additional Traefik settings you're using for matrix-docker-ansible-deploy
, as described in Fronting the integrated reverse-proxy webserver with another reverse-proxy of the matrix-docker-ansible-deploy
documentation.
You probably need this added to vars.yml
on the mash-playbook side:
devture_traefik_config_entrypoint_web_secure_enabled: false
This would automatically cascade into:
switching devture_traefik_entrypoint_primary
to default to the devture_traefik_config_entrypoint_web_name
entrypoint (=web
), instead of using the non-existent web-secure
entrypoint
switching devture_traefik_config_certificatesResolvers_acme_enabled
to false
, so cert resolvers would not be added to any services
Tanks a lot! This was the missing piece. Now it's working.
I have the matrix-playbook with traeffik, fronted by a Caddy2. I'm trying to let the mash-playbook use the traeffik from the matrix-playbook. I got a lot of log-lines from matrix-treaffik right after the start and both subdomains running into a 404 not found.
mash-playbook config:
Everything looks ok, but I guess, I have missed some config somewhere or there is a issue.