-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Federation Not Working #3069
Comments
I think I fixed the issue by adding More info here: https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-base-domain-serving.md |
Port 80 is also required for obtaining SSL certificates from Let's Encrypt |
also you have https://[matrix.domain]/.well-known/matrix/client isn't the federation server https://[domain]/.well-known/matrix/client |
Port 80 is/was also open. I think the problem was that I wasn't serving the base domain, which I resolved by doing the above. The issue seems to be resolved; thank you for the reply! |
Good to hear it's solved now! For completeness, I'll mention here that serving the base domain is only one of the ways to achieve server delegation. If you have an HTTPS-enabled server handling the base domain elsewhere already, you can continue handling it there and set up some well-known redirects on it. |
Playbook Configuration:
My
vars.yml
file looks like this:Standard vars.yml with my server info
Matrix Server:
Problem description:
Federation isn't working, and I'm not sure why. When I run the setup.yml script, I get the following error:
Obviously the error has something to do with port 443, but port 443 is open to both inbound and outbound TCP traffic in my firewall. Do I also need to open it to UDP traffic?
I've set everything up by following the installation instructions, and everything else seems to be working. The only non-standard thing I've added is the web GUI for admins. Any help would be appreciated! Thanks!
EDIT: Port 8448 is also open to inbound/outbound traffic per the installation guide.
The text was updated successfully, but these errors were encountered: