<?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: &amp;quot;Server Error&amp;quot; for a fresh Splunk install in Security</title>
    <link>https://community.splunk.com/t5/Security/quot-Server-Error-quot-for-a-fresh-Splunk-install/m-p/447288#M10478</link>
    <description>&lt;P&gt;@vytakas : Thank you sir. This is exactly what was blocking the connection to the Splunk server. &lt;/P&gt;</description>
    <pubDate>Thu, 09 May 2019 15:38:09 GMT</pubDate>
    <dc:creator>rahgovin</dc:creator>
    <dc:date>2019-05-09T15:38:09Z</dc:date>
    <item>
      <title>"Server Error" for a fresh Splunk install</title>
      <link>https://community.splunk.com/t5/Security/quot-Server-Error-quot-for-a-fresh-Splunk-install/m-p/447283#M10473</link>
      <description>&lt;P&gt;Installed a 7.2.4.2 instance on a new Ubuntu Server 18.0.4 VM . The installation went through ok and I set the admin username and password. I run into an issue once the splunk service is started. When I go to the web login page and use the newly created account, I get a "Server Error" message at the bottom of the screen. &lt;/P&gt;

&lt;P&gt;I tried the same install on an Ubuntu Desktop version with the same results as above. But then go to the web url using the http:127.0.0.1:8000 and the login works correctly. I change the setting to SSL and now I can login from my remote machine.&lt;/P&gt;

&lt;P&gt;I see the same behavior on Centos as well. Anyone seen this before? What logs can I look at to give me some more info on what 's causing the error?&lt;/P&gt;

&lt;P&gt;Thanks.&lt;/P&gt;

&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/6729iADCF54972142AF6A/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 16 Mar 2019 18:01:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/quot-Server-Error-quot-for-a-fresh-Splunk-install/m-p/447283#M10473</guid>
      <dc:creator>rahgovin</dc:creator>
      <dc:date>2019-03-16T18:01:47Z</dc:date>
    </item>
    <item>
      <title>Re: "Server Error" for a fresh Splunk install</title>
      <link>https://community.splunk.com/t5/Security/quot-Server-Error-quot-for-a-fresh-Splunk-install/m-p/447284#M10474</link>
      <description>&lt;P&gt;Any errors in the logfiles: splunkd.log, splunkd_access.log, web_service.log, web_access.log - or any other?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 23:42:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/quot-Server-Error-quot-for-a-fresh-Splunk-install/m-p/447284#M10474</guid>
      <dc:creator>rvany</dc:creator>
      <dc:date>2020-09-29T23:42:59Z</dc:date>
    </item>
    <item>
      <title>Re: "Server Error" for a fresh Splunk install</title>
      <link>https://community.splunk.com/t5/Security/quot-Server-Error-quot-for-a-fresh-Splunk-install/m-p/447285#M10475</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/168920"&gt;@rahgovin&lt;/a&gt; ,&lt;BR /&gt;
You can try some below workarounds:-&lt;BR /&gt;
1. Please look at splunkd.log file (located at $SPLUNK_HOME/var/log/splunk) for errors or warnings.&lt;BR /&gt;
2. Check for the management port &lt;STRONG&gt;mgmtHostPort = IP:port&lt;/STRONG&gt; in your web.conf. &lt;BR /&gt;
3. You can also clear the cache in SplunkWeb by calling the bump endpoint.  &lt;CODE&gt;https://mysplunkinstall/en-US/_bump&lt;/CODE&gt;(replace mysplunkinstall with the domain name of your Splunk install).&lt;BR /&gt;
4. Also, restart splunkd.&lt;BR /&gt;
5. At last, if nothing works for you can try to reinstall splunk.&lt;/P&gt;

&lt;P&gt;Hope it helps!&lt;BR /&gt;
Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 23:45:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/quot-Server-Error-quot-for-a-fresh-Splunk-install/m-p/447285#M10475</guid>
      <dc:creator>MoniM</dc:creator>
      <dc:date>2020-09-29T23:45:08Z</dc:date>
    </item>
    <item>
      <title>Re: "Server Error" for a fresh Splunk install</title>
      <link>https://community.splunk.com/t5/Security/quot-Server-Error-quot-for-a-fresh-Splunk-install/m-p/447286#M10476</link>
      <description>&lt;P&gt;After trial and error, I now feel that there is something in the path between my remote computer and the splunk web that is obfuscating the login request. When I send the initial login request un-encrypted on http port 8000, I see the "Server Error" warning. As soon as I enable https, I can login from the same machine without issues. Since the https page sends the login encrypted, whatever is in the path can no longer mess with it. I have not checked my IPS and Firewall logs yet, but pretty sure that one of them is causing the issue. I tried the remote login from another remote machine that bypasses them and can now login without https enabled. &lt;/P&gt;

&lt;P&gt;Planning to check the log and capture to see what the splunk side sees. Thanks everyone.&lt;/P&gt;</description>
      <pubDate>Sun, 17 Mar 2019 13:32:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/quot-Server-Error-quot-for-a-fresh-Splunk-install/m-p/447286#M10476</guid>
      <dc:creator>rahgovin</dc:creator>
      <dc:date>2019-03-17T13:32:48Z</dc:date>
    </item>
    <item>
      <title>Re: "Server Error" for a fresh Splunk install</title>
      <link>https://community.splunk.com/t5/Security/quot-Server-Error-quot-for-a-fresh-Splunk-install/m-p/447287#M10477</link>
      <description>&lt;P&gt;In may case it was Bidefender online threat prevention what blocked connection without notification: "An attempt to send your password unencrypted was about to occur on 192.168.xx.xx:8000. We blocked the connection to stop your private data from being exposed and tampered with" Need to add exeption.,In my case it was Bitdefender firewal what bloked conn without any notification: "An attempt to send your password unencrypted was about to occur on 192.168.xxx:8000. We blocked the connection to stop your private data from being exposed and tampered with.&lt;BR /&gt;
Add to exceptions"&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2019 14:17:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/quot-Server-Error-quot-for-a-fresh-Splunk-install/m-p/447287#M10477</guid>
      <dc:creator>vytakas</dc:creator>
      <dc:date>2019-05-09T14:17:23Z</dc:date>
    </item>
    <item>
      <title>Re: "Server Error" for a fresh Splunk install</title>
      <link>https://community.splunk.com/t5/Security/quot-Server-Error-quot-for-a-fresh-Splunk-install/m-p/447288#M10478</link>
      <description>&lt;P&gt;@vytakas : Thank you sir. This is exactly what was blocking the connection to the Splunk server. &lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2019 15:38:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/quot-Server-Error-quot-for-a-fresh-Splunk-install/m-p/447288#M10478</guid>
      <dc:creator>rahgovin</dc:creator>
      <dc:date>2019-05-09T15:38:09Z</dc:date>
    </item>
    <item>
      <title>Re: "Server Error" for a fresh Splunk install</title>
      <link>https://community.splunk.com/t5/Security/quot-Server-Error-quot-for-a-fresh-Splunk-install/m-p/447289#M10479</link>
      <description>&lt;P&gt;Exact same issue for; BitDefender&lt;/P&gt;</description>
      <pubDate>Sat, 31 Aug 2019 01:38:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/quot-Server-Error-quot-for-a-fresh-Splunk-install/m-p/447289#M10479</guid>
      <dc:creator>clhall1</dc:creator>
      <dc:date>2019-08-31T01:38:40Z</dc:date>
    </item>
  </channel>
</rss>

