[SUPPORT|kbn_ent] https in 1.53.version

Hi,
I installed the ROR version
server01-client readonlyrest 1.53.0
But ssl stopped working for me. Have you changed anything?

[2023-12-13T19:18:54,835][ERROR][o.e.b.Bootstrap          ] [server01-client]Exception
java.lang.IllegalStateException: Unsupported http.type [ssl_netty4]

I don’t see any changes in the documentation.

elastic conf

cluster.name: cluster

node.name: ${HOSTNAME}-client
node.master: false
node.data: false
node.ingest: false
node.ml: false
xpack.ml.enabled: false
node.transform: false
node.remote_cluster_client: false
node.voting_only: false
 

path.data: /var/log/elasticsearch/data
path.logs: /var/log/elasticsearch-1

http.type: ssl_netty4

bootstrap.memory_lock: true

network.host: 0.0.0.0
http.port: 9201
transport.tcp.port: 9301

discovery.zen.ping.unicast.hosts: ['ip:9301', 'ip:9301', 'ip:9301']
discovery.zen.minimum_master_nodes: 2

xpack.security.enabled: false

PS.
I can’t create tickets in Enterprise support

An error occurred: You are not permitted to view the requested resource.

{“customer_id”: “6c4a385b-2ae8-4f02-a9cd-ef24addfb5b3”, “subscription_id”: “32d4073f-dc2f-4056-a868-842727c637cd”}

https transport doesn’t work too

[2023-12-13T19:51:07,697][ERROR][o.e.b.Bootstrap          ] [server01-client]Exception
java.lang.IllegalStateException: Unsupported transport.type [ror_ssl_internode]
	at org.elasticsearch.common.network.NetworkModule.getTransportSupplier(NetworkModule.java:201) ~[elasticsearch-7.15.1.jar:7.15.1]

Nope. There were no changes related to SSL. What ROR version did you have before the upgrade?

There was no ROR on this cluster.
I installed 1.49.1 where https works exactly and the error persists. I am surprised.
ElasticSeach, ROR and configuration are assembled by Ansible, so it is unlikely that the configs are different.

If remove the line http.type: ssl_netty4 then elasticsearch and the ROR plugin will start. This means the plugin was installed correctly.

full error

[2023-12-13T21:29:58,269][INFO ][o.e.t.NettyAllocator     ] [server01-client]creating NettyAllocator with the following configs: [name=elasticsearch_configured, chunk_size=1mb, suggested_max_allocation_size=1mb, factors={es.unsafe.use_netty_default_chunk_and_page_size=false, g1gc_enabled=false, g1gc_region_size=0b}]
[2023-12-13T21:29:58,299][ERROR][o.e.b.Bootstrap          ] [server01-client]Exception
java.lang.IllegalStateException: Unsupported http.type [ssl_netty4]
	at org.elasticsearch.common.network.NetworkModule.getHttpServerTransportSupplier(NetworkModule.java:187) ~[elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.node.Node.newHttpTransport(Node.java:1282) ~[elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.node.Node.<init>(Node.java:659) ~[elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.node.Node.<init>(Node.java:288) ~[elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:219) ~[elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:219) ~[elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:399) [elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:167) [elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:158) [elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:75) [elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:114) [elasticsearch-cli-7.15.1.jar:7.15.1]
	at org.elasticsearch.cli.Command.main(Command.java:79) [elasticsearch-cli-7.15.1.jar:7.15.1]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:123) [elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:81) [elasticsearch-7.15.1.jar:7.15.1]
[2023-12-13T21:29:58,303][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [server01-client]uncaught exception in thread [main]
org.elasticsearch.bootstrap.StartupException: java.lang.IllegalStateException: Unsupported http.type [ssl_netty4]
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:171) ~[elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:158) ~[elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:75) ~[elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:114) ~[elasticsearch-cli-7.15.1.jar:7.15.1]
	at org.elasticsearch.cli.Command.main(Command.java:79) ~[elasticsearch-cli-7.15.1.jar:7.15.1]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:123) ~[elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:81) ~[elasticsearch-7.15.1.jar:7.15.1]
Caused by: java.lang.IllegalStateException: Unsupported http.type [ssl_netty4]
	at org.elasticsearch.common.network.NetworkModule.getHttpServerTransportSupplier(NetworkModule.java:187) ~[elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.node.Node.newHttpTransport(Node.java:1282) ~[elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.node.Node.<init>(Node.java:659) ~[elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.node.Node.<init>(Node.java:288) ~[elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:219) ~[elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:219) ~[elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:399) ~[elasticsearch-7.15.1.jar:7.15.1]
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:167) ~[elasticsearch-7.15.1.jar:7.15.1]
	... 6 more

please show us your readonlyrest settings too

You were right. The ROR file was missing a section for SSL.

    ssl:
      enable: true
      keystore_file: "cert.p12"
      keystore_pass: pass
      key_pass: pass

But I was sure that the config was the same for all clusters.
Thanks for the help.

If possible, it might be worth making a more informative error.

yeah, we have to improve it.