You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
name joined the room
name made the room invite only.
name made future room history visible to all room members.
name has allowed guests to join the room.
The room is set to private, element is set to not allow guests, encryption is enabled.
It is telling me guests are allowed, so it is either a bug, I misunderstand, or I am missing a config setting. Registration is on but only allowed with token.
Steps to reproduce
Create a new private and encrypted room using Synapse + element versions listed above.
Homeserver
My own homeserver
Synapse Version
1.75.0+focal1
Installation Method
Debian packages from packages.matrix.org
Database
fresh postgresql (single on same machine as synapse)
Workers
Single process
Platform
KVM VPS
Ubuntu 20
Element 1.11.19 (on separate KVM VPS)
Configuration
No response
Relevant log output
NA
Anything else that would be useful to know?
No response
The text was updated successfully, but these errors were encountered:
Description
When I create a new private room it displays:
The room is set to private, element is set to not allow guests, encryption is enabled.
It is telling me guests are allowed, so it is either a bug, I misunderstand, or I am missing a config setting. Registration is on but only allowed with token.
Steps to reproduce
Create a new private and encrypted room using Synapse + element versions listed above.
Homeserver
My own homeserver
Synapse Version
1.75.0+focal1
Installation Method
Debian packages from packages.matrix.org
Database
fresh postgresql (single on same machine as synapse)
Workers
Single process
Platform
KVM VPS
Ubuntu 20
Element 1.11.19 (on separate KVM VPS)
Configuration
No response
Relevant log output
Anything else that would be useful to know?
No response
The text was updated successfully, but these errors were encountered: