Forbidden Runner version v2.317.0 is deprecated and cannot receive messages
Problem
This happened to us on 2.317.0, which is the latest version at time of writing: [code block] It happened twice. Timestamps in UTC. past occurence: https://github.com/actions/runner/issues/3366#issuecomment-2204514441
Error Output
error occured: Error: Forbidden Runner version v2.317.0 is deprecated and cannot receive messages.
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Upgrade to a Supported Runner Version
The error 'Forbidden Runner version v2.317.0 is deprecated and cannot receive messages' occurs because the GitHub Actions runner version 2.317.0 has been deprecated. This means that it no longer receives updates or support, leading to communication failures with GitHub's servers.
Awaiting Verification
Be the first to verify this fix
- 1
Check Current Runner Version
Verify the currently installed version of the GitHub Actions runner to confirm it is indeed v2.317.0.
bashecho 'Current Runner Version: $(./bin/Runner --version)' - 2
Download Latest Runner Version
Download the latest stable version of the GitHub Actions runner from the official GitHub releases page.
bashcurl -o actions-runner-linux-x64-<latest_version>.tar.gz -L https://github.com/actions/runner/releases/download/v<latest_version>/actions-runner-linux-x64-<latest_version>.tar.gz - 3
Stop the Current Runner
Stop the currently running GitHub Actions runner to prepare for the upgrade.
bash./svc.sh stop - 4
Extract the New Runner Files
Extract the downloaded runner files to the appropriate directory.
bashtar xzf ./actions-runner-linux-x64-<latest_version>.tar.gz - 5
Configure the New Runner
Reconfigure the runner with your GitHub repository settings, ensuring it connects properly to GitHub Actions.
bash./config.sh --url https://github.com/<your_org>/<your_repo> --token <your_token> - 6
Start the New Runner
Start the newly configured runner to begin receiving messages and processing jobs.
bash./svc.sh install && ./svc.sh start
Validation
To confirm the fix worked, check the runner logs for successful connection messages and ensure that jobs are being processed without errors. You can also verify the runner version by running './bin/Runner --version' again to ensure it reflects the new version.
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep