Attempting to access artifacts results in "An internal server error occurred."

From a recent doc build I was checking:

$ curl
{"message":"An internal server error occurred."}

The job completes fine, but the artifacts are not viewable. Going back to builds from a day or two ago that I was able to access results in the same error.

1 Like

Experiencing the same issue

Getting similar 500 Server Error when trying to access artifacts.

This was resolved earlier today. More info:

1 Like

Thanks. I can confirm that the artifacts are now accessible. Must have squeezed this report in just before the fix…

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.