It’s back ![]()
![]()
It’s back ![]()
![]()
FFS, no it’s not ![]()
Yes. You say it worked for some minutes?
No problems for me ![]()
The Wiki photos as well? ![]()
Eh…well, no. I mixed up the main forum page with the topics. Honest slip-up, happens to the best of us ![]()
Yes for the topics it works for me as well. It is a very strange kind of bug…
Maybe we need the @BusyBee to investigate? ![]()

Yes, it’s like this for me too.

Some pics in the Wiki are not loading either.

The logo is displayed everywhere for me, but no images in the wiki.
Only for some of them
Most of them. Try the participants photos of realm108. Just to see if the same are not loading for us.
You are on mobile. It is different there.
Yes, both are not loading. Only the latest added guests are loading. You just added a new one
I’m not mobile. I’m sitting here at my PC…
Yes exactly the same for me.
And you can see the logo when you are in that topic?
Well I found the problem @kaya @BusyBee
It is the bucket again.
All photos not loading in the Wiki use the same bucket:
vh-forum-xvpwuxajhontmrvfn4sjs
<Error>
<Code>NoSuchBucket</Code>
<Message>Der angegebene Bereich existiert nicht</Message>
<BucketName>vh-forum-xvpwuxajhontmrvfn4sjs</BucketName>
<RequestId>01B8626668B4CEB8:B</RequestId>
<HostId>fwDU6K1cx9yO/3RGsWQeUpXgDa/idH2y//bc5vdly01KFA90pLTE6OhTdYlOk7JerxJMzvkkvBsG</HostId>
<CMReferenceId>MTc1OTk1MDQ1MTA0MyAxMzAuMTE3LjI1Mi4xMDQgQ29uSUQ6ODg3NTQ4NTMxOS9FbmdpbmVDb25JRDo4NTkwNTQ5NS9Db3JlOjQ=</CMReferenceId>
</Error>
It seems the forum is not able to connect to that bucket. Can be a problem at AWS or at the forum side. Admin should find out by testing if the bucket can be reached from the servers where the forum is running on.
I was able to check the bucket name of a working photo and it is also the same bucket:
<BucketName>vh-forum-xvpwuxajhontmrvfn4sjs</BucketName>
So the reason is most likely some connection or configuration issue of the forum as the bucket clearly exists. It seems all images in the forum (I only checked a few of them) are stored in the same S3 Bucket.