To create, setup, and connect to your Elastisearch index, or just connect to your existing index, you will setup a connection to the index as seen in the following screen.

Connect to your new or existing Elasticsearch index
Click on the button “”Connect to your Elasticsearch / Apache Solr”, to open the connection setup parameters.

Here are the steps:
- Open the Elasticsearch index parameters
- Select the type of index you’re connecting too (“Elasticsearch” here)
- Give a name to your index. It’s just for wpsolr, it does not need to be related to your index real name. Like “dev index”, “stage site.com”, “prod do not delete”
- Real name of your index in your Elasticsearch server (no whitespace, no special characters).
- Choose if your index is protected with https or not (it should!)
- This is the host name of your Elasticsearch server. Like localhost, www.mysite.com, subsite.mysite.com
- The port of your Elasticsearch server. 9200 is the default, or 443 with https.
- If your Elasticsearch uses Basic HTTP authentication (it should!), this is the “user”
- If your Elasticsearch uses Basic HTTP authentication (it should!), this is the “Password”
- This button verifies your connection (by pinging the index) and saves it if it’s fine. A green icon will be shown briefly if the connection is fine. Else, error messages in red appear.
Remove or update your Elasticsearch index connection

After creating your connection, you can either:
- Create another one
- Change it’s parameters or check that it is still alive
- Remove the connection from wpsolr. It does not delete the index from Elasticsearch: it just removes the connection from wpsolr’s connections list.
Common error messages
No handler for type [keyword] declared on field [id]
Your Elasticsearch version is 2.x. WPSOLR requires a 5.x version, with the mapper attachment plugin.
Couldn't resolve host
Your host name does not exist, probably because of a typing mistake. Ensure there is not http, not :, not // in the host name.
no such index [index: bad-request]
The index name contains unsupported characters, like white spaces. Or the index is in bad shape: verify the error messages in your Elasticsearch logs.
Couldn't connect to host, Elasticsearch down?
The Elastisearch server is down: verify that you can access it’s admin UI with this port. Or your WordPress hosting company blocks all outgoing ports, but 80 and 443: ensure your Elasticsearch uses one of those ports.