We get a 403 error, which prevents us from downloading images of your products from the repository, and, as I understand it, it doesn't even allow us to upload images on the Kibana page with data integrations
[2025-12-15T12:00:40.103+00:00][ERROR][plugins.fleet] '403 Forbidden' error response from package registry at ``https://epr.elastic.co/package/atlassian_confluence/1.29.2/img/confluence-logo.svg [2025-12-15T12:00:40.148+00:00][ERROR][plugins.fleet] '403 Forbidden' error response from package registry at ``https://epr.elastic.co/package/auth0/1.23.0/img/auth0-logo.svg`` [2025-12-15T12:00:40.179+00:00][ERROR][plugins.fleet] '403 Forbidden' error response from package registry at ``https://epr.elastic.co/package/aws/5.0.0/img/logo_aws.svg
But our main problem is reaching these addresses, for example: ``https://artifacts.elastic.co/downloads/beats/elastic-agent/elastic-agent-9.2.2-linux-x86_64.tar.gz
and this applies to any of your product packages. Please help. Below is some information about us:
Thanks, @carly.richmond , but the geoip data shows correctly that the server is in the neatherlands, which I guess is not a sanctioned country
@Robert_Garrigos you are correct that the server is located in the Netherlands, which is not a sanctioned country. However, the blocking is done at an ASN level, and the ASN that your IP belongs to has a connection to a sanctioned country that cannot be unblocked as it would let traffic that should be blocked through.
If you think the ASN information is incorrect, you can request from the main IP database providers to update the information.
Glad to hear it’s working for you since this morning. Thanks for checking it in multiple ways as well (websites, curl, and Chocolatey), that really helps narrow things down.
Next time, if you’re able to grab the IPs, that would be perfect, but for now it sounds like everything has stabilized.
Hi @carly.richmond , I asked our network team, they said that nothing like this is on.
We are using ipv4, and “artifacts.elastic.co” worked before.
And It is working for other IPs from “our pool” now e.g. 160.72.147.88
Thanks for confirming @kim_dev. You say it's working from other IPs from the pool now. Can you confirm if the original IP is still experiencing a 403? I just want to check if it was a temporary issue that is now resolved.
Thanks for confirming @kim_dev. I've raised the ticket and will provide an update when I hear back. Just a heads up that it can take some time to get a response from the team.
Ok, no problem, I can’t disable IPv6 but it is not used if you didn’t configure it on your side since ou don’t support it. Juste the 6 IPv5 addresses should be enough.
Thanks @Thomas_DE_LUCA . Before I raise the issue can you perform a trace as per these instructions to verify that you're definitely not hitting IPv6? We have seen cases where IPv6 is triggered when enabled even if it's not used.
I hope you're well. Not sure if you're still having issues, but the ASN is added to the allow list. It might take a bit of time to propagate, but if you're still encountering issues let us know!
Hi, I tried curl -x internal-proxy:5555--trace - --trace-time https://artifacts.elastic.co/GPG-KEY-elasticsearch and it worked fine. It seems to work with IPv4 only but I can only see my proxy’s IPv4.
Can you confirm which Elastic asset you're trying to download (or command you're running ) and that IPv6 is disabled on your host? That is a common reason for issues.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.