• Installed and indexed. When searching on the frontend, we just get an error from Guzzle:

    Fatal error: Uncaught exception ‘Guzzle\Http\Exception\ClientErrorResponseException’ with message ‘Client error response [status code] 400 [reason phrase] Bad Request [url] https://127.0.0.1:9200/boltons-1/post/_search’ in /home/boltons/public_html/wp-content/plugins/elasticsearch-indexer/vendor/guzzle/guzzle/src/Guzzle/Http/Exception/BadResponseException.php:43 Stack trace: #0 /home/boltons/public_html/wp-content/plugins/elasticsearch-indexer/vendor/guzzle/guzzle/src/Guzzle/Http/Message/Request.php(145): Guzzle\Http\Exception\BadResponseException::factory(Object(Guzzle\Http\Message\EntityEnclosingRequest), Object(Guzzle\Http\Message\Response)) #1 [internal function]: Guzzle\Http\Message\Request::onRequestError(Object(Guzzle\Common\Event), ‘request.error’, Object(Symfony\Component\EventDispatcher\EventDispatcher)) #2 /home/boltons/public_html/wp-content/plugins/elasticsearch-indexer/vendor/symfony/event-dispatcher/EventDispatcher.php(164): call_user_func(Array, Object(Guzzle\Common\Event), ‘request.error’, Object(Symfony\C in /home/boltons/public_html/wp-content/plugins/elasticsearch-indexer/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/GuzzleConnection.php on line 277

    https://www.ads-software.com/plugins/elasticsearch-indexer/

  • The topic ‘Guzzle error on searching’ is closed to new replies.