!HsxjoYRFsDtWBgDQPh:matrix.org

Synapse Admins

1765 Members
Help with setting up and running Synapse | Current: 0.99.1.1 - please read https://matrix.org/blog/2019/02/05/synapse-0-99-0/ | RC: none | For questions about developing on Matrix, please join #matrix-dev:matrix.org | File bugs at https://github.com/matrix-org/synapse/issues | Announcements in #homeowners:matrix.org648 Servers

Load older messages


Timestamp Message
21 Feb 2019
00:58:46@cdknight1:matrix.orgcdknightOh, I'll try that
00:58:51@cdknight1:matrix.orgcdknightSounds like a better hack
00:59:59@cdknight1:matrix.orgcdknightThat worked, thanks!
01:03:04@dandellion:dodsorf.asDandellionthat will have the "interesting side effect" of not letting people upload profile pictures as well
01:04:04@gwilliams:matrix.orgSamsoniteI reverse proxy 8008 from my apache server to my synapse server. what should my bind_addresses be in homeserver.yaml?
01:04:27@gwilliams:matrix.orgSamsoniteI keep reading it should be ['127.0.0.1'] but that isn't working, making me think something is wrong
01:04:46@gwilliams:matrix.orgSamsoniteit does work if i do [''::', '0.0.0.0']
01:08:40@gwilliams:matrix.orgSamsonitei dunno my server is working right now but i got a feeling i didn't set it up correctly and it won't federate come version 1.0
01:29:04@cdknight1:matrix.orgcdknightSo there is no way to disable joining outside rooms other than with a hacky firewall rule?
01:30:31@ostrichbot:matrix.orgostrichbotYou can use the federation_domain_whitelist directive in homeserver.yaml
01:30:25@earfolds:earfolds.comearfoldswhat's an "outside room"?
01:31:25@ostrichbot:matrix.orgostrichbotand then disable federation on ports 8448 and 8008 for good measure as well. But that will entirely isolate your instance from federating.
01:32:29@cdknight1:matrix.orgcdknightBy an outside room I mean a room that's not under our homeserver's domain
01:33:56@cdknight1:matrix.orgcdknightPreventing federation will not work, because we want users outside our homeserver to join our rooms but users inside our homeserver to not be able to join rooms outside the homeserver
01:34:40@earfolds:earfolds.comearfoldsthe only way I can think of to do that is prevent people from other servers from joining your rooms, or disabling federation entirely
01:34:25@lindalap:matrix.orgLinda

Rooms exist on all servers federating with.

01:35:17@earfolds:earfolds.comearfoldsbecause as soon as a user from another server joins, it becomes an outside room
01:34:29@lindalap:matrix.orgLinda

with members in them

01:37:14@earfolds:earfolds.comearfoldsyou could then uninstall and completely remove your server from the entire internet and those rooms would still exist, for instance
01:35:16@cdknight1:matrix.orgcdknightYes, but I mean restriction by domain name
01:35:32@cdknight1:matrix.orgcdknightso if the room ends in, for example, matrix.org, then don't let a user join
01:35:49@mooshoe:matrix.orglegally stupidJust curious if anyone knows — what are the reasources for creating a new synapse server and federating with matrix.org on bigger channels today? I set up a homeserver a year ago or so and tried to federate but it wasn't enough to handle bigger rooms, and I gave the server some pretty good specs. There seems to be more self hosted servers today though, has there been any progress here?
01:38:03@cdknight1:matrix.orgcdknighti see what you mean, I'll just have to remind our users that they should not be joining other domains with a bot or something
01:38:38@cdknight1:matrix.orgcdknightI could do it in a chat room (I saw there was a setting make users auto-join a room when they register)
01:39:39@mooshoe:matrix.orglegally stupid
In reply to @mooshoe:matrix.org
Just curious if anyone knows — what are the reasources for creating a new synapse server and federating with matrix.org on bigger channels today? I set up a homeserver a year ago or so and tried to federate but it wasn't enough to handle bigger rooms, and I gave the server some pretty good specs. There seems to be more self hosted servers today though, has there been any progress here?
i guess i can just spin up a vps and try this weekend nvm
02:19:42@ostrichbot:matrix.orgostrichbotCan the guide at https://github.com/matrix-org/synapse/blob/master/docs/reverse_proxy.rst be updated to reflect homeserver.yaml config changes that need to be made to the listeners?
02:20:27@ostrichbot:matrix.orgostrichbotIf you reverse proxy 8448, it conflicts with matrix-synapse listening on 8448. That's not addressed in the source documents.
02:22:04@ostrichbot:matrix.orgostrichbotAlso would like to know what the disposition of tls_certificate_path, key_path, and tls_fingerprint are.
02:22:21@ostrichbot:matrix.orgostrichbotFeels like TLS fingerprinting was a huge issue that we are sidestepping now.
02:26:31@ostrichbot:matrix.orgostrichbotSorry TLS discussion in release notes.

There are no newer messages yet.


Back to Room List