matrix-static-files doesn't use matrix_playbook_reverse_proxyable_services_additional_network about matrix-docker-ansible-deploy HOT 2 CLOSED

Your vars.yml is outdated. matrix_static_files_container_network is set like this:

If matrix_playbook_reverse_proxy_type is anything other than none (that is, if it's playbook-managed-traefik or other-traefik-container), then matrix-static-files would be connected to the container network specified in matrix_playbook_reverse_proxy_container_network

As per our new Traefik managed by you documentaiton, you're supposed to tell the playbook on which network your Traefik instance lives by redefining matrix_playbook_reverse_proxy_container_network in your vars.yml file.

Our changelog section People managing their own Traefik instance need to do minor changes from the large Goodbye, matrix-nginx-proxy 🪦 also tells you about it:

Because Traefik has an extra job now, you need to adapt your configuration to add the additional matrix-internal-matrix-client-api entrypoint and potentially configure the matrix_playbook_reverse_proxy_container_network variable.

It seems like you've skipped over this part. If you haven't added the additional matrix-internal-matrix-client-api entrypoint, you would also experience other problems.

from matrix-docker-ansible-deploy.

As a workaround I manually set the network-name in the systemd-unit on the host. This obviously will be reverted anytime the playbook is run.

from matrix-docker-ansible-deploy.