Closed Seele-Vollerei32 closed 5 months ago
See what else could be occupying port 8448
and preventing matrix-nginx-proxy.service
from starting.
netstat -anp | grep :8448
may help.
Perhaps you had a manually installed Synapse in the past?
I installed Dendrite manually in the past(from AUR) And there is the output of netstart
tcp 0 0 0.0.0.0:8448 0.0.0.0:* LISTEN 992/docker-proxy
tcp6 0 0 :::8448 :::* LISTEN 997/docker-proxy
I have stop all the service of matrix by ansible-playbook -i inventory/hosts setup.yml --tags=stop
xI am encountering what I believe to be the same issue.
@Seele-Vollerei32 – Did you find a solution? I'm also curious: is your server pretty low-powered (low memory / CPU)?
Some more details of my issue:
playbook-managed-traefik
and playbook-managed-nginx
to debug (and because I would take anything that lets me use my server in the short term). The same error message happens when using matrix_playbook_reverse_proxy_type: playbook-managed-traefik
and when using playbook-managed-nginx
– logs say that Bind for 0.0.0.0:8448 failed: port is already allocated
docker-proxy
, matching previous commentdocker ps
shows that matrix-synapse
indeed has a binding to 8448/tcp
just stop-all
-> just setup-all
multiple times, thinking that maybe matrix-synapse
needs to be down before Traefik/nginx starts; no successVM.Standard.E2.1.Micro
: 1GB of memory + 1GB swapfile). (Could Traefik be racing matrix-synapse? like, maybe other servers launch Traefik more quickly, allowing it to bind to 8448, and somehow matrix-synapse binds to the same port after Traefik launches... somehow? 🤷)setup-all
s, since my machine was running out of memory mid-setup: server became unresponsive and I had to force reboot. This is no longer happening after I added a swapfile. Not sure if this is relevant.systemctl list-units
shows that matrix-container-socket-proxy.service
is not found
. Checking journalctl
for this service shows some logs including Can't open server state file '/var/lib/haproxy/server-state': No such file or directory
just setup-all
fails waiting for Traefik / nginx to start (see log below)playbook-managed-nginx
docker kill
/ stop
ing matrix-synapse, then waiting for nginx to automatically try starting again. This fails with the same error; it looks like matrix-synapse
automatically restarts itself and binds to 8448 again. (Is this correct? Doing docker inspect matrix-synapse
, I see RestartPolicy
is no
, which is unexpected.)matrix_synapse_federation_port_enabled
, matrix_nginx_proxy_proxy_matrix_federation_api_enabled
, matrix_synapse_reverse_proxy_companion_federation_api_enabled
all to false to try to disable the 8448 port on matrix-synapse (following these docs); ran setup-all
– same issueHappy to make a new issue, but this does sound like the same issue.
I could not figure out what the issue was, but migrating to a new instance by following https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/maintenance-migrating.md got me back up and running :(
Had the same issue, for me traefik service would not start due to port being allocated already.
@davidisaaclee's comment pretty much summed up all the symptoms. I was running on a 1gb instance(t3a.micro ec2) and had failed setup-all
's as well which resulted is such broken state. That was a new install, so I didn't need to preserve any configs and after docker system prune -a
, removing /matrix/
and adding a 2gb swap file the install went without a hitch.
I had the very same issue. - But I had some legacy configs in following folder on the host:
/matrix/nginx-proxy/conf.d/
- first I deleted there everything.
After this I noticed some network in docker network ls
seemed odd. After running ansible-playbook -i inventory/hosts setup.yml --tags=stop
- I ran on the hostsystem docker network prune
Now everything works.
Had a similar issue to this today, everything seemed to be working but the built in traefik container kept crashing because of the error
Error response from daemon: driver failed programming external connectivity on endpoint matrix-traefik (---): Bind for 0.0.0.0:8448 failed: port is already allocated
Turns out docker-proxy was using that port for some reason, restarting docker as a whole fixed the issue. Just to be safe though I did a docker system prune --all --volume
to delete all the containers and networks and start over.
Playbook Configuration:
My
vars.yml
file looks like this:Matrix Server:
Problem description:
Before I reboot my server, the webui is unable to open. I reboot the server because I thought the load of the server is too heavy for the server to run. But after reboot, it still can't open.
Additional context `journalctl -fu matrix-nginx-proxy.service
in this cycle.