jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-23 11:54:18 -05:00
Code Issues Projects Releases Wiki Activity

Bug fixes for Enterprise content, 2022-01-28 (#24798)

Browse Source
This commit is contained in:
Matt Pollard
2022-02-03 12:29:07 +01:00
committed by GitHub
parent 15ed0a363a
commit 52f0a069a1
11 changed files with 41 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
View File

@@ -52,9 +52,11 @@ If you use Docker container actions or service containers in your workflows, you
If these settings aren't correctly configured, you might receive errors like `Resource unexpectedly moved to https://<IP_ADDRESS>` when setting or changing your {% data variables.product.prodname_actions %} configuration.
## Runners not connecting to {% data variables.product.prodname_ghe_server %} after changing the hostname
## Runners not connecting to {% data variables.product.prodname_ghe_server %} with a new hostname
If you change the hostname of {% data variables.product.product_location %}, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs.
{% data reusables.enterprise_installation.changing-hostname-not-supported %}
If you deploy {% data variables.product.prodname_ghe_server %} in your environment with a new hostname and the old hostname no longer resolves to your instance, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs.
You will need to update the configuration of your self-hosted runners to use the new hostname for {% data variables.product.product_location %}. Each self-hosted runner will require one of the following procedures: