@gh0stface so this is what I've setup;

## S3 Storage PF_ENABLE_CLOUD=true FILESYSTEM_DRIVER=local FILESYSTEM_CLOUD=s3 PF_LOCAL_AVATAR_TO_CLOUD=true MEDIA_DELETE_LOCAL_AFTER_CLOUD=true AWS_ACCESS_KEY_ID=xxx AWS_SECRET_ACCESS_KEY=xxx AWS_DEFAULT_REGION=xxx AWS_BUCKET=mediapixelfedsg AWS_URL=https://media.pixelfed.sg AWS_ENDPOINT=https://xxx.backblazeb2.com #AWS_USE_PATH_STYLE_ENDPOINT=false

and it works.

@nebulon
Oh, I just wanted to understand where the problem was coming from to potentially fix it since Pixelfed considers it an error.

But if it's not a real problem, then I'll keep it as it is.

Thanks

@jdaviescoates added link, thanks.

@jdaviescoates Fixed up your gitlab permissions as well.

@girish That's the solution for me, somehow the cookies were making trouble. After deleting the cookies (I did delete my browser cache before, but that's not enough) now everything is working fine! Maybe because I had a test with pixelfed on the main domain and the browser had stored some old cookies. Thanks for your reply!

@girish I took a look again and now it changed. seems like a caching thing. Thanks for looking into it.

Ok thanks for the information, I misunderstood. Sorry for the unnecessary question.

@girish No, not the image itself, just the link its wrapped in.

Yeah, AFAIK, this is by design. You can only see posts from when you created the instance. You cannot see posts from the past.

@RazielKanos If you go into Services, redis, then increase the ram:f201a80a-04bd-459a-88d9-4a47bdf03048-image.png

To anyone who arrived here via a Google search like I did and aren't sure where to find the controls referenced by scooke above... you may not yet be an Pixelfed admin user.

Follow these instructions to upgrade your user to an admin and then when you visit /i/admin/dashboard you'll find the controls. Visiting that URL without following those instructions will result in a redirect.

@scooke Thanks! Added "Wait and see" to the "Reboot" and "Reinstall" options! 🙂

Indeed, in the "new UI", the admin page link is not there. Or maybe, I just cannot find it. If you switch to the old UI, it's under your profile icon.

Go back to previous design:

a5abd516-ad6c-4ef2-b33b-f5acd12039a7-image.png

Admin page link is below profile icon:

27c6ff0b-e9bd-4492-9501-393d93ce00b1-image.png

Admin page:

bd5430b7-2526-473d-8cef-533e820bd76d-image.png

@urtzai said in Redis error when uploading pictures:

Has somebody any clue of what could be causing? I already have the latest redis server and I'm pretty sure the ZPOPMIN command is in there.

Just want to double check here. This is the Cloudron Forum for answering questions about the Pixelfed package. Did you deploy Pixelfed via Cloudron ? Since you said I already have "latest redis" server, this seems like you are not using Cloudron.

See https://pixelfed.social/site/help on how to contact the upstream project.

@byghuutran said in Can't access to admin panel:

Ok, thank you. And can i enable my Cloudron user to create some app from appstore ( only wordpress or ghost) as a user blog like as blogger?

Not 100% sure what you mean, but maybe you want to make that user an admin so they can install apps? If so, please see https://docs.cloudron.io/user-management/#roles .

Also, please open a new thread for new questions. That will help others search and look for answers.

This is quite complex to integrate. Requires patching source files - https://docs.pixelfed.org/running-pixelfed/ldap-authentication.html . Not sure why it's made so complicated.

@jdaviescoates No problem so far. Even notifications work. 🙂

Hi, after the last Pixelfed update, everything is fine now. The topic is solved

@girish
ok, thanks I will open a ticket with them for a MySQL issue with pixeldroid.

This happens on my instance as well 😞

@timconsidine just be careful - my relay is "hidden" but once you find it, it relays what it gets. So, moderation will be a bit of a challenge till you get the hang of it.

@subtlecourage trust it, test it, or do some other update that refreshes the UI so it reflects what you expect.

There's no evidence it doesn't work as set in the config.

I this upstream project does not implement this as yet. https://github.com/pixelfed/pixelfed/issues/2924 and https://github.com/pixelfed/pixelfed/issues/2802 are the issues.

Thanks for letting us know, I have now published a new package.

@doodlemania2 i have pushed an update.

@onlybro thanks for the heads up on this. I think I understand the reason for that recommendation. But to understand this in the Cloudron context, once the box process starts up, we create a mysql connection pool. This is never destroyed and as long as the box process is up and running, the name resolving is only done during startup once. So I think we are good as is on this one.

I would actually be more curious about the memory settings you mentioned, that is probably more worthwhile understanding.

@jdaviescoates Yeah, i keep permanently running on marketing "from" email addresses.