# Official apt repository (451 Unavailable For Legal Reasons) **URL:** \ **Category:** Elasticsearch\ **Created:** [May 13, 2020, 6:09pm UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494 "2020-05-13T18:09:39Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![vdt\_mik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vdt_mik/32/59998_2.png) [@vdt\_mik](https://discuss.elastic.co/u/vdt_mik)\ **Post date:** [May 13, 2020, 6:09pm UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/1 "2020-05-13T18:09:39Z")
Hi! I faced this problem in my VM on the DigitalOcean(Europe region). I tried to do an apt update in my Debian 9 VM. But I recieved this message: ``` Ign:1 http://deb.debian.org/debian stretch InRelease Hit:2 http://security.debian.org stretch/updates InRelease Hit:3 http://deb.debian.org/debian stretch Release Hit:4 http://nginx.org/packages/mainline/debian stretch InRelease Ign:5 https://artifacts.elastic.co/packages/7.x/apt stable InRelease Ign:6 https://artifacts.elastic.co/packages/oss-7.x/apt stable InRelease Err:7 https://artifacts.elastic.co/packages/7.x/apt stable Release 451 Unavailable For Legal Reasons Err:8 https://artifacts.elastic.co/packages/oss-7.x/apt stable Release 451 Unavailable For Legal Reasons ``` Ip: 157.230.23.XXX ![photo5325765932896857701](https://us1.discourse-cdn.com/elastic/original/3X/3/6/364a578862d20552c1431ffae72bfa8fccc04783.jpeg) ---
**Author:** ![Luca\_Belluccini](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/luca_belluccini/32/33239_2.png) [@Luca\_Belluccini](https://discuss.elastic.co/u/Luca_Belluccini)\ **Post date:** [May 13, 2020, 7:25pm UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/2 "2020-05-13T19:25:36Z")
Hello! We are aware of the issue and waiting for the CDN provider to resolve a small issue with their geoip filters. A rough estimate might be end of this week, but cannot confirm 100%. Please post again if you will still face the issue. ---
**Author:** ![MikeHarness](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikeharness/32/67763_2.png) [@MikeHarness](https://discuss.elastic.co/u/MikeHarness)\ **Post date:** [May 15, 2020, 6:59pm UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/3 "2020-05-15T18:59:33Z")
Glad it's not just me. All my nodes are hosted by Vultr, but all within the US. ---
**Author:** ![OE-Eddie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oe-eddie/32/45218_2.png) [@OE-Eddie](https://discuss.elastic.co/u/OE-Eddie)\ **Post date:** [May 16, 2020, 1:43am UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/4 "2020-05-16T01:43:34Z")
Same problem with Digitalocean in sfo2 region. Fails with error 451 about 50% of the time when creating a 3 node cluster. Makes deploying IaC basically impossible. ---
**Author:** ![aximuseng](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@aximuseng](https://discuss.elastic.co/u/aximuseng)\ **Post date:** [May 16, 2020, 7:08am UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/5 "2020-05-16T07:08:20Z")
Same here Digital Ocean tor1 region - servers currently DOA after a failed update. ---
**Author:** ![MaJaHa95](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/majaha95/32/26121_2.png) [@MaJaHa95](https://discuss.elastic.co/u/MaJaHa95)\ **Post date:** [May 18, 2020, 1:28am UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/6 "2020-05-18T01:28:25Z")
No news yet, I take it? ☹ I'm still seeing this, as OE-Eddie had said, in DigitalOcean SFO2. It wouldn't be possible to temporarily disable the geoip while they work through this? ---
**Author:** ![Luca\_Belluccini](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/luca_belluccini/32/33239_2.png) [@Luca\_Belluccini](https://discuss.elastic.co/u/Luca_Belluccini)\ **Post date:** [May 18, 2020, 8:05am UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/7 "2020-05-18T08:05:00Z")
Thank you for reporting. Our provider shared a date for the fix, which should be the 22nd May. ---
**Author:** ![OE-Eddie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oe-eddie/32/45218_2.png) [@OE-Eddie](https://discuss.elastic.co/u/OE-Eddie)\ **Post date:** [May 18, 2020, 4:55pm UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/8 "2020-05-18T16:55:06Z")
Still happening for me and it's unlikely they will disable it because it's probably part of embargo check. That said, not sure why it's taking so long to fix unless they are using a 3rd party provider instead of local database (maxmind, etc) and need to go through them for a fix. Strange thing is, I looked up the geoip location of several of the IPs that failed and they all showed as Santa Clara, CA which I'm relatively sure isn't on the embargo list. ---
**Author:** ![Luca\_Belluccini](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/luca_belluccini/32/33239_2.png) [@Luca\_Belluccini](https://discuss.elastic.co/u/Luca_Belluccini)\ **Post date:** [May 20, 2020, 9:19pm UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/9 "2020-05-20T21:19:04Z")
We have a CDNs to provide faster downloads. ---
**Author:** ![MikeHarness](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikeharness/32/67763_2.png) [@MikeHarness](https://discuss.elastic.co/u/MikeHarness)\ **Post date:** [May 22, 2020, 8:49pm UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/10 "2020-05-22T20:49:29Z")
Any update? ---
**Author:** ![datn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/datn/32/9184_2.png) [@datn](https://discuss.elastic.co/u/datn)\ **Post date:** [May 23, 2020, 2:04pm UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/11 "2020-05-23T14:04:35Z")
Thanks for this information. As of this writing (16:00 CEST on 2020-05-23) the problem is still happening. Do you have any updates from your CDN provider? ---
**Author:** ![403Page](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/403page/32/68975_2.png) [@403Page](https://discuss.elastic.co/u/403Page)\ **Post date:** [May 24, 2020, 7:47pm UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/12 "2020-05-24T19:47:20Z")
Same for me as of today. Digital Ocean droplet in London. ---
**Author:** ![Koldunz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/koldunz/32/45055_2.png) [@Koldunz](https://discuss.elastic.co/u/Koldunz)\ **Post date:** [May 25, 2020, 2:27pm UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/13 "2020-05-25T14:27:42Z")
The problem is still happening. Do you have any updates from your CDN provider? Droplet in USA ---
**Author:** ![Liam\_Hennessy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/liam_hennessy/32/69017_2.png) [@Liam\_Hennessy](https://discuss.elastic.co/u/Liam_Hennessy)\ **Post date:** [May 25, 2020, 3:39pm UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/14 "2020-05-25T15:39:00Z")
Same here, Droplet in Toronto ```auto E: Failed to fetch https://artifacts.elastic.co/packages/6.x/apt/dists/stable/InRelease 451 Unavailable For Legal Reasons [IP: 2a04:4e42:1e::734 443] ``` ---
**Author:** ![Sandesh\_Rana](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sandesh_rana/32/69060_2.png) [@Sandesh\_Rana](https://discuss.elastic.co/u/Sandesh_Rana)\ **Post date:** [May 26, 2020, 8:24am UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/15 "2020-05-26T08:24:41Z")
same issue here in South East Asia ``` 2020-05-26 08:08:12 ERROR 451: Unavailable For Legal Reasons. ``` ---
**Author:** ![TillmanZ](https://avatars.discourse-cdn.com/v4/letter/t/8491ac/32.png) [@TillmanZ](https://discuss.elastic.co/u/TillmanZ)\ **Post date:** [May 26, 2020, 10:05am UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/16 "2020-05-26T10:05:55Z")
Same issue still happening from DigitalOcean instances in Frankfurt and Amsterdam. I really do not understand why fixing this could be so time consuming. And besides - if this geo IP check was implemented because of any embargo reasons (which personally I would not really understand anyway), why won't you just add any embargoed (is this a word?) country to you license and exclude them from using it? I don't see how an open source project would be required to implement geo IP filtering (on whose authority). Best, Tillman ---
**Author:** ![rugma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugma/32/69271_2.png) [@rugma](https://discuss.elastic.co/u/rugma)\ **Post date:** [May 28, 2020, 9:23am UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/17 "2020-05-28T09:23:52Z")
Still happening from Canada. I can't believe it takes so long to fix this issue ---
**Author:** ![andrey\_borisov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrey_borisov/32/69273_2.png) [@andrey\_borisov](https://discuss.elastic.co/u/andrey_borisov)\ **Post date:** [May 28, 2020, 10:12am UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/18 "2020-05-28T10:12:33Z")
from digitalocean VM in LON1 just now ``` wget https://artifacts.elastic.co/packages/7.x/yum/repodata/repomd.xml --2020-05-28 10:11:01-- https://artifacts.elastic.co/packages/7.x/yum/repodata/repomd.xml Resolving artifacts.elastic.co (artifacts.elastic.co)... 151.101.18.222, 2a04:4e42:4::734 Connecting to artifacts.elastic.co (artifacts.elastic.co)|151.101.18.222|:443... connected. HTTP request sent, awaiting response... 451 Unavailable For Legal Reasons 2020-05-28 10:11:01 ERROR 451: Unavailable For Legal Reasons. ``` ---
**Author:** ![Luca\_Belluccini](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/luca_belluccini/32/33239_2.png) [@Luca\_Belluccini](https://discuss.elastic.co/u/Luca_Belluccini)\ **Post date:** [May 28, 2020, 10:23am UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/19 "2020-05-28T10:23:57Z")
Hello all, While I'm sharing this thread with Elastic infra team to follow up, they informed me while the geoip databases have been updated, the edge nodes are not still in sync and the provider expects them to be updated tomorrow (29th May). ---
**Author:** ![samu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/samu/32/47746_2.png) [@samu](https://discuss.elastic.co/u/samu)\ **Post date:** [May 29, 2020, 2:12am UTC](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494/20 "2020-05-29T02:12:43Z")
Hi Luca, should a solution be implemented tomorrow?, I continue with the problem. [Next page](https://discuss.elastic.co/t/official-apt-repository-451-unavailable-for-legal-reasons/232494.md?page=2)