Are you getting 403's when downloading? Please read here first

Meta Elastic
275

Hello. I am getting 403 from Uzbekistan

{
  "ip": "89.232.184.162",
  "city": "Tashkent",
  "region": "Tashkent",
  "country": "UZ",
  "loc": "41.2647,69.2163",
  "org": "AS43647 SERVERCORE CIS LLC",
  "timezone": "Asia/Tashkent",
  "readme": "https://ipinfo.io/missingauth"
}

Err:6 https://artifacts.elastic.co/packages/8.x/apt stable InRelease
403 Forbidden [IP: 34.120.127.130 443]

276

all ips of Servercore -

https://www.ip2location.com/as43647
277

34.120.127.130 403

{
  "ip": "35.214.163.51",
  "hostname": "51.163.214.35.bc.googleusercontent.com",
  "city": "Groningen",
  "region": "Groningen",
  "country": "NL",
  "loc": "53.2192,6.5667",
  "org": "AS15169 Google LLC",
  "postal": "9711",
  "timezone": "Europe/Amsterdam",
  "readme": "https://ipinfo.io/missingauth"
}
278

Welcome @Pabs!

Thanks for sharing your IP. Can you confirm which location/ artifact you are trying to access?

279

Hi @a.hozyainov,

We're taking a look. I'll keep you posted!

280

https://artifacts.elastic.co/packages/7.x/apt/dists/stable/InRelease

281

We're getting 403s, which sounds a bit weird because we're coming from GCP as well.

What we're trying to fetch is the elasticsearch<dot>org/GPG-KEY-elasticsearch , but it seems our IP is banned for all of elasticsearchorg and subsequent tries to install anything also fails. [Note: I had to type elasticsearchorg or the forum won't let me post the actual URL for some reason]

Seems like the ban lifts about once a day, but then quickly re-affirms itself and we're banned again. This has only started very recently despite not increasing our call volume.

Since this is a NAT IP, there might be a higher volume of calls from there than what you'd expect for a single server/cluster, but I couldn't find anything about rate limits that would restrict this.

{
  "ip": "34.159.46. 87",
  "hostname": "87.46.159.34.bc.googleusercontent.com",
  "city": "Frankfurt am Main",
  "region": "Hesse",
  "country": "DE",
  "loc": "50.1155,8.6842",
  "org": "AS396982 Google LLC",
  "postal": "60306",
  "timezone": "Europe/Berlin",
}
282

Hi, we are getting random block while APT update 1-2 in 24 request will go throught, but mainly they are blocked. Issue persist for last ~14 days.

{
  "ip": "88. 86. 105_7",
  "hostname": "xxx", # don't want to expose this one, its our customer info
  "city": "Prague",
  "region": "Prague",
  "country": "CZ",
  "loc": "50.0880,14.4208",
  "org": "AS39392 SH.cz s.r.o.",
  "postal": "110 00",
  "timezone": "Europe/Prague",
  "readme": "https://ipinfo.io/missingauth"
}

Same issue have 4 other server's from 88.86.105.0/24

E: Failed to fetch https://artifacts.elastic.co/packages/8.x/apt/dists/stable/InRelease  403  Forbidden [IP: 34.120.127.130 443]

We are quite large hosting company in Czechia, would it be maybe possible to get in touch with somebody about repository mirror?

283

Thanks for raising @a.hozyainov. I've received confirmation that the IP has been unblocked. If you're still having issues in a couple of days just let me know.

1 Like
284

Thanks @MrTrustworthy and @Pabs for the details. I'm slightly surprised at these ones since they are Google LLC but I've raised a request and will come back with an update when I've heard back from the team.

1 Like
285

Thanks for raising @jakub.pinkas. I've raised a request for your IP range and will provide an update when I hear back from the team.

286

@carly.richmond
Hello,
We are getting 403 from Google, europe-west3 region.
34.107.20.197

Can you please check?

287

Hi @Bakar_Chkhaidze,

You look to be having the same issue as @MrTrustworthy. I've raised it with the team and we'll come back when we can.

If you have any other details such as which artefact you are struggling to access or if like @MrTrustworthy it is an intermittent block do let us know.

288

Hi! @carly.richmond @warkolm

We are reaching out from Pro-Data, we are cloud infrastructure service provider in Uzbekistan.

Our customers encountering problems accessing your services due to incorrect association of subnet 95.47.238.0/23 with another country. It looks like our subnet is on your blacklist on your end due to this reason.

Please remove our subnet from your blacklist since our subnet is located in the UZ zone. Thank you.

ip:"95.47.238.0",
city:"Tashkent",
region:"Tashkent",
country:"UZ",
loc:"41.2647,69.2163",
org:"AS213029 PRO DATA-TECH Ltd.",
timezone:"Asia/Tashkent",
289

Hi @zhnv,

Welcome! Thanks for raising. I've raised the issue for this subnet with our team and will revert back when I have an update.

Hope that helps!

290

Hi @a.hozyainov,

I've received word that your IP unblock has been actioned. Check and let us know if you're still facing issues in a couple of days as the change can take time to propogate.

Thanks!

291

Hi, Carly

I've checked it and all works. Thank you

ср, 31 янв. 2024 г. в 14:27, Carly Richmond via Discuss the Elastic Stack <notifications@elastic.discoursemail.com>:

1 Like
292

getting

Err:1 https://artifacts.elastic.co/packages/8.x/apt stable/main amd64 filebeat amd64 8.12.0
  403  Forbidden [IP: 34.120.127.130 443]

when trying to install with apt

ip - 46.17.99.18

* ip:"46.17.99.18",

* city:"Amsterdam",

* region:"North Holland",

* country:"NL",

* loc:"52.3740,4.8897",

* org:"AS57043 HOSTKEY B.V.",

* postal:"1012",

* timezone:"Europe/Amsterdam",

* asn:Object,

  * asn:"AS57043",

  * name:"HOSTKEY B.V.",

  * domain:"hostkey.com",

  * route:"46.17.99.0/24",

  * type:"hosting",
* company:Object,

  * name:"HOSTKEY B.V.",

  * domain:"hostkey.com",

  * type:"hosting",
* privacy:Object,

  * vpn:false,

  * proxy:false,

  * tor:false,

  * relay:false,

  * hosting:true,

  * service:"",
* abuse:Object,

  * address:"W Frederik Hermansstr 91, 1011DG, Amsterdam, NETHERLANDS",

  * country:"NL",

  * email:"abuse@hostkey.nl",

  * name:"Hostkey_NL abuse",

  * network:"46.17.97.32-46.17.99.255",

  * phone:"+31208203777",
293

Thanks for raising @stashevvsky. I've raised the issue and will report back when I have an update.

294

Hi @Bakar_Chkhaidze and @MrTrustworthy,

Hope you're well. I've checked with our team and these IPs are allowed since they're owned by Google and covered by our services. We haven't blocked them.

I would recommend reporting this issue to Google. As a contingency, we would advise you to download the artefacts from hosts with other IPv4 or IPv6 IPs if you can.

Hope that helps!