![]() ![]() Crafted with wheat in a 3×3 arrangement.even if you retry more than 10 times manually. I tried to download previous version of the provider but same issue. │ 2 attempts, please try again later: Get " ": net/http: request canceled while waiting for connection (Client.Timeout │ Could not retrieve the list of available versions for provider hashicorp/archive: could not query provider registry for /hashicorp/archive: the request failed after │ attempts, please try again later: Get " ": net/http: request canceled while waiting for connection (Client.Timeout │ Could not retrieve the list of available versions for provider hashicorp/aws: could not query provider registry for /hashicorp/aws: the request failed after 2 │ Error: Failed to query available provider packages Finding latest version of hashicorp/archive.Finding hashicorp/aws versions matching "~> 4.50".+1 with same problem, network issues from provider registry. │ Error while installing hashicorp/external v2.2.2: Get ![]() │ registry for /hashicorp/time: the request failed after │ Error while installing hashicorp/time v0.7.2: could not query provider │ 2 attempts, please try again later: Get │ registry for /hashicorp/tls: the request failed after │ Error while installing hashicorp/tls v3.4.0: could not query provider │ net/http: request canceled while waiting for connection (Client.Timeout Using Azure Pipelines, Microsoft hosted agents: And if so, what is the recommended solution to this? Running terraform init locally on the exact same configuration has so far not caused any issues (although I have not yet tried to simulate breaking some kind of limits here).ĭoes the terraform registry have rate limits per downloading IP? I have not been able to find any documentation on this. I can imagine this being possible though given that we are continuously redownloading things. But it doesn't make sense that this hasn't happened before, and also the intermittent nature seems to suggest that instead some kind of rate limits are being hit, although the error message doesn't specify that. Which seems to suggest it might have something to do with this issue: #27742. T08:14:09.168Z Previous request to the remote registry failed, attempting retry. Net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |