Roni Laukkarinen on Nostr: Just spent 6 hours trying find out and solve why my Matrix instance is showing: ...

Just spent 6 hours trying find out and solve why my Matrix instance is showing: {"errcode":"M_NOT_FOUND","error":"Not found"} when trying to access images. I did not notice this problem before, because Matrix/Element caches images locally using blobs, but realized this after uploading images to IRC via heisenbridge.

I first thought I had messed up my S3 Object Storage. Then thought I messed up my filesystem. Then I thought I made a mistake in yaml configs. But it was none of that.

It's a while since I installed my Matrix server and completely forgot on how I set up my S3 Object Storage. It seems it is literally not documented. Like at all. Just like the half of Matrix and Synapse.

I ended up debugging literally anything and everything without any solution. After turning all stones I even asked ChatGPT and it started to run in loops in despair. Finally ended up reading synapse changelog here one bit by bit: https://element-hq.github.io/synapse/latest/upgrade.html#authenticated-media-is-now-enforced-by-default

It seems, I have upgraded in some point. And wow, in between of upgrades the whole thing has broken. I mean it runs without erros, but it's broken. No deprecated warnings in the log, no warnings in release logs. Left a comment here: https://github.com/element-hq/synapse/pull/17889#issuecomment-2564520513

My solution was to add in homeserver.yaml:
enable_authenticated_media: false

What I hate about Matrix is:

- Nothing is documented
- Nothing is explained
- Everything is complicated to set up

Each upgrade and extension is like building and tinkering for hours and hours and hoping for the best.

I don't know why I keep using Matrix. Guess I like being hurt all the time.

#Matrix #Element #MatrixSynapse #SysOps #Servers #API