ES 2.2 Elasticsearch Version: 8.0.0

[Nirjonadda]

Enhanced Search 2.2.2 not compatible with Elasticsearch Version: 8.0.0?

 

[Chris D]

Not really something we've had an opportunity to test yet, given it was only released yesterday.

Are you telling us it's not compatible? (if so, we'd need more info) or are you asking us is it compatible? (if so, I have no idea)

 

[duderuud]

Good to know, will test it out on my staging server (with latest XF version).

 

[Nirjonadda]

Not really something we've had an opportunity to test yet, given it was only released yesterday.

Are you telling us it's not compatible? (if so, we'd need more info) or are you asking us is it compatible? (if so, I have no idea)

I am asked for support or bug because I can not use enhanced search after upgraded to Version: 8.0.0.

Elasticsearch server is running.



But enhanced search can not made connect:



Also Use HTTPS connection have server error log:

 

[Chris D]

Recommendation would be to use Elasticsearch 7.x until such a time we add support for 8.x.

 

[goyo]

I am asked for support or bug because I can not use enhanced search after upgraded to Version: 8.0.0.

Elasticsearch server is running.

View attachment 264676

But enhanced search can not made connect:

View attachment 264677

Also Use HTTPS connection have server error log:

View attachment 264678

In case you are fine with disabling its security features (options in elasticsearch.yml under "# Enable security features"),
version 8 should work just fine.

 

[Nirjonadda]

In case you are fine with disabling its security features (options in elasticsearch.yml under "# Enable security features"),
version 8 should work just fine.

Do we need disabled all security features?

# Enable security features
xpack.security.enabled: true

xpack.security.enrollment.enabled: true

# Enable encryption for HTTP API client connections, such as Kibana, Logstash, and Agents
xpack.security.http.ssl:
  enabled: true
  keystore.path: certs/http.p12

# Enable encryption and mutual authentication between cluster nodes
xpack.security.transport.ssl:
  enabled: true
  verification_mode: certificate
  keystore.path: certs/transport.p12
  truststore.path: certs/transport.p12

 

[goyo]

Do we need disabled all security features?

# Enable security features
xpack.security.enabled: true

xpack.security.enrollment.enabled: true

# Enable encryption for HTTP API client connections, such as Kibana, Logstash, and Agents
xpack.security.http.ssl:
  enabled: true
  keystore.path: certs/http.p12

# Enable encryption and mutual authentication between cluster nodes
xpack.security.transport.ssl:
  enabled: true
  verification_mode: certificate
  keystore.path: certs/transport.p12
  truststore.path: certs/transport.p12

Dear @Nirjonadda ,

I just disabled all of them.

As I solely use in localhost for XF (and XF seems safe enough ) single-node and ES's 9200 port blocked from outside with a firewall, I guess it should be adequately secure if your system is safe otherwise.

Please note I'm not a security guru, and constant new vulnerabilities are now the default way of living (thankfully Elasticsearch ≥ 7.16.3 is not vulnerable to Log4j / Log4Shell).

If someone has more security knowledge or Elasticsearch localhost specific incidents, please feel free to add your point of view.


.

 

[Frode789]

Following this to see when ES 8 support is added.

 

[phucvandinh]

Just switch true to false and don't use HTTPS is enough.

xpack.security.http.ssl:
  enabled: true
  keystore.path: certs/http.p12

 

[duderuud]

Also got ES 8(.1.2) working with credentials needed for the certificate. So far so good.

 

[Recep Baltaş]

OK, got 8.2 running but would be nice to configure it with security enabled.

 

[gerryvz]

Any official updates from XenForo Development as to whether / when Elasticsearch 8.x is officially supported?

Also one question - why does official ES support go all the way back to version 2.x? Why not advance the ES minimum version supported like with PHP, databases, and so forth? Does ES 2.x essentially do the same things that the current 7.X and 8.X do?

 

[Recep Baltaş]

Any official updates from XenForo Development as to whether / when Elasticsearch 8.x is officially supported?

Also one question - why does official ES support go all the way back to version 2.x? Why not advance the ES minimum version supported like with PHP, databases, and so forth? Does ES 2.x essentially do the same things that the current 7.X and 8.X do?

I believe this will be a 2.3 thing.

 

[Mouth]

ElasticSearch 8.x was released 9 months ago, is there sill no official support from Xf?

 

[phucvandinh]

ElasticSearch 8.x was released 9 months ago, is there sill no official support from Xf?

It's working properly, just need to disable new security measures introduced in ES8

 

[Recep Baltaş]

It's working properly, just need to disable new security measures introduced in ES8

That's not the point but I'm sure it'll be a feature of XenForo 2.3

 

[Marcus]

This is the quickest way to make Elasticsearch 8.x compatible with xenforo (one line change in the elasticsearch main configuration file): https://xenforo.com/community/resources/elasticsearch-8-x-compatibility-fix.8976/

Yes, it does deactivate the 8.x new security features but these are not available anyway in 7.x

 

[Nirjonadda]

@Chris D Please any update for this issues?

 

[Recep Baltaş]

@Chris D I haven't seen any update ragarding this in XF 2.3 HYSs. Is there going to be a seperate HYS for Ehanced Search?