lapineige

Great, that was fast, thanks a lot ! 🚀 We mainly depends on released version to upgrade, do you think you will make an hotfix for this, or should we...

I tried manually using this commit (or rather a later one https://github.com/pixelfed/pixelfed/pull/4276), it still fails. Example : https://photo.lapineige.fr/i/web/post/548958694320755247

> ERROR The [public/storage] link already exists.

How can I help to better diagnose this ?

It's only been 3 days, no worries :) Restart + cache:clear, no difference. Horizon is working, no failed job.

What do you mean by permissions ? Account permissions (I'm admin), or file permissions ? This wasn't a problem before upgrading to v0.11.5. I don't understand why any file permission...

> Go to /var/www/pixelfed/public/storage and go deeper... Everything is owned by pixelfed user. No change since the (working) state before the upgrade. > If I'm correct newly created folders should...

> You need to modify config/filesystems.php to fix it. How/why ? 🤔 What I don't understand is why it was working perfectly since that upgrade with folder and files owned...

So… for some reason the patch wasn't applied. I upgraded again to that version, the patch is here now, I have the filesystems.php changes, the new media:fix command is working...

Do you know where those files are stored so I can check manually before messing with all files rights and permissions ? 😅