Hi @emoteek ,
Per our pinned post on this support forum, we provide all support through Github. You can file issues at https://github.com/10up/ElasticPress.
In order to confirm that self-hosted connections are working, I did the following:
Set up a free trial account on Elastic.co with all default options (IO optimized, basic VMs, etc)
Enter URL for Elasticsearch from value copied in Elastic.co dashboard into WP/ElasticPress settings page
Confirm 401 response (expected as credentials have not been entered)
Set ES_SHIELD value as username:password based on values pasted from Elastic.co dashboard
Run a successful index.
Perform a test search on the front end, confirm I get a 200 result from my Elastic.co endpoint
While Elasticsearch does have a lot of options, this can cause confusion when trying to set up a self-hosted connection. While we do support the plugin side of a self-hosted solution, I do caution you that setup and maintenance of these servers can be quite difficult, which is why we built a service around this (ElasticPress.io) in the first place.
Again, we will 100% stand behind our plugin and fix any bugs that exist in the plugin, but we cannot provide troubleshooting for individual connectivity issues with self-hosted solutions through Github or this forum. We do, however, provide custom consulting if you need to use a specific solution such as Elastic.co or another self-hosted solution like AWS Elasticsearch Service.
