Unable to configure elastic search apt repository as a remote repository in Artifactory

Hi all,

We are trying to configure Elasticsearch apt repository in Artifactory, but it always fails due to a error: "HTTP ERROR 404"

We are using the following URL: https://artifacts.elastic.co/packages/8.x/apt

The same issue occur if i try to setup the rpm remote repository with the following URL: https://artifacts.elastic.co/packages/8.x/yum/

Does anyone knows why this happens? Isn't it possible to set the apt repository this way, or there's another URL to do it?

Thank you very much

Welcome to our community! :smiley:

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


Thanks for your reply.

It isn't 403 error when downloading, it's HTTP ERROR 404 when trying to setup the repository using the URL: https://artifacts.elastic.co/packages/8.x/apt or the yum.

Since it can't find the page, we just can't setup it as a remote repository in Jfrog artifactory.

I wonder if someone had a similar problem and how it was fixed (or if even possible).


Ahh sorry, I am used to seeing so many 403s I misread that.

Our RPM repo instructions are at Install Elasticsearch with RPM | Elasticsearch Guide [8.7] | Elastic. If this is what you are doing then it'd be good to see the commands you are running to set it up, the install commands you are running and the output.

Hey there,

Thanks again for your reply.

Maybe i didn't explain my self properly :grinning:.

My goal here's to setup the Elastic Search APT package repository as a "Remote Repository" (caching proxy for a repository located on a remote server).

If i use the URL provided in Elasticsearch documentation to setup the remote repository i get HTTP ERROR 404 (this can be reproduced by simply using a browser and try to open: https://artifacts.elastic.co/packages/8.x/apt).

Experts from Artifactory say they can't setup the repo with this URL, and after some research in the web, i see some people refering to Elasticsearch repositories as "non browsable" because it doesn't generate the index files ... this explains the issue while trying to setup the caching proxy.

And so, what i want to know is if there's an URL or other alternative to set this up? or if anyone experienced this kind of issue? and how they overcome/workaround it?

Please note, i don't have any issues setting up the repo as explained in the ES documentation on a endpoint or system, but i do have a scenario where i can't set this up this way because the systems aren't able to reach the internet, but they are able to reach the Artifactory instance.

Thank you very much

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