-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chart repository not reachable (DNS Issue) #13313
Comments
same issue |
Does Bitnami provide some kind of status page by the way? |
Seem fix now : http://dns.squish.net/traverses/958c5af6fa063f7bb00db86b71aecb18 But CNAME are in cache for 2h new one is "dqk9m89za31r9.cloudfront.net" |
I can confirm I am now getting good DNS lookups from some locations. |
I am still hitting errors too.
|
Yes - you have to flush DNS. Then the issue should be solved. Having the same issue.. |
hello sir when will the issue be of the fix sir? my koobyneet is now in the broke?? |
Recommendation: LOCK, and add comment from maintainers. DNS is repopulating, and the issue is resolved. Flush your caches, if necessary. For confirmation, use
|
Had to re-run the command a few times to have the DNS propagate to the new URL, but yeah it seems fixed. |
my DNS was still hitting old distribution. Updating the nameserver to 8.8.4.4 did the trick for me. thanks, guys. |
When is this going to be solved? |
Thanks for reporting this issue. It was a problem in the CloudFront distribution that we used for the Charts repository. The problem is that terraform recreated the CloudFront collection, creating a new DNS endpoint that needed to replicate globally. A small number of DNS are still resolving the old CloudFront collection name, but for the most part, the issue should be fixed shortly. |
I ran the following commands but still got the same issue. Am I missing anything?
I ran the commands multiple times/ fresh session. |
@codablock I can resolve the host:
but this is what I a getting now:
I am not sure if this is a new issue. |
Same issue here:
|
not related, 403 Forbidden mean your reach the endpoint. this issue was about DNS issues not permissions. |
Thanks. Thought it is related, charts were working few days back. We are using postgres chart as a dependency. I will see if there is another ticket, or will report one for 403. |
getting the same error as @sumesh-aot with the prestashop chart, nothing has changed on our end and since this morning I im getting 403 |
@carrodher Still getting errors: |
The problem still exists |
Name and Version
All Charts
What steps will reproduce the bug?
Are you using any custom parameters or values?
No
What is the expected behavior?
Chart repository is reachable at https://charts.bitnami.com/bitnami
What do you see instead?
In browser
DNS_PROBE_FINISHED_NXDOMAIN
, in helmdial tcp: lookup charts.bitnami.com on ... : no such host
Additional information
nslookup gives the following:
charts.bitnami.com canonical name = d1xe8nqhpmcyfh.cloudfront.net.
The text was updated successfully, but these errors were encountered: