<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Splunk Web Server SSL Access to Search Engine using v9.2.x in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Splunk-Web-Server-SSL-Access-to-Search-Engine-using-v9-2-x/m-p/693537#M14051</link>
    <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;There could be a few things going on here.&lt;/P&gt;&lt;P&gt;I would hazard a guess that you're running Splunk as a non-root user trying to bind to port 443 which is a privileged-port. Check if Splunk is listening on 443/TCP:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="bash"&gt;ss -tlp&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, check for web related messages under:&lt;/P&gt;&lt;P&gt;$SPLUNK_HOME/bin/splunk status&lt;BR /&gt;And&amp;nbsp;&lt;SPAN&gt;UiHttpListener&amp;nbsp;entries in /opt/splunk/var/log/splunk/splunkd.log.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;If this is indeed your problem, I suggest that you use different port such as 8443. You could also try to allow Splunk to bind to the system ports, you will need to &lt;A href="https://stackoverflow.com/questions/413807/is-there-a-way-for-non-root-processes-to-bind-to-privileged-ports-on-linux" target="_self"&gt;research how to do this securely for your environment&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;If Splunk is listening on 443, start working your way out:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Are there any error entries in splunkd.log.&lt;/LI&gt;&lt;LI&gt;Can you curl it via local host&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;curl -kv https://localhost​&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Are you dropping connections on the local FW?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;firewall-cmd --list-all&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Is there a routing issue / network firewall between your client browser and Splunk instance?&lt;/LI&gt;&lt;LI&gt;Is there an issue with client machine / browser?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Feel free to upload any relevant Splunkd.log entries, redacted appropriately to help troubleshooting.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 17 Jul 2024 00:29:58 GMT</pubDate>
    <dc:creator>Tom_Lundie</dc:creator>
    <dc:date>2024-07-17T00:29:58Z</dc:date>
    <item>
      <title>Splunk Web Server SSL Access to Search Engine using v9.2.x</title>
      <link>https://community.splunk.com/t5/Installation/Splunk-Web-Server-SSL-Access-to-Search-Engine-using-v9-2-x/m-p/693134#M14046</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have been working for a day or so on getting this to work.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here is my web.conf file configuration&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;[settings]
httpport = 443
loginBackgroundImageOption = custom
loginCustomBackgroundImage = search:logincustombg/Hub_Arial.jpg

enableSplunkWebSSL = true
privKeyPath = /opt/splunk/share/splunk/certs/decrypted-xxx_2025_wc.key
serverCert = /opt/splunk/share/splunk/certs/splunk-wc-xxx-com.pem&lt;/LI-CODE&gt;
&lt;P&gt;the key file is the decrypted certificate, the server cert is the server cert, the intermediate and root from godaddy g2.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am currently running splunk 9.2.x&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am not finding a quick how to to complete this task and I am working if someone could give me a hand.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am using Wireshark off the firefox browser and sometimes I see the client request but never see the server request.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am not doing this from the command line or the web server, I am updating the files and restarting splunkd.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance for your assistance.&amp;nbsp; Please let me know if there are any questions.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jul 2024 11:35:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Splunk-Web-Server-SSL-Access-to-Search-Engine-using-v9-2-x/m-p/693134#M14046</guid>
      <dc:creator>Ken_Taylor</dc:creator>
      <dc:date>2024-07-12T11:35:14Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Web Server SSL Access to Search Engine using v9.2.x</title>
      <link>https://community.splunk.com/t5/Installation/Splunk-Web-Server-SSL-Access-to-Search-Engine-using-v9-2-x/m-p/693537#M14051</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;There could be a few things going on here.&lt;/P&gt;&lt;P&gt;I would hazard a guess that you're running Splunk as a non-root user trying to bind to port 443 which is a privileged-port. Check if Splunk is listening on 443/TCP:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="bash"&gt;ss -tlp&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, check for web related messages under:&lt;/P&gt;&lt;P&gt;$SPLUNK_HOME/bin/splunk status&lt;BR /&gt;And&amp;nbsp;&lt;SPAN&gt;UiHttpListener&amp;nbsp;entries in /opt/splunk/var/log/splunk/splunkd.log.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;If this is indeed your problem, I suggest that you use different port such as 8443. You could also try to allow Splunk to bind to the system ports, you will need to &lt;A href="https://stackoverflow.com/questions/413807/is-there-a-way-for-non-root-processes-to-bind-to-privileged-ports-on-linux" target="_self"&gt;research how to do this securely for your environment&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;If Splunk is listening on 443, start working your way out:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Are there any error entries in splunkd.log.&lt;/LI&gt;&lt;LI&gt;Can you curl it via local host&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;curl -kv https://localhost​&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Are you dropping connections on the local FW?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;firewall-cmd --list-all&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Is there a routing issue / network firewall between your client browser and Splunk instance?&lt;/LI&gt;&lt;LI&gt;Is there an issue with client machine / browser?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Feel free to upload any relevant Splunkd.log entries, redacted appropriately to help troubleshooting.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jul 2024 00:29:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Splunk-Web-Server-SSL-Access-to-Search-Engine-using-v9-2-x/m-p/693537#M14051</guid>
      <dc:creator>Tom_Lundie</dc:creator>
      <dc:date>2024-07-17T00:29:58Z</dc:date>
    </item>
  </channel>
</rss>

