Unsupported http.type ssl_netty4 with ES 7.8.0-1

After upgrading from elasticsearch 7.6.2 to 7.8.0 and upgrading ROR 1.20.0 for ES7.6.2 to ROR 1.22.1 for 7.8.0, elastic won’t start and complains of unsupported http.type ssl_netty4

do you have a stacktrace?

I’m not able to copy the full stack trace but can provide some of it here by typing it. I hope this can provide you with enough clues. :slight_smile:

org.elasdticsearch.bootstrap.StartupException: java.lang.IllegalStateExcpetion: Unsupported http.type {ssl_netty4]
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:174) ~[elasticsearch-7.8.0.jar:7.8.0]
at org.elasticsearch.bootstraap.Elasticsearch.execute(Elasticsearch.java:161) ~[elasticsearch-7.8.0.jar:7.8.0]

Caused by: java.lang.IllegalStateException: Unsupported http.type [ss_netty4]
at org.elasticsearch.common.network.NetworkModule.getHttpServerTransportSupplier(NetworkModuel.java:198) ~[elasticsearch-7.8.0.jar:7.8.0]
at org.elasticsearch.node.Node.newHttpTransport(Node.java:1095)

Just to be sure? this is not a typo?

Yeah looks like a typo in elasticsearch.yml: it should be “ssl_netty4”
@coutoPL in an ideal world, we would not require that configuration change, and when SSL is enabled in readonlyrest,yml Elasticsearch should use ROR’s HTTP type “ssl_netty4”.

I never took the time to investigate how to do this. Should add to Jira?

Rhonda (@rgregory) responded via email:

My elasticsearch.yml has:
http.type: ssl_netty4

and elasticsearch throws an error. The typo was my handtyped stack trace. Our implementation lives in an air-gapped network so I can not easily share stack traces

ok, added to backlog

@rgregory the only situation where ssl_netty4 http type would not be recognised by ES, as far as I can guess are:

  1. ROR Is not installed, so please double check it installed correctly.
  2. “xpack.security.enabled: false” is not present in elasticsearch.yml