Issues with Uploading Artifacts, Caches, and Workspaces on Runner

Overview 

In this article, we'll walk through common issues related to self-hosted runners not being able to upload artifacts, caches, and workspaces in CircleCI. We'll also provide solutions to these problems.

 

Possible Solutions

Here are two common solutions to this problem:

1. Make Sure the Date/Time are Correct on the Runner

The first step is to ensure that the date and time settings on your runner are correct. Incorrect date/time settings can lead to synchronization issues, causing problems when attempting to upload artifacts, caches, and workspaces.

How to check and correct date/time settings:

  • Access your runner's system settings. The method for doing this will vary depending on your runner's operating system.
  • Check the current date/time settings. If they are incorrect, update them to the current date and time.
  • Save the changes and restart your runner if necessary.

2. Confirm that the Runner can Access Certain CircleCI Domains

The second step is to confirm that your runner can access runner.circleci.com and circleci-binary-releases.s3.amazonaws.com. These are domains that CircleCI uses for its operations, and your runner must be able to access them to upload artifacts, caches, and workspaces.

How to confirm domain accessibility:

  • Open a terminal or command prompt on your runner.
  • Use the ping command to check connectivity with the domains. Here's how:
ping runner.circleci.com
ping circleci-binary-releases.s3.amazonaws.com

If the ping returns a response, it means your runner can reach the domains. If it doesn't, there may be a network issue preventing your runner from accessing these domains.

Possible solutions to network issues:

  • Check your firewall settings: Make sure your firewall isn't blocking access to these domains. You may need to add them to an allowlist.
  • Check your network's DNS settings: If your network's DNS server is unable to resolve these domains, you might need to switch to a different DNS server.
  • Check your proxy settings: If your runner is behind a proxy, make sure the proxy is correctly configured to allow access to these domains.

 

Additional Resources

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.