anilaws opened a new issue, #2092:
URL: https://github.com/apache/apisix-ingress-controller/issues/2092

   ### Description
   
   followed https://apisix.apache.org/docs/ingress-controller/deployments/aws/ 
and deployed apisix gateway using NLB on EKS. 
   http://apsisix-gateway-url/ works fine.
   I have enabled tls on gateway and when i try https://apsisix-gateway-url/ , 
i am getting error 
   OpenSSL/3.0.8: error:0A000438:SSL routines::tlsv1 alert internal error
   
   I even tried hitting the gateway service without the load balancer URL from 
one of the pods inside the cluster
    curl -kv https://apisix-gateway.ingress-apisix.svc.cluster.local/headers -H 
'Host: local.httpbin.org'
   *   Trying 172.20.168.24:443...
   * Connected to apisix-gateway.ingress-apisix.svc.cluster.local 
(172.20.168.24) port 443 (#0)
   * ALPN: offers h2,http/1.1
   * TLSv1.3 (OUT), TLS handshake, Client hello (1):
   * TLSv1.3 (IN), TLS alert, internal error (592):
   * OpenSSL/3.0.8: error:0A000438:SSL routines::tlsv1 alert internal error
   * Closing connection 0
   curl: (35) OpenSSL/3.0.8: error:0A000438:SSL routines::tlsv1 alert internal 
error
   
   ### Environment
   
   - APISIX version (run `apisix version`): 3.2.0
   - Operating system (run `uname -a`):  Linux apisix-6bfbd9c7cb-jjvql 
5.15.93-55.139.amzn2.x86_64 apache/apisix#1 SMP Tue Feb 14 21:47:11 UTC 2023 
x86_64 GNU/Linux
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`): nginx 
version: openresty/1.21.4.1
   - etcd version, if relevant (run `curl 
http://127.0.0.1:9090/v1/server_info`):
   - APISIX Dashboard version, if relevant:
   - Plugin runner version, for issues related to plugin runners:
   - LuaRocks version, for installation issues (run `luarocks --version`):
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to