403 error while downloading the install script #2664
Comments
|
This happens because you exceeded the Github api rate limit. {
"message": "API rate limit exceeded for xx.xx.xx.xx. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
"documentation_url": "https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting"
} |
|
Yah, unfortunately this is expected. On Github actions, try installing via some other method, like a package manager. |
|
One thing that could potentially help here is if there was an official docker container to utilize. Just has frequent enough releases that installing alpine and using their packaging is not ideal (what might be the most up to date/lightest distro to use) ? Related to #1497. |
|
I don't maintain any packages or distributions of |
This adds support for utilizing the env var GITHUB_TOKEN if it exists for both curl/wget download utils. fixes casey#2664
This adds support for utilizing the env var GITHUB_TOKEN if it exists for both curl/wget download utils. The token handling portion is removed from debug output, which only includes writing the token to a temporary file. Using a temp file ensures that the token is not shown during the download both in debug output or ps output. fixes casey#2664
This adds support for utilizing the env var GITHUB_TOKEN when the --auth flag is passed for both curl/wget download utils. The command invocations are not included in xtrace output so that the token is not logged. fixes casey#2664
This adds support for utilizing the env var GITHUB_TOKEN when the --auth flag is passed for both curl/wget download utils. The command invocations are not included in xtrace output so that the token is not logged. fixes casey#2664
I'm not sure if this is the appropriate place for this issue but running
curl --proto '=https' --tlsv1.2 -sSf https://just.systems/install.sh | bash -s -- --to DESTis returning the following error:curl: (22) The requested URL returned error: 403The text was updated successfully, but these errors were encountered: