# Failed to upload artifacts from self-hosted runner

**URL:** <https://discuss.circleci.com/t/failed-to-upload-artifacts-from-self-hosted-runner/50260>\
**Category:** Build Environment\
**Tags:** artifacts\
**Created:** [January 19, 2024, 2:53pm UTC](https://discuss.circleci.com/t/failed-to-upload-artifacts-from-self-hosted-runner/50260 "2024-01-19T14:53:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gianmarco](https://avatars.discourse-cdn.com/v4/letter/g/13edae/32.png) [@Gianmarco](https://discuss.circleci.com/u/Gianmarco)\
**Post date:** [January 19, 2024, 2:53pm UTC](https://discuss.circleci.com/t/failed-to-upload-artifacts-from-self-hosted-runner/50260/1 "2024-01-19T14:53:20Z")

</div>

Hello, I am trying to troubleshoot an issue that I have uploading the log of a script that is running on my self-hosted runner. I tried by giving both the absolute path and the relative path of the log file but the upload fails after hanging for more than 15 minutes.

```auto
Uploading C:\script.log to script.log
Uploading C:\script.log (19 kB): Total size uploaded: 0 B
FAILED with error an unexpected storage error occurred (operation id: 6dc71376)

```

Can it be that the runner is blocked uploading the file by some policy on the company network?

---

<div class="post-metadata">

**Author:** ![rit1010](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/rit1010/32/34738_2.png) [@rit1010](https://discuss.circleci.com/u/rit1010)\
**Post date:** [January 21, 2024, 4:12pm UTC](https://discuss.circleci.com/t/failed-to-upload-artifacts-from-self-hosted-runner/50260/2 "2024-01-21T16:12:24Z")

</div>

I’ve just done a test using a self-hosted runner and this config.yml

```auto
version: 2.1

executors:
  exec_node:
    machine: true
    working_directory: /tmp/CircleCI_working_directories/project_test_container
    resource_class: mycompany/basic-linux

jobs:
  build:
    executor: exec_node

    steps:
      - checkout

      # create some output
      - run:
          name: output
          command: ls > output.txt

      # Store test artifacts (screenshots, etc.)
      - store_artifacts:
          path: output.txt
          destination: artifacts

workflows:
  build-and-test:
    jobs:
      - build

```

It worked as expected with the output.txt file being uploaded.

My runner is not limited by any firewall rules in terms of its access to the internet as it just sits behind a NAT gateway. From CircleCI’s docs, it is unclear what rules you would need to have in place if you have a fully locked-down data centre environment.

---

<div class="post-metadata">

**Author:** ![Gianmarco](https://avatars.discourse-cdn.com/v4/letter/g/13edae/32.png) [@Gianmarco](https://discuss.circleci.com/u/Gianmarco)\
**Post date:** [January 22, 2024, 9:56am UTC](https://discuss.circleci.com/t/failed-to-upload-artifacts-from-self-hosted-runner/50260/3 "2024-01-22T09:56:52Z")

</div>

Thank you for investigating. Seems like the issue has indeed something to do with network issues…