Blomstra Search, an elasticsearch fulltext search extension

luceos

Shock no, we also use https in production. Just make sure your Elastic Endpoint setting uses that https url.

Shock

luceos It does.

When I query the service using the command from the ES docs, it works:

curl --cacert $ES_HOME/config/certs/http_ca.crt -u elastic:$ELASTIC_PASSWORD https://localhost:9200
yields
{ "name" : "node-1", "cluster_name" : "cluster-1", "cluster_uuid" : "jwMl-ycHSCiPyEwQKnAlyw", "version" : { "number" : "8.15.2", "build_flavor" : "default", "build_type" : "tar", "build_hash" : "98adf7bf6bb69b66ab95b761c9e5aadb0bb059a3", "build_date" : "2024-09-19T10:06:03.564235954Z", "build_snapshot" : false, "lucene_version" : "9.11.1", "minimum_wire_compatibility_version" : "7.17.0", "minimum_index_compatibility_version" : "7.0.0" }, "tagline" : "You Know, for Search" }

I have all the same settings set in flarum:

host: https://localhost:9200
username: elastic
password: <$ELASTIC_PASSWORD>
index: flarum-search

and yet when I run php flarum blomstra:search:index i get

In StaticNoPingConnectionPool.php line 64:
                                        
  No alive nodes found in your cluster

luceos

Shock then the server flarum runs as probably can't connect to the redis server. Is this dockerized?

maisen20

Shock I am pretty sure the problem is probably because you are using your self signed ssl cert. Therefore your CLI command works (because of the --cacert $ES_HOME/config/certs/http_ca.crt) but flarum cannot connect to elasticsearch.

I had the same problem but then changed the following in the file vendor/blomstra/search/src/Provider.php:

$builder = ClientBuilder::create()
                ->setHosts([$settings->get('blomstra-search.elastic-endpoint')])
                ->setSSLVerification(false); // disable cert verification

As soon as you deactivate ssl verification with '->setSSLVerification(false)', it works. At least for me.

@luceos Can you please add an option to the blomstra-search in the settings to set setSSLVerification to false using a checkbox? I know it's not the best practice in terms of security, but it would certainly help some people with debugging.

Shock

luceos redis server?

No it's not dockerized

luceos

Shock sorry I meant elastic 🙈

still it seems it cannot connect to the elastic instance at all

Shock

luceos any idea why? They are on the same server

luceos

Shock try the IP instead of the host: 127.0.0.1

Oshvam

I recently started looking into ZincSearch, it is a self-hosted alternative to ElasticSearch. I don't know if there would be an option to offer support for this in this add-on.

zincsearch/zincsearch?tab=readme-ov-file

Teddan

I got this error installing the extension even with the -W command:

o not run Composer as root/super user! See https://getcomposer.org/root for details
Continue as root/super user [yes]? 
./composer.json has been updated
Running composer update blomstra/search --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - blomstra/search[0.0.1, ..., 0.1.19] require elasticsearch/elasticsearch 7.* -> satisfiable by elasticsearch/elasticsearch[v7.0.0, ..., v7.17.2].
    - elasticsearch/elasticsearch[v7.11.0, ..., v7.17.2] require ezimuel/ringphp ^1.1.2 -> satisfiable by ezimuel/ringphp[1.1.2, 1.2.0, 1.2.1, 1.2.2].
    - ezimuel/ringphp[1.1.2, ..., 1.2.2] require react/promise ~2.0 -> found react/promise[v2.0.0, ..., v2.11.0] but these were not loaded, likely because it conflicts with another require.
    - elasticsearch/elasticsearch[v7.0.0, ..., v7.10.0] require php ^7.1 -> your php version (8.2.24) does not satisfy that requirement.
    - Root composer.json requires blomstra/search * -> satisfiable by blomstra/search[0.0.1, ..., 0.1.19].

luceos

maisen20 fastest would be providing a pull request. I'm currently too busy to tackle this.

maisen20

luceos I understand that. I've made a very simple extension for myself and when I activate it, setSSLVerification(false) is set and the connection to elasticsearch works.

« Previous Page