Unable to download dumb-init. says 403 forbidden
csridhar opened this issue ยท 3 comments
csridhar commented
--2020-05-07 17:22:58-- https://github.com/Yelp/dumb-init/releases/download/v1.2.2/dumb-init_1.2.2_amd64
Resolving github.com (github.com)... 192.30.255.113
Connecting to github.com (github.com)|192.30.255.113|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/40563188/6068ab3c-95ac-11e8-86b7-1c2828e1bea0?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200507%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200507T232258Z&X-Amz-Expires=300&X-Amz-Signature=885c985def9f09e702d8c19bdda2255695af36ff43f663635d67ba648a6ed93d&X-Amz-SignedHeaders=host&actor_id=0&repo_id=40563188&response-content-disposition=attachment%3B+filename%3Ddumb-init_1.2.2_amd64&response-content-type=application%2Foctet-stream [following]
--2020-05-07 17:22:58-- https://github-production-release-asset-2e65be.s3.amazonaws.com/40563188/6068ab3c-95ac-11e8-86b7-1c2828e1bea0?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200507%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200507T232258Z&X-Amz-Expires=300&X-Amz-Signature=885c985def9f09e702d8c19bdda2255695af36ff43f663635d67ba648a6ed93d&X-Amz-SignedHeaders=host&actor_id=0&repo_id=40563188&response-content-disposition=attachment%3B+filename%3Ddumb-init_1.2.2_amd64&response-content-type=application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)... 52.216.107.44
Connecting to github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)|52.216.107.44|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2020-05-07 17:22:58 ERROR 403: Forbidden.
Started seeing this very recently
asottile commented
github had a blip earlier today -- perhaps you were affected by it?
chriskuehl commented
@csridhar are you still seeing this? Looks like it's working for me now.
csridhar commented
yep, definitely related to the github blip. things look good now ๐