teodorkostov opened a new issue, #14079:
URL: https://github.com/apache/apisix/issues/14079

   ### Description
   
   I have the following config:
   
   ```
   apisix:
     enable_admin: false
     enable_control: false
     enable_ipv6: false
     node_listen: 80
     router:
       http: radixtree_host_uri
       ssl: radixtree_sni
     ssl:
       enable: true
       listen:
         - port: 443
           enable_http3: true
       ssl_protocols: TLSv1.3
       ssl_trusted_certificate: /config/ca.pem
   
   deployment:
     role: data_plane
     role_data_plane:
       config_provider: yaml
   
   plugin_attr:
     redirect:
       https_port: 443
   
   #END
   ```
   
   I see regular requests from 127.0.0.1. The traffic originates from within 
the container. I believe this is some kind of healthcheck to the Control API or 
the Admin API that are disabled.
   
   Here is the log message:
   
   ```[error] 81#81: *308794 [lua] init.lua:218: ssl_client_hello_phase(): 
failed to find SNI: please check if the client requests via IP or uses an 
outdated protocol. If you need to report an issue, provide a packet capture 
file of the TLS handshake., context: ssl_client_hello_by_lua*, client: 
127.0.0.1, server: 0.0.0.0:443
   ```
   
   How can I disable this healthcheck?
   
   ### Environment
   
   - APISIX version (run `apisix version`): 3.19.0-redhat
   - Operating system (run `uname -a`): docker
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`): NA
   - etcd version, if relevant (run `curl 
http://127.0.0.1:9090/v1/server_info`): NA
   - APISIX Dashboard version, if relevant: NA
   - Plugin runner version, for issues related to plugin runners: NA
   - LuaRocks version, for installation issues (run `luarocks --version`): NA
   


-- 
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