Welcome to the staging ground for new communities! Each proposal has a description in the "Descriptions" category and a body of questions and answers in "Incubator Q&A". You can ask questions (and get answers, we hope!) right away, and start new proposals.
Are you here to participate in a specific proposal? Click on the proposal tag (with the dark outline) to see only posts about that proposal and not all of the others that are in progress. Tags are at the bottom of each post.
Image upload broken in Incubator Q&A
Meta issue: https://meta.codidact.com/posts/288441
I uploaded an image into this question: How accurate are the browser usage statistics at caniuse.com?
However it isn't showing up. When I uploaded it created the URL https://proposals.codidact.com/uploads/teqvdp0qxce3zm8ic42k9aod6ujb when when I try to view the image at that URL it shows the message:
<Error> <Code>AccessDenied</Code> <Message>Access Denied</Message> <RequestId>ARFXMCHKE3MHQY3P</RequestId> <HostId>XcKABOPwLuI4PDXIMhDQw/91vxBBjoFfZ/OmvT//AoY2UwY1sDml7pOc6uVRBZZb2SfURquBwR0=</HostId> </Error>
2 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
I recently uploaded an image to a question. I didn't encounter this problem, although I would expect that I should have.
I'm able to view the image with Right click -> Open image in new tab and it goes to https://s3.amazonaws.com/storage.codidact.com/mhnq6m6s8yv3nq450wqgf92xad7t which also works. Notably, the s3 URL confirms what Monica posted.
The error message in the question looks like it is some sort of XML based error response - I think either Apache or Nginx issues those (it's also customizable by the server admin, of course). I imagine it's CD's web server giving you the error, because you are trying to access the old URL which is no longer made accessible to the public.
0 comment threads
Sorry for the poorly-timed disruption! I've been told that this is due to a migration of S3 storage causing a caching problem that should clear up soon. (Sorry, I'm the messenger not the technical expert on this one.)
0 comment threads
1 comment thread