We have our load balancer not supported https url for camunda.client.zeebe.grpc-address currently. In this case can we use only camunda.client.zeebe.rest-address?
Also if we configure only camunda.client.zeebe.rest-address it is getting redirected to localhost url with error as below:
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: getsockopt: /0.0.0.0:26500
Caused by: java.net.ConnectException: Connection refused: getsockopt
@ssmahanta - I’m not quite sure I understand the question - seems like there’s 2-3 questions here.
- the 8.8 release should bring the REST API to parity with the gRPC API, so can you use whichever better suits your environment and development workflows
- HTTPS is not strictly required, but it is, of course, a best practice
- the redirect to 0.0.0.0:26500 looks very strange, because port 26500 is the gRPC port, not the REST API port. How did you configure this, how are you trying to call the API, and where are you seeing that error?
1 Like