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

**URL:** <https://discuss.circleci.com/t/attempting-to-access-artifacts-results-in-an-internal-server-error-occurred/33934>\
**Category:** Bug Reports\
**Tags:** artifacts\
**Created:** [December 31, 2019, 2:31pm UTC](https://discuss.circleci.com/t/attempting-to-access-artifacts-results-in-an-internal-server-error-occurred/33934 "2019-12-31T14:31:24Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![effigies](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/effigies/32/12246_2.png) [@effigies](https://discuss.circleci.com/u/effigies)\
**Post date:** [December 31, 2019, 2:31pm UTC](https://discuss.circleci.com/t/attempting-to-access-artifacts-results-in-an-internal-server-error-occurred/33934/1 "2019-12-31T14:31:24Z")

</div>

From a [recent doc build](https://circleci.com/gh/oesteban/nipype/2089#artifacts/containers/0) I was checking:

```auto
$ curl https://2089-17021985-gh.circle-artifacts.com/0/tmp/src/nipype/doc/_build/html/index.html
{"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.

---

<div class="post-metadata">

**Author:** ![sarahbx](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/sarahbx/32/23905_2.png) [@sarahbx](https://discuss.circleci.com/u/sarahbx)\
**Post date:** [December 31, 2019, 3:18pm UTC](https://discuss.circleci.com/t/attempting-to-access-artifacts-results-in-an-internal-server-error-occurred/33934/2 "2019-12-31T15:18:26Z")

</div>

Experiencing the same issue  
[https://23060-78030626-gh.circle-artifacts.com/REDACTED](https://23060-78030626-gh.circle-artifacts.com/REDACTED)

---

<div class="post-metadata">

**Author:** ![shellygr](https://avatars.discourse-cdn.com/v4/letter/s/7ab992/32.png) [@shellygr](https://discuss.circleci.com/u/shellygr)\
**Post date:** [December 31, 2019, 3:28pm UTC](https://discuss.circleci.com/t/attempting-to-access-artifacts-results-in-an-internal-server-error-occurred/33934/3 "2019-12-31T15:28:57Z")

</div>

Getting similar `500 Server Error` when trying to access artifacts.

---

<div class="post-metadata">

**Author:** ![ndintenfass](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/ndintenfass/32/156_2.png) [@ndintenfass](https://discuss.circleci.com/u/ndintenfass)\
**Post date:** [December 31, 2019, 7:49pm UTC](https://discuss.circleci.com/t/attempting-to-access-artifacts-results-in-an-internal-server-error-occurred/33934/4 "2019-12-31T19:49:55Z")

</div>

This was resolved earlier today. More info: [https://status.circleci.com/incidents/6jyjwlb0bxqf](https://status.circleci.com/incidents/6jyjwlb0bxqf)

---

<div class="post-metadata">

**Author:** ![effigies](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/effigies/32/12246_2.png) [@effigies](https://discuss.circleci.com/u/effigies)\
**Post date:** [December 31, 2019, 8:39pm UTC](https://discuss.circleci.com/t/attempting-to-access-artifacts-results-in-an-internal-server-error-occurred/33934/5 "2019-12-31T20:39:51Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\
**Post date:** [January 10, 2020, 8:39pm UTC](https://discuss.circleci.com/t/attempting-to-access-artifacts-results-in-an-internal-server-error-occurred/33934/6 "2020-01-10T20:39:55Z")

</div>

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