| 30 Jul 2021 |
 Passant (@Milan:tchncs.de) | * Hey, i am sorry for asking here, but i didn't get help in the other rooms i have asked, while my homeserver is down, which leaves me growingly impatient :(
Upgrading leaves me with Expected database schema version 61 but got 60. The main process states ['main', 'state']: Existing schema is 60 (+2 deltas) \n Applying schema deltas for v60. I have tried a fresh virtualenv multiple times now. Downgrading results in all workers and main being quite active but port 8008 is never opened. Please help ._. | 12:23:52 |
 callahad | Possibly! But I'd love to see us get her work on removing the database from Sygnal merged first... | 14:27:29 |
| callahad | In reply to @reivilibre:librepush.net
callahad: reckon this would be sensible? * Possibly! But I'd love to see us get her work on removing the database from Sygnal merged first... | 14:27:38 |
| Passant (@Milan:tchncs.de) | * Hey, i am sorry for asking here, but i didn't get help in the other rooms i have asked, while my homeserver is down, which leaves me growingly impatient :(
Upgrading leaves me with Expected database schema version 61 but got 60. The main process states ['main', 'state']: Existing schema is 60 (+2 deltas) \n Applying schema deltas for v60. I have tried a fresh virtualenv multiple times now. Downgrading results in all workers and main being quite active but port 8008 is never opened. Please help ._.
Edit: a solution was found in the Admins room. Thanks again Olivier 'reivilibre'
| 14:58:36 |
|  bobby joined the room. | 15:34:12 |
 Timo ⚡️ | 
Download Screenshot_20210730_175609.png | 15:56:43 |
| Timo ⚡️ | How well does synapse enforce this? | 15:56:49 |
 clokep | Timo ⚡️: Room versions > 6 enforce it. | 15:58:13 |
| Timo ⚡️ | Conduit currently rejects PDUs if they contain a number that's out of bounds (even if it's in a non-spec field) | 15:58:14 |
| clokep | Yes it doesn't matter if it is in a spec field or not. | 15:58:30 |
| clokep | The entire payload has to be valid. | 15:58:33 |
| Timo ⚡️ | Good, thanks | 15:58:40 |
| clokep | https://spec.matrix.org/unstable/rooms/v6/#canonical-json | 15:59:31 |
| clokep | (See https://github.com/matrix-org/matrix-doc/pull/2540 for rationale of why it is only version 6+) | 16:00:01 |
|  Yoric|Away changed their display name from Yoric to Yoric|Away. | 18:30:25 |
| 31 Jul 2021 |
|  Chagai ( backup account ) changed their display name from Chagai (backup account) to Chagai (backup account ). | 08:19:22 |
| Chagai ( backup account ) changed their display name from Chagai (backup account ) to Chagai ( backup account ). | 08:41:23 |
 Moe (Moritz Dietz) | Hey all! I've been looking at open Docs issues and the Discussion section on GitHub. I would love to update the docs around reverse proxies and HTTP Headers.
As in: in #synapse:matrix.org I've seen questions around "which headers should I add for the reverse proxy in front of my synapse" and the docs don't really tell you if you should and where you should use which. Or at least give some suggestion as to what are sensible defaults (leaning on what is out there from https://infosec.mozilla.org/guidelines/web_security.html).
Not sure if this is better discussed in a GH issue or here. | 12:15:47 |
| clokep | Moe (Moritz Dietz) I think https://matrix-org.github.io/synapse/latest/reverse_proxy.html has all the info necessary but if there’s improvements to make that clearer we would gladly accept them! If you think something needs discussion — here or an issue is fine. If you already have ideas of what to change a PR would be reasonable for discussion too! | 15:38:35 |
| 1 Aug 2021 |
| Moe (Moritz Dietz) | Thanks! As of now the only two headers which reverse proxies should handle are X-Forwarded-For and X-Forwarded-Proto. And from the wording it is somewhat implied that Synapse will take care of the "rest".
This is something I'd maybe like to add, to spell it out that Synapse does set Headers on its own via request.setHeader and that homeserver admins don't need to "worry" about it.
| 10:27:45 |
| Moe (Moritz Dietz) | Or if they should, which ones that would be and perhaps why. I don't want to bloat the document more than it is, but maybe make it clear what is expected to do. | 10:29:23 |
| *  ~creme create a repo with useful matrix-synapse configs (incl. workers setup) & tools. FYI: https://git.envs.net/envs/matrix-conf | 12:44:28 |
| ~creme | ^^ feel free to use it for the synpase documentation | 12:44:48 |
|  tejas.bhagwat joined the room. | 13:19:21 |
| tejas.bhagwat | Hi, I was trying to change firebase account from matrix/element account to my newly created account. But i am not able to find any configurations for Firebase on server as well as in android app. Can anyone tell me is it possible or not to change Firebase account? | 13:22:00 |
 s7evink | And i tought my request was weired. :P | 13:27:02 |
| ~creme | tejas.bhagwat: you try to setup your own sygnal? | 13:29:25 |
| ~creme | maybe the channel #sygnal:matrix.org is better for your question. this channel is the synpase developer channel. | 13:30:02 |
| tejas.bhagwat | Thank you. | 13:45:06 |
| ~creme | you're welcome | 13:46:29 |
