---
summary: Build machines reach only their own forge and a list of package sources;
  everything else does not resolve.
title: A CI step can't download something
path: troubleshooting/job-network
status: published
---

# A CI step can't download something

A step fails with an error like `Could not resolve host`, `Temporary failure
in name resolution` or a connection timeout.

Build machines are deliberately closed: they reach their own ScaiGit
instance and a short list of package sources (Ubuntu, PyPI, npm, Go modules,
crates.io and Forgejo's actions mirror). Everything else, `github.com`
included, does not resolve. The full list is in
[Actions → Network](/docs/scaigit/guides/actions#network).

What to do:

- **An action from GitHub.** Use the short form (`actions/checkout@v4`),
  which is fetched from Forgejo's mirror, instead of a
  `https://github.com/...` URL.
- **A tool downloaded from a website.** Install it from a package source
  that is allowed (apt, pip, npm, Go, cargo), or commit what you need to the
  repository.
- **A source your build really needs.** Ask your administrator to allow it
  for your instance.
