# Problem accessing charts and artifacts from hetzner.de servers

**URL:** <https://discuss.elastic.co/t/problem-accessing-charts-and-artifacts-from-hetzner-de-servers/300840>\
**Category:** Meta Elastic\
**Created:** [March 28, 2022, 12:12pm UTC](https://discuss.elastic.co/t/problem-accessing-charts-and-artifacts-from-hetzner-de-servers/300840 "2022-03-28T12:12:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![nymous](https://avatars.discourse-cdn.com/v4/letter/n/5daacb/32.png) [@nymous](https://discuss.elastic.co/u/nymous)\
**Post date:** [March 28, 2022, 12:12pm UTC](https://discuss.elastic.co/t/problem-accessing-charts-and-artifacts-from-hetzner-de-servers/300840/1 "2022-03-28T12:12:26Z")

</div>

Hi folks! I have a strange issue with getting artifacts (debs, helm charts) from [elastic.co](http://elastic.co/) for my cloud at [Hetzner.de](http://hetzner.de/). Some servers are downloading them fine, but others just get 403 error. Is there a reason for that, did I missed something? I can't find the pattern, servers are from different subnets, some of them are just rented and simply yet empty, so they shouldn't be doing any activity against [helm.elastic.co](http://helm.elastic.co/) or [artifacts.elastic.co](http://artifacts.elastic.co/)

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [March 29, 2022, 8:01am UTC](https://discuss.elastic.co/t/problem-accessing-charts-and-artifacts-from-hetzner-de-servers/300840/2 "2022-03-29T08:01:31Z")

</div>

Hey,

this looks indeed weird and fishy. Can you share ip blocks or exact error messages, so we could take a look?

--Alex

---

<div class="post-metadata">

**Author:** ![nymous](https://avatars.discourse-cdn.com/v4/letter/n/5daacb/32.png) [@nymous](https://discuss.elastic.co/u/nymous)\
**Post date:** [March 29, 2022, 10:26pm UTC](https://discuss.elastic.co/t/problem-accessing-charts-and-artifacts-from-hetzner-de-servers/300840/3 "2022-03-29T22:26:54Z")

</div>

Hi Alexander,

The message is just this (if I curl [helm.elastic.co](http://helm.elastic.co), for example):  
`<!doctype html><meta charset="utf-8"><meta name=viewport content="width=device-width, initial-scale=1"><title>403</title>403 Forbidden`

As for ranges, I have problems with almost all 135.181.0.0/16 addresses, though there are several which got 200 reply and proper output. Also 65.108.0.0/15 and 95.217.0.0/16 seem to be affected. I do not see a pattern really. Say I have 20 servers in 135.181.0.0/16 subnet, 18 of which do reply with 403, while 2 are completely ok.

Most of my servers are in Helsinki's DCs, if it rings any bells.

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [March 30, 2022, 8:11am UTC](https://discuss.elastic.co/t/problem-accessing-charts-and-artifacts-from-hetzner-de-servers/300840/4 "2022-03-30T08:11:23Z")

</div>

I have forwarded this internally and we will take a look. it seems there is indeed an issue with wrongly blocking some IPs.

Thanks for raising!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 27, 2022, 8:11am UTC](https://discuss.elastic.co/t/problem-accessing-charts-and-artifacts-from-hetzner-de-servers/300840/5 "2022-04-27T08:11:58Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
