This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Synapse not listening on Federation port #4775
Comments
|
@richvdh you closed this ticket way too fast.... With SYNAPSE_NO_TLS=1
With SYNAPSE_NO_TLS=0
So no change |
I dug deeper inside the image and I found the problem, the default homeserver.yaml file isn't configured to listen on the federation port, only on the normal client port.
|
@richvdh ah, I've taken a look at the actual code in synapse/docker/conf/homeserver.yamland saw the line:
Removing the line "-e SYNAPSE_NO_TLS=1" enables it indeed:
|
@richvdh I can confirm that I experienced the same issue in #4663 as I mentioned above.
If I simply remove the whole entry "-e SYNAPSE_NO_TLS=0" then the entries to define port 8448 is added. |
This comment was marked as abuse.
This comment was marked as abuse.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
I was running version v0.99.1 of the Docker Synapse container and trying out the Federation.
It all seems to work until at some point I noticed that the port wasn't reachable anymore.
I tried restarting the container... nothing.
Tried running v0.99.2 but still, connections to port 8448 are refused.
The logs don't seem to indicate anything wrong:
This is how I launch the image:
The text was updated successfully, but these errors were encountered: