I guess that was the problem and it is confirmed as fixed by the user who complained.
I’m not sure what this upload of images does, but I guess it is some extra feature that complex servers might need. I guess our 40 users don’t need a discourse with this complex feature. We are more interested in emoji likes.
However, when I followed the s3 instructions, I had to double back and make a new bucket for “backups” while the original one was for uploads (because I did in order as it appeared for settings). I think I will probably add some more info to the s3 instructions as a reply to help make this easier for others to follow. Also the permission policy listed in that help thread did not exist, and I ended up finding a “*” solution from another website. I’ll try to help clarify this on that thread. It worked, but work and tweaks to the instructions.
These actions did not work… I used * instead.
"Action": [
"s3:ListAllMyBuckets",
"s3:HeadBucket"
],
The thread I used to configure and follow the instructions is here
It too also has enable s3 uploads marked as checked… Seems like making things too complex for the average user.
On the otherhand, I’m hoping my backups are working fine with out it.