BUG_REPORT.yml
BUG_REPORT.yml
Name | About | Labels | Assignees |
---|---|---|---|
Bug report | Create a report to help us improve |
THIS IS NOT A SUPPORT CHANNEL!
IF YOU HAVE SUPPORT QUESTIONS ABOUT RUNNING OR CONFIGURING YOUR OWN HOME SERVER, please ask in #synapse:matrix.org (using a matrix.org account if necessary).
If you want to report a security issue, please see https://matrix.org/security-disclosure-policy/
This is a bug report form. By following the instructions below and completing the sections with your information, you will help the us to get all the necessary data to fix your issue.
You can also preview your report before submitting it.
Describe the problem that you are experiencing
Describe the series of steps that leads you to the problem.
Describe how what happens differs from what you expected.
IMPORTANT: please answer the following questions, to help us narrow down the problem.
Which homeserver was this issue identified on? (matrix.org, another homeserver, etc)
What version of Synapse is this homeserver running?
You can find the Synapse version by visiting https://yourserver.example.com/_matrix/federation/v1/version
or with this command:
$ curl http://localhost:8008/_synapse/admin/v1/server_version
(You may need to replace localhost:8008
if Synapse is not configured to listen on that port.)
Are you using SQLite or PostgreSQL? What's the version of your database?
If PostgreSQL, please also answer the following:
- are you using a single PostgreSQL server
or separate servers formain
andstate
? - have you previously ported from SQLite using the Synapse "portdb" script?
- have you previously restored from a backup?
Are you running a single Synapse process, or are you running
2 or more workers?
Tell us about the environment in which your homeserver is operating...
e.g. distro, hardware, if it's running in a vm/container, etc.
Do you have any unusual config options turned on? If so, please provide details.
- Experimental or undocumented features
- Presence
- Message retention
- Synapse modules
Please copy and paste any relevant log output, ideally at INFO or DEBUG log level.
This will be automatically formatted into code, so there is no need for backticks (```).
Please be careful to remove any personal or private data.
Bug reports are usually impossible to diagnose without logging.