Outbound traffic
Allow or deny the hosts and networks your jobs may reach.
Egress rules decide which addresses a job's machine may connect to. Use them to block a package mirror you don't trust, or to lock jobs down to GitHub and a short list of hosts. An admin sets them in Settings → Egress rules, and they apply to every job in the workspace from its next start.
How a connection is decided
Each outgoing connection is checked in this order, and the first match wins:
- Loopback, the machine talking to itself, is always allowed.
- Your deny rules.
- Your allow rules.
- The default policy: allow or deny.
With the default set to deny, GitHub (including ghcr.io and the Actions services), RaftRun itself and the cache's storage stay reachable, so jobs can still check out code, report progress and use the cache.
Rule types
| Type | Example | Matches |
|---|---|---|
| Hostname | registry.npmjs.org | The addresses that name resolves to when the job starts. Subdomains are separate names. |
| IP address | 203.0.113.10 | That one address. |
| CIDR block | 10.0.0.0/8 | Every address in the range. |
Allow only what jobs need
Add allow rules first
For example
registry.npmjs.org,pypi.org,files.pythonhosted.org,registry-1.docker.io, and your deploy target.Set the default to deny
Save it. Jobs that start from now on get the new rules; running jobs keep theirs.
Watch the next runs
A blocked connection shows in the job's log as a timeout or "connection refused". Search the logs for it and add the host that was missing.
What rules don't do
- They cover IPv4. With a deny default, IPv6 is blocked outright.
- Hostnames are resolved once, at the start of the job. A service whose addresses change from minute to minute, such as some CDNs, may need a CIDR rule instead.
- They are a guard rail, not a sandbox. A job runs as root and can change the machine's firewall. They stop mistakes and unwanted dependencies, not a hostile workflow.