[SOLVED] Storage Auth

1. What version did you upgrade from?
2. What versions did you upgrade to?
3. What versions did you run the migrate command on?

@Steven hey master 🙂 i didnt skip a version.. i upgraded to 1.3.0 then 1.3.1 and now 1.3.2 - but i can not say if this is since 1.3.0 or 1.3.2

but i am pretty sure before 1.3.0 it was working fine

i think i run the migration in 1.3.0 and 1.3.2

but not in 1.3.1

The migrate command on 1.3.2 might have screwed things up...you're going to need to restore from backup

😱

my users will kill me

If you care about your instance, you should always have a backup and test upgrades

yeah i have a backup .. but it is a week old or something.. all the userdata in between would be gone

@Steven is there only storage involved, or will i also have problems with my documents?

if only storage i would prefer to create a new bucket and use that in the future instead of ruin all my users data

I'm not sure

You can try

didnt work 😦

seems to be a problem with the users, and not with the storage 🤔

ahhhh forgot to set security on new bucket.. works now, thanks

Phew!

@Steven i saw a storage related fix in 1.3.4 is it related to this?

maybe...the problem i saw was access became public...your problem was like the opposite...which im not sure how/why

I will try it an give you feedback after i upgraded 👍

there was an api problem where updating the bucket permissions didn't really work, though

Not sure why but my old buckets are now also working again 😅😅

@S3ppo sorry, just saw the notification now 😁 but it looks like we have solved all issues now 👀

[SOLVED] Storage Auth