ES throws 404 File or directory not found

Hi, We recently saw a customer report indexing failures with 404 File or directory not found.
This is happening in ES version 5.6.

Any help here what is contributing to this failure ?

Details present in the response :

Raw response: [<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "">< html xmlns="">< head>< meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>< title>404 - File or directory not found.</title>< style type="text/css">< !-- body{margin:0;font-size:.7em;font-family:Verdana, Arial, Helvetica, sans-serif;background:#EEEEEE;} fieldset{padding:0 15px 10px 15px;} h1{font-size:2.4em;margin:0;color:#FFF;} h2{font-size:1.7em;margin:0;color:#CC0000;} h3{font-size:1.2em;margin:10px 0 0 0;color:#000000;} #header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"trebuchet MS", Verdana, sans-serif;color:#FFF; background-color:#555555;} #content{margin:0 0 0 2%;position:relative;} .content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;} --></style>< /head>< body>< div id="header"><h1>Server Error</h1></div>< div id="content"> <div class="content-container"><fieldset> <h2>404 - File or directory not found.</h2> <h3>The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.</h3> </fieldset></div>< /div>< /body>< /html> ] ]

Thanks, Divya


Elasticsearch only returns JSON as its response, so this HTML must not have been sent by Elasticsearch.

Can you explain what request you sent to Elasticsearch (if you sent it to Elasticsearch directly) and which response you expected, where your systems are running, etc?


The request sent was bulk index call. The call is sent to ES thru NEST. The version of NEST being used is 2.3.3. We were expecting a normal bulk response(as you say the JSON) with maybe more relevant exception info. But this is the first time, a HTML embedded response was encountered.

is there a proxy in front of the host you are trying to query? Can you paste the response of the / endpoint here? I am pretty sure there is another component in between (like a proxy) or you are not querying an Elasticsearch endpoint.

Alex, you are right. The customer has setup a reverse proxy where he mapped a url like http://machinename:9200 to

What could this have done to the request ?

this is something you have to check out within the reverse proxy. Maybe not being able to reach ES might trigger this - which is easy to test by just shutting down ES and sending a request.

Thanks for the prompt clarification. Let me try the suggestion and get back.

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