I am currently facing an issue accessing the Splunk Web interface over HTTPS. When I configure enableSplunkWebSSL = true in web.conf, the Splunk Web service appears to start normally, and the port 8000 is open. However, users are unable to reach the interface via the public IP using HTTPS. When I change the configuration to enableSplunkWebSSL = false, and use HTTP instead, everything works fine — users can successfully access the Splunk Web interface on the public IP and port 8000. Additional details: There is full network connectivity; telnet to the public IP and port 8000 works. The issue is reproducible across different browsers and devices. The certificate used is the default self-signed certificate provided by Splunk. The Splunk Web service log does not show any fatal errors. I need to maintain HTTPS access for security compliance. Could you please assist in identifying the root cause and provide guidance on how to ensure HTTPS access works properly over the public IP?   ... View more