Delete server rules button does not delete rule.
-
wrote on Apr 30, 2024, 5:27 PM last edited by yehuda1491 Apr 30, 2024, 5:54 PM
@girish It's all missing, and saving new won't take.
-
wrote on Apr 30, 2024, 6:36 PM last edited by
My settings are also not saved and /horizon gives an error.
-
wrote on Apr 30, 2024, 7:32 PM last edited by
I also have a problem with the version, rules cannot be added and I had a larger user storage limit and it is 5 Gb after the update and cannot be increased in the settings
-
wrote on Apr 30, 2024, 8:04 PM last edited by
@girish It also breaks Curated Onboarding, there is just wide open registrations
-
wrote on Apr 30, 2024, 8:09 PM last edited by
@girish Dan says "I will look into this after work, seems like something maybe corrupted in the config_cache table, however it will be easy to fix"
-
wrote on May 1, 2024, 10:41 AM last edited by
@girish his fix didn't work, and of course this is much more extensive than just the rules.
-
wrote on May 1, 2024, 10:43 AM last edited by
I went back, to an older version
-
wrote on May 2, 2024, 4:12 PM last edited by
I had to roll back to the previous Pixelfed version, I couldn't leave everything unconfigured and registrations wide open.
-
@yehuda1491 do you happen to know what his plans are? Will he be making a new release with fixes? Maybe we can revert the Cloudron package release.
-
wrote on May 3, 2024, 3:29 PM last edited by
@girish I told Dan this is not a one-off issue, that more people than just me are experiencing the issue. I'm going to setup a Cloudron server with one Pixelfed instance to see if I can replicate the issue with 0.12.0 that he can diagnose. If I can't replicate it with a fresh 0.12.0, it is likely related to the upgrade from 0.11.13 I'm imagining. Is there a way to start a fresh install with a specific version?
-
@girish I told Dan this is not a one-off issue, that more people than just me are experiencing the issue. I'm going to setup a Cloudron server with one Pixelfed instance to see if I can replicate the issue with 0.12.0 that he can diagnose. If I can't replicate it with a fresh 0.12.0, it is likely related to the upgrade from 0.11.13 I'm imagining. Is there a way to start a fresh install with a specific version?
@yehuda1491 yes, https://git.cloudron.io/cloudron/pixelfed-app/-/blob/master/CHANGELOG?ref_type=heads gives a mapping between package version and pixelfed version. Click on pixelfed in appstore and change the URL bar to have the right package version and then click install.
-
@yehuda1491 yes, https://git.cloudron.io/cloudron/pixelfed-app/-/blob/master/CHANGELOG?ref_type=heads gives a mapping between package version and pixelfed version. Click on pixelfed in appstore and change the URL bar to have the right package version and then click install.
wrote on May 3, 2024, 4:31 PM last edited by@girish It does replicate on a fresh 0.12.0 install, fyi. I'll let you know what happens.
-
wrote on May 4, 2024, 8:51 PM last edited by yehuda1491 May 4, 2024, 8:53 PM
@girish still haven't heard from Dan.
FYI I have no idea if this is relevant, but on both v0.11.13 & v0.12.0 in env.production ENABLE_CONFIG_CACHE=true, and in v0.11.13 diagnostics ENABLE_CONFIG_CACHE is true, but in v0.12.0 diagnostics ENABLE_CONFIG_CACHE is false. -
I was following the upstream defaults here https://github.com/pixelfed/pixelfed/blob/v0.12.0/.env.docker#L70 also the app itself does not build anymore with config cache enabled. The mentioned docs link in pixelfed is also sadly outdated.
-
wrote on May 6, 2024, 8:09 PM last edited by
-
wrote on May 6, 2024, 8:19 PM last edited by yehuda1491 May 7, 2024, 6:24 AM
@girish @nebulon A person I know says they fixed the issue, but I don't know how this relates to cloudron/docker:
"Btw, I was able to get pixelfed working I had to do the setting permissions step again
cd pixelfed
sudo chown -R http:http . # change user/group to http user and http group
sudo find . -type d -exec chmod 755 {} ; # set all directories to rwx by user/group
sudo find . -type f -exec chmod 644 {} ; # set all files to rw by user/group(replace http in http:http with the user you run pixelfed as with the systemd service) then after this, i did
php artisan cache:clear
and then these
php artisan config:cache
php artisan route: cache
php artisan migrate --forcefrom the upgrade steps now it all works"
-
wrote on May 7, 2024, 6:23 AM last edited by
-
wrote on May 7, 2024, 6:55 AM last edited by
Hello, Pixelfed developer here. I am working on a fix for this, and I apologize about the inconvenience this has caused!
-
@yehuda1491 thanks for keeping us in the loop. Presumably some folders need to be moved to read/writeable locations for the cache if it is enabled during runtime then.