Hi,
I am not able to deploy a process from Desktop modeler to Docker setup. I have a docker setup on a linux box and have exposed 26500 port by reverse proxy. The proxy url is like https://mydomain.xxx.yyy.com/ I am getting this error in the Modeler log
Error: 14 UNAVAILABLE: No connection established. Last error: 33638144:error:10000103:SSL routines:OPENSSL_internal:INVALID_ALPN_PROTOCOL:…..\third_party\boringssl\src\ssl\extensions.cc:1436:
Hi @priyaprabhu - usually INVALID_ALPN_PROTOCOL errors are due to the gRPC API requiring HTTP/2, but your ingress/proxy/firewall/etc isn’t configured to allow HTTP/2 traffic.
Hi Nathan. Firewall changes were not working. We exposed the port directly.though it shows error in the modeler, the model was deployed in the background
I’m not a network engineer, so I’m not entirely certain. HTTP/2 uses ALPN to negotiate the connection, and the gRPC gateway requires HTTP/2. If you search the forums there are a few reports of ALPN negotiation errors (example) and all were network related issues. Because it’s HTTP/2, just exposing the port may not be enough, but it is strange that you’re seeing the deployed process.