Elasticsearch Debian Repository in error


(Benoit) #1

Hello,

The Debian repository URL from this page https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-repositories.html return a 404

$ curl -v https://packages.elastic.co/elasticsearch/2.x/debian
* Hostname was NOT found in DNS cache
*   Trying 107.22.226.93...
* Connected to packages.elastic.co (107.22.226.93) port 443 (#0)
* successfully set certificate verify locations:
*   CAfile: none
  CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server key exchange (12):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* Server certificate:
* 	 subject: C=US; ST=California; L=Mountain View; O=Elasticsearch, Inc.; CN=*.elastic.co
* 	 start date: 2016-01-18 00:00:00 GMT
* 	 expire date: 2019-03-27 12:00:00 GMT
* 	 subjectAltName: packages.elastic.co matched
* 	 issuer: C=US; O=DigiCert Inc; CN=DigiCert SHA2 Secure Server CA
* 	 SSL certificate verify ok.
> GET /elasticsearch/2.x/debian HTTP/1.1
> User-Agent: curl/7.38.0
> Host: packages.elastic.co
> Accept: */*
> 
< HTTP/1.1 404 Not Found
< Content-Type: application/xml
< Date: Tue, 18 Oct 2016 07:25:36 GMT
* Server nginx/1.4.6 (Ubuntu) is not blacklisted
< Server: nginx/1.4.6 (Ubuntu)
< x-amz-id-2: 6W6pXrn/puhCRzbHSsfFF6t+F8HvGq4olgaMg+DcpZN+TsWVyk0a0c3iuw8YdqsxmrNPXknuGxM=
< x-amz-request-id: 638A24AC90845849
< Content-Length: 295
< Connection: keep-alive
< 
<?xml version="1.0" encoding="UTF-8"?>
* Connection #0 to host packages.elastic.co left intact
<Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Key>elasticsearch/2.x/debian</Key><RequestId>638A24AC90845849</RequestId><HostId>6W6pXrn/puhCRzbHSsfFF6t+F8HvGq4olgaMg+DcpZN+TsWVyk0a0c3iuw8YdqsxmrNPXknuGxM=</HostId></Error>

Is it a temporary problem or the URL have changed ?

BenoƮt


(Mark Walkom) #2

It's not an error, we don't allow traversal/browsing of the URL.


(system) #3