Federation setup for Matrix #2404
Unanswered
gouthamravee
asked this question in
Q&A
Replies: 1 comment 5 replies
-
Hi, i'd recommend to stick with port 443. Ther is absolutely no need to forward other ports than 80&443 for NPM.
After that you should be able to test your instance with https://federationtester.matrix.org/#my.domain |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to get federation working for my matrix server. I'm using the ansible install method.
Matrix and nginx-proxy are on different vms with their own unique address on the LAN.
I have the ansible nginx-proxy on but using different ports, and NPM is managing proxying from
matrix.my.domain
andmy.domain
.NPM is also managing certs for both domains.
https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-own-webserver.md#method-2-fronting-the-integrated-nginx-reverse-proxy-webserver-with-another-reverse-proxy
I can access matrix from matrix.my.domain.
I have port
8448
forwarded to NPM and I have the dockerfile setup to pass port8448
to8048
on the matrix server.The problem is I need
my.domain:8448
to show the SSL cert for my.domainIn NPM I have hosts with SSL created for
I also have a stream host as
8448 -> matrix.my.lan:8084
But I'm getting a connection refused when doing the matrix federation test.
Beta Was this translation helpful? Give feedback.
All reactions