Hey Mark,
I'm with the same problem, my host IP address is 165.22.236.91
Hi,
same here now on DigitalOcean FRA1. Public IP address is 104.248.27.109.
$ wget -vO - https://artifacts.elastic.co/GPG-KEY-elasticsearch | sudo apt-key add -
--2020-06-16 18:03:12-- https://artifacts.elastic.co/GPG-KEY-elasticsearch
Resolving artifacts.elastic.co (artifacts.elastic.co)... 151.101.114.222, 2a04:4e42:1b::734
Connecting to artifacts.elastic.co (artifacts.elastic.co)|151.101.114.222|:443... connected.
HTTP request sent, awaiting response... 451 Unavailable For Legal Reasons
2020-06-16 18:03:12 ERROR 451: Unavailable For Legal Reasons.
gpg: no valid OpenPGP data found.
This continues to be an issue. Most recent attempt from IP 159.203.7.233:
...
Err:12 https://packages.elastic.co/kibana/4.6/debian stable Release
451 Unavailable For Legal Reasons
Err:20 https://artifacts.elastic.co/packages/5.x/apt stable Release
451 Unavailable For Legal Reasons
Err:23 https://artifacts.elastic.co/packages/6.x/apt stable Release
451 Unavailable For Legal Reasons
Err:25 https://artifacts.elastic.co/packages/7.x/apt stable Release
451 Unavailable For Legal Reasons
64.227.18.113, which is a droplet with Digital Ocean in their NYC1 datacenter:
wget https://artifacts.elastic.co/GPG-KEY-elasticsearch
--2020-06-16 17:52:37-- https://artifacts.elastic.co/GPG-KEY-elasticsearch
Resolving artifacts.elastic.co (artifacts.elastic.co)... 151.101.210.222, 2a04:4e42:31::734
Connecting to artifacts.elastic.co (artifacts.elastic.co)|151.101.210.222|:443... connected.
HTTP request sent, awaiting response... 451 Unavailable For Legal Reasons
2020-06-16 17:52:37 ERROR 451: Unavailable For Legal Reasons.
Seriously guys, this makes it a pain in the ass to use your product correctly, and it's been going on for a long time. Give us a way around it or get it fixed. PLEASE.
Thanks for the IPs folks, please do keep listing them and we will pass them to our provider.
Hi,
I'm having the same issue from my colo provider in Canada:
$ sudo dnf update
CentOS-8 - AppStream 14 kB/s | 4.3 kB 00:00
CentOS-8 - Base 719 B/s | 3.9 kB 00:05
CentOS-8 - Base 270 kB/s | 2.2 MB 00:08
CentOS-8 - Extras 4.8 kB/s | 1.5 kB 00:00
Docker CE Stable - x86_64 77 kB/s | 3.5 kB 00:00
Elastic repository for 7.x packages 0.0 B/s | 0 B 00:00
Failed to download metadata for repo 'elastic-7.x'
Error: Failed to download metadata for repo 'elastic-7.x'
$ sudo rpm --import https://packages.elastic.co/GPG-KEY-elasticsearch
curl: (22) The requested URL returned error: 451
error: https://packages.elastic.co/GPG-KEY-elasticsearch: import read failed(2).
The public IP is 38.117.105.228
Hi warkolm,
here is my IP: 159.89.33.40
It's Digital Ocean NYC3, if it makes sense
Thank you for you time and support.
E: Failed to fetch https://artifacts.elastic.co/packages/7.x/apt/dists/stable/InRelease 451 Unavailable For Legal Reasons [IP: 151.101.18.222 443]
DigitalOcean LON1, been waiting a week for fix - anyone know of mirror?
I've checked round for a mirror but couldn't find one.
@warkolm any idea how long it'd take for each listed IP to be resolved?
The trouble server is meant to be live on Friday but we'd have no central logging in place at this rate which would be scary.
@rmcevoy need it for a production server also - considering installing openvpn and tunneling through one of my other servers, it should work in theory (then disconnect after). Or it might be possible to build from source?
@rickyodin I attempted using OpenVPN and but the second I routed traffic through the vpn my SSH connection dropped and I had to reboot 
I don't want to build from source as then I'll have to maintain the updates myself instead or roll-back later to the official releases
Ah yes, good point. I'm wondering if another new droplet would be blocked? Because could build snapshot of droplet -> restore to another droplet -> install elasticsearch -> snapshot -> restore to original droplet. #effort
Problem is you won't know until you try it, unfortunately the floating IPs can't be seen by droplets either so you can't even use that as a workaround by routing all traffic through that IP.
If the problem isn't resolved by friday morning I'll have to duplicate my whole droplet and test if that works instead
I'm also experiencing this issue on DigitalOcean, but not on other providers.
DigitalOcean Server IP: 167.71.9.136
Datacenter: Amsterdam 3
I am also experiencing the same LON1 digitalocean
the new one, in DigitalOcean Canada is 165.227.46.175
This is unbelievable... still happening at FRA1 DigitalOcean.
I'd rather not list my ip publicly.
Also seeing this - DO LON1
This is causing us a major issue at the moment as all our traffic flows through a couple of servers in this region which act as aggregators, and our outbound proxy is in this region as well meaning that anything behind the proxy (we have site-to-site VPN's for all traffic) is also denied access to deploy.
@warkolm: For obvious security reasons I'm unable to share the affected IP Addresses, but as a DO partner I'm happy to talk with them about it as well or at least put someone from Elastic in touch with them if you're not speaking already?
FWIW, we're using YUM, not Apt, but I suspect it's the same CDN causing these issues!
I should also point out that this is happening with CURL as well when trying to download any of the binaries, so trying to install those "directly" isn't really an option either:
curl -I https://artifacts.elastic.co/downloads/logstash/logstash-7.8.0.rpm
HTTP/1.1 451 Unavailable For Legal Reasons
Connection: close
Content-Length: 0
Retry-After: 0
Accept-Ranges: bytes
Date: Fri, 19 Jun 2020 12:04:20 GMT
Via: 1.1 varnish
X-Served-By: cache-lcy19226-LCY
X-Cache: MISS
X-Cache-Hits: 0
X-Timer: S1592568260.049992,VS0,VE0
server: ElasticInfrastructure
I've raised this with DO, they're looking into it.