Skip to content

Commit a1be25b

Browse files
Update communicating-with-self-hosted-runners.md (#55595)
Co-authored-by: Joe Clark <[email protected]>
1 parent 7b2c26b commit a1be25b

File tree

1 file changed

+17
-1
lines changed

1 file changed

+17
-1
lines changed

content/actions/hosting-your-own-runners/managing-self-hosted-runners/communicating-with-self-hosted-runners.md

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,14 @@ For caching to work, the runner must be able to communicate with the blob storag
4040

4141
You must ensure that the machine has the appropriate network access with at least 70 kilobits per second upload and download speed to communicate with the {% data variables.product.prodname_dotcom %} hosts listed below. Some hosts are required for essential runner operations, while other hosts are only required for certain functionality.
4242

43-
You can use the REST API to get meta information about {% data variables.product.company_short %}, including the IP addresses of {% data variables.product.company_short %} services. See [AUTOTITLE](/rest/meta/meta).
43+
You can use the REST API to get meta information about {% data variables.product.company_short %}, including the IP addresses and domain details for {% data variables.product.company_short %} services. The `actions_inbound` section of the API supports both fully qualified and wildcard domains. Fully qualified domains specify a complete domain name (e.g., `example.github.com`), while wildcard domains use a `*` to represent multiple possible subdomains (e.g., `*.github.com`). An example of the self-hosted runner requirements using wildcard domains has been listed below. For more information, see [AUTOTITLE](/rest/meta/meta).
44+
45+
```shell copy
46+
github.com
47+
*.github.com
48+
*.githubusercontent.com
49+
ghcr.io
50+
```
4451

4552
{% data reusables.actions.domain-name-cname-recursive-firewall-rules %}
4653

@@ -71,6 +78,15 @@ codeload.github.com
7178
pkg.actions.githubusercontent.com
7279
```
7380

81+
You can use the REST API to get meta information about {% data variables.product.company_short %}, including the IP addresses and domain details for {% data variables.product.company_short %} services. The `actions_inbound` section of the API supports both fully qualified and wildcard domains. Fully qualified domains specify a complete domain name (e.g., `example.github.com`), while wildcard domains use a `*` to represent multiple possible subdomains (e.g., `*.github.com`). An example of the self-hosted runner requirements using wildcard domains has been listed below. For more information, see [AUTOTITLE](/rest/meta/meta).
82+
83+
```shell copy
84+
github.com
85+
*.github.com
86+
*.githubusercontent.com
87+
ghcr.io
88+
```
89+
7490
{% data reusables.actions.domain-name-cname-recursive-firewall-rules %}
7591

7692
{% endif %}

0 commit comments

Comments
 (0)