ES 2.2 Elasticsearch Version: 8.0.0

Chris D

XenForo developer
Staff member
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)
 

Nirjonadda

Well-known member
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.

ScreenShot00472.png

But enhanced search can not made connect:

ScreenShot00473.png

Also Use HTTPS connection have server error log:

ScreenShot00474.png
 

goyo

Member

Nirjonadda

Well-known member
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?

Code:
# 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

Member
Do we need disabled all security features?

Code:
# 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.


.
 

gerryvz

Well-known member
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ş

Well-known member
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.
 
Top