!QvOYYvjPoWZBfgSBNk:matrix.org

Synapse Installation Guide Feedback

148 Members
Feedback and discussion about the recommended synapse installation guide: https://www.natrius.eu/dokuwiki/doku.php?id=digital:server:matrixsynapse49 Servers

Load older messages


SenderMessageTime
6 May 2019
@coiner:matrix.orgAceLooking now. Do I need to put my keys in the homeserver.yaml as well as nginx?20:10:58
@mathijs:matrix.vgorcum.comMathijsThis guide, and most others, needs updating20:11:04
@coiner:matrix.orgAcehttps://github.com/matrix-org/synapse/blob/master/docs/reverse_proxy.rst20:11:19
@coiner:matrix.orgAceI'm using that nginx config and there is no certs mentioned20:11:31
@mathijs:matrix.vgorcum.comMathijs
In reply to @coiner:matrix.org
Looking now. Do I need to put my keys in the homeserver.yaml as well as nginx?
If you choose (as i would recommend) to use nginx for the reverse proxy of federation traffic you don't need to give synapse access the the certs
20:12:18
@coiner:matrix.orgAceAny example nginx config? The ones provided are not working20:15:55
@coiner:matrix.orgAceI added the certificates to the one specified on the github page20:16:05
@coiner:matrix.orgAceAnd in the homeserver.yaml just in case20:16:11
@coiner:matrix.orgAceAnd now the tester just says "error": "msg=Failed to GET JSON to20:16:29
@coiner:matrix.orgAceAnd also 502 now on 844820:16:35
@mathijs:matrix.vgorcum.comMathijsright, so what we'll do20:22:16
@mathijs:matrix.vgorcum.comMathijsis have nginx listen on port 443 for both client-server and server-server traffic20:22:38
@mathijs:matrix.vgorcum.comMathijsand reverse proxy that to port 800820:22:44
@mathijs:matrix.vgorcum.comMathijsthen we'll use a .well-known file to tell other servers to look for your server on port 44320:23:07
@mathijs:matrix.vgorcum.comMathijssound good?20:23:16
@coiner:matrix.orgAceSure however surely the SRV record should work? It shows on the federation tester20:23:33
@mathijs:matrix.vgorcum.comMathijsif you prefer, we could also tell nginx to listen on port 844820:23:34
@coiner:matrix.orgAceI have that20:23:39
@coiner:matrix.orgAceI have the one from: https://github.com/matrix-org/synapse/blob/master/docs/reverse_proxy.rst20:23:47
@coiner:matrix.orgAceRedacted or Malformed Event20:23:55
@mathijs:matrix.vgorcum.comMathijs
In reply to @coiner:matrix.org
Sure however surely the SRV record should work? It shows on the federation tester
SRV record should work as well, if you prefer that one, we can use the record to point to port 443
20:24:05
@coiner:matrix.orgAceand specifying the cert and key20:24:05
@coiner:matrix.orgAceIt's pointing to 8448 at the moment so I could set it to 44320:24:33
@coiner:matrix.orgAceI am correct in assuming if it just points to mydomain.net then that is the same as @20:24:47
@coiner:matrix.orgAceAs namecheap won't let me do @ for SRV record and I'm not using subdomain20:25:08
@coiner:matrix.orgAceIn homeserver.yaml should I change 8448 to 44320:26:15
@mathijs:matrix.vgorcum.comMathijsno, in homeserver.yaml we'll only have synapse listen on port 800820:26:33
@coiner:matrix.orgAceOkay, only 800820:26:40
@mathijs:matrix.vgorcum.comMathijsand disable tls, so synapse doesn't need an SSL cert20:26:51
@coiner:matrix.orgAceGotcha20:27:12

There are no newer messages yet.


Back to Room ListRoom Version: 1