You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been successfully running matrix for a while now. However, I've had some issues with coturn (out of scope of this issue) and so I tried to uninstall according to the documentation and reinstall everything, just as a sanity check.
Running /matrix/bin/remove-all completed successfully without any errors.
I then tried to re-install everything by re-running just roles and then just setup-all -K, with the same config. However, if I try to go to element.my-domain.tld, or #, or hit any endpoint, traefik returns a 404.
This is on commit f84a53d8 (latest as of time of writing) of matrix-docker-ansible-deploy
First off, thanks for the awesome project!
Describe the bug
Issue: All routes 404.
I've been successfully running matrix for a while now. However, I've had some issues with coturn (out of scope of this issue) and so I tried to uninstall according to the documentation and reinstall everything, just as a sanity check.
Running
/matrix/bin/remove-all
completed successfully without any errors.I then tried to re-install everything by re-running
just roles
and thenjust setup-all -K
, with the same config. However, if I try to go toelement.my-domain.tld
, or #, or hit any endpoint,traefik
returns a 404.This is on commit
f84a53d8
(latest as of time of writing) ofmatrix-docker-ansible-deploy
To Reproduce
My
vars.yml
file looks like this:Simply going to
element.my-domain.tld
can reproduce the issueExpected behavior
Traefik to route requests
Matrix Server:
Client:
Additional context
Add any other context about the problem here.
Here is my
traefik.yml
from the server:Here is my
providers.yml
, which seems very suspicious:Here is the relevant output from
journalctl -u matrix-traefik.service
:I found the
filtering disabled container
interesting, but I'm not sure what it means.The text was updated successfully, but these errors were encountered: