<?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: App Upgrade GUI in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/App-Upgrade-GUI-Getting-internal-server-error/m-p/643673#M16358</link>
    <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;I will be putting this reply to the posts that I can find.&amp;nbsp; I know it's a late reply to some. But hope this will help you all.&amp;nbsp; And anyone having similar issues in the future.&lt;BR /&gt;&lt;BR /&gt;The issue I will be discussing here is when Splunk update does NOT update from Splunk Web. And when you search for the error you find similar to this:&lt;BR /&gt;&lt;EM&gt;splunk.ResourceNotFound:&amp;nbsp;[HTTP&amp;nbsp;404]&lt;BR /&gt;&lt;/EM&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Explanation on how really it works:&lt;/P&gt;&lt;P&gt;When you try to update the app Splunk Web makes a call to itself 127.0.0.1 on port 8089 for SplunkD&amp;nbsp;&amp;nbsp; at /services/apps/remote/entriesbyid/&amp;lt;your_app&amp;gt; e.g. -&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;A href="https://127.0.0.1:8089/services/apps/remote/entriesbyid/Splunk_TA_windows" target="_blank"&gt;https://127.0.0.1:8089/services/apps/remote/entriesbyid/Splunk_TA_windows&lt;/A&gt;&lt;/P&gt;&lt;P&gt;which you can check yourself by simple CURL:&lt;/P&gt;&lt;P&gt;curl -k --user "admin:changeme" &lt;A href="https://127.0.0.1:8089/services/apps/remote/entriesbyid/Splunk_TA_windows" target="_blank"&gt;https://127.0.0.1:8089/services/apps/remote/entriesbyid/Splunk_TA_windows&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This call is getting proxied via SplunkD process to the internet which would end up calling&amp;nbsp; &lt;A href="https://splunkbase.splunk.com/api/apps/entriesbyid/%3cyour_app%3e" target="_blank"&gt;https://splunkbase.splunk.com/api/apps/entriesbyid/&amp;lt;your_app&amp;gt;&lt;/A&gt;&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;which you can check yourself by simple CURL:&lt;/P&gt;&lt;P&gt;curl -k&amp;nbsp; &lt;A href="https://splunkbase.splunk.com/api/apps/entriesbyid/Splunk_TA_windows" target="_blank"&gt;https://splunkbase.splunk.com/api/apps/entriesbyid/Splunk_TA_windows&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now the issues here can be numerous from here on. To give some examples:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Splunk has issues accessing internet from SplunkD process&lt;/LI&gt;&lt;LI&gt;Certificate chain was changed. By default it is configured in server.conf&lt;BR /&gt;[applicationsManagement]&lt;BR /&gt;sslVerifyServerCert = false&lt;/LI&gt;&lt;LI&gt;Proxy and/or Firewall in the middle which is changing certificates.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;One of the ways you can check for networking issues for that is do a tcpdump for packet capture and check the SSL Conversation:&lt;BR /&gt;tcpdump -i &amp;lt;interface&amp;gt; -s 65535 port 443 -w /tmp/port443.pcap&lt;BR /&gt;&lt;BR /&gt;That's for people who are familiar what packet capture looks like and can understand it's contents.&lt;/P&gt;</description>
    <pubDate>Wed, 17 May 2023 15:50:44 GMT</pubDate>
    <dc:creator>dtsariapkin</dc:creator>
    <dc:date>2023-05-17T15:50:44Z</dc:date>
    <item>
      <title>App Upgrade GUI- Getting internal server error?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/App-Upgrade-GUI-Getting-internal-server-error/m-p/610561#M13713</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;
&lt;P&gt;When I visit the Apps page on my search head server and select "Upgrade to ..." on any of my applications that require an upgrade I get the following 500 Inernal Server Error:&amp;nbsp;/opt/splunk/var/log/splunk/web_service.log&lt;/P&gt;
&lt;P&gt;2022-08-23 21:11:36,576 ERROR [63054287cc7fe2c82754d0] error:335 - Traceback (most recent call last):&lt;BR /&gt;File "/opt/splunk/lib/python3.7/site-packages/cherrypy/_cprequest.py", line 628, in respond&lt;BR /&gt;self._do_respond(path_info)&lt;BR /&gt;File "/opt/splunk/lib/python3.7/site-packages/cherrypy/_cprequest.py", line 687, in _do_respond&lt;BR /&gt;response.body = self.handler()&lt;BR /&gt;File "/opt/splunk/lib/python3.7/site-packages/cherrypy/lib/encoding.py", line 219, in __call__&lt;BR /&gt;self.body = self.oldhandler(*args, **kwargs)&lt;BR /&gt;File "/opt/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/lib/htmlinjectiontoolfactory.py", line 75, in wrapper&lt;BR /&gt;resp = handler(*args, **kwargs)&lt;BR /&gt;File "/opt/splunk/lib/python3.7/site-packages/cherrypy/_cpdispatch.py", line 54, in __call__&lt;BR /&gt;return self.callable(*self.args, **self.kwargs)&lt;BR /&gt;File "/opt/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/lib/routes.py", line 383, in default&lt;BR /&gt;return route.target(self, **kw)&lt;BR /&gt;File "&amp;amp;lt;/opt/splunk/lib/python3.7/site-packages/decorator.py:decorator-gen-98&amp;amp;gt;", line 2, in start&lt;BR /&gt;File "/opt/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/lib/decorators.py", line 40, in rundecs&lt;BR /&gt;return fn(*a, **kw)&lt;BR /&gt;File "&amp;amp;lt;/opt/splunk/lib/python3.7/site-packages/decorator.py:decorator-gen-96&amp;amp;gt;", line 2, in start&lt;BR /&gt;File "/opt/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/lib/decorators.py", line 118, in check&lt;BR /&gt;return fn(self, *a, **kw)&lt;BR /&gt;File "&amp;amp;lt;/opt/splunk/lib/python3.7/site-packages/decorator.py:decorator-gen-95&amp;amp;gt;", line 2, in start&lt;BR /&gt;File "/opt/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/lib/decorators.py", line 166, in validate_ip&lt;BR /&gt;return fn(self, *a, **kw)&lt;BR /&gt;File "&amp;amp;lt;/opt/splunk/lib/python3.7/site-packages/decorator.py:decorator-gen-94&amp;amp;gt;", line 2, in start&lt;BR /&gt;File "/opt/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/lib/decorators.py", line 245, in preform_sso_check&lt;BR /&gt;return fn(self, *a, **kw)&lt;BR /&gt;File "&amp;amp;lt;/opt/splunk/lib/python3.7/site-packages/decorator.py:decorator-gen-93&amp;amp;gt;", line 2, in start&lt;BR /&gt;File "/opt/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/lib/decorators.py", line 284, in check_login&lt;BR /&gt;return fn(self, *a, **kw)&lt;BR /&gt;File "&amp;amp;lt;/opt/splunk/lib/python3.7/site-packages/decorator.py:decorator-gen-92&amp;amp;gt;", line 2, in start&lt;BR /&gt;File "/opt/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/lib/decorators.py", line 304, in handle_exceptions&lt;BR /&gt;return fn(self, *a, **kw)&lt;BR /&gt;File "/opt/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/controllers/appinstall.py", line 232, in start&lt;BR /&gt;remote_app = self.getRemoteAppEntry(appid);&lt;BR /&gt;File "/opt/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/controllers/appinstall.py", line 106, in getRemoteAppEntry&lt;BR /&gt;return en.getEntity('/apps/remote/entriesbyid', sbAppId)&lt;BR /&gt;File "/opt/splunk/lib/python3.7/site-packages/splunk/entity.py", line 277, in getEntity&lt;BR /&gt;serverResponse, serverContent = rest.simpleRequest(uri, getargs=kwargs, sessionKey=sessionKey, raiseAllErrors=True)&lt;BR /&gt;File "/opt/splunk/lib/python3.7/site-packages/splunk/rest/__init__.py", line 655, in simpleRequest&lt;BR /&gt;raise splunk.ResourceNotFound(uri)&lt;BR /&gt;splunk.ResourceNotFound: [HTTP 404] &lt;A href="https://127.0.0.1:8089/services/apps/remote/entriesbyid/treeview-viz" target="_blank" rel="noopener"&gt;https://127.0.0.1:8089/services/apps/remote/entriesbyid/treeview-viz&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;This happens on any application I try to upgrade via the GUI - I can upgrade them ok when doing it manually or by uploading the tgz archive.&lt;/P&gt;
&lt;P&gt;I can use the GUI just fine on any other server (Index/Heavy Forwarder).&lt;/P&gt;
&lt;P&gt;Does anyone know what could be causing this? Any help would be appreciated.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Oct 2022 14:25:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/App-Upgrade-GUI-Getting-internal-server-error/m-p/610561#M13713</guid>
      <dc:creator>pglover</dc:creator>
      <dc:date>2022-10-21T14:25:25Z</dc:date>
    </item>
    <item>
      <title>Re: App Upgrade GUI</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/App-Upgrade-GUI-Getting-internal-server-error/m-p/617955#M14292</link>
      <description>&lt;P&gt;Hi, Did you find a solution to this? I am seeing the same thing on one of my lab machines.&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Oct 2022 09:13:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/App-Upgrade-GUI-Getting-internal-server-error/m-p/617955#M14292</guid>
      <dc:creator>markhill1</dc:creator>
      <dc:date>2022-10-21T09:13:38Z</dc:date>
    </item>
    <item>
      <title>Re: App Upgrade GUI- Getting internal server error?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/App-Upgrade-GUI-Getting-internal-server-error/m-p/620258#M14469</link>
      <description>&lt;P&gt;I am having the same problem on all splunk instances. Any help apreciated&lt;/P&gt;</description>
      <pubDate>Wed, 09 Nov 2022 11:52:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/App-Upgrade-GUI-Getting-internal-server-error/m-p/620258#M14469</guid>
      <dc:creator>Johnn</dc:creator>
      <dc:date>2022-11-09T11:52:34Z</dc:date>
    </item>
    <item>
      <title>Re: App Upgrade GUI</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/App-Upgrade-GUI-Getting-internal-server-error/m-p/620288#M14474</link>
      <description>&lt;P&gt;I haven't found a fix for this as yet unfortunately&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Nov 2022 14:21:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/App-Upgrade-GUI-Getting-internal-server-error/m-p/620288#M14474</guid>
      <dc:creator>pglover</dc:creator>
      <dc:date>2022-11-09T14:21:45Z</dc:date>
    </item>
    <item>
      <title>Re: App Upgrade GUI- Getting internal server error?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/App-Upgrade-GUI-Getting-internal-server-error/m-p/639111#M15969</link>
      <description>&lt;P&gt;Open a support ticket.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Apr 2023 23:04:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/App-Upgrade-GUI-Getting-internal-server-error/m-p/639111#M15969</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2023-04-06T23:04:46Z</dc:date>
    </item>
    <item>
      <title>Re: App Upgrade GUI</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/App-Upgrade-GUI-Getting-internal-server-error/m-p/643673#M16358</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;I will be putting this reply to the posts that I can find.&amp;nbsp; I know it's a late reply to some. But hope this will help you all.&amp;nbsp; And anyone having similar issues in the future.&lt;BR /&gt;&lt;BR /&gt;The issue I will be discussing here is when Splunk update does NOT update from Splunk Web. And when you search for the error you find similar to this:&lt;BR /&gt;&lt;EM&gt;splunk.ResourceNotFound:&amp;nbsp;[HTTP&amp;nbsp;404]&lt;BR /&gt;&lt;/EM&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Explanation on how really it works:&lt;/P&gt;&lt;P&gt;When you try to update the app Splunk Web makes a call to itself 127.0.0.1 on port 8089 for SplunkD&amp;nbsp;&amp;nbsp; at /services/apps/remote/entriesbyid/&amp;lt;your_app&amp;gt; e.g. -&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;A href="https://127.0.0.1:8089/services/apps/remote/entriesbyid/Splunk_TA_windows" target="_blank"&gt;https://127.0.0.1:8089/services/apps/remote/entriesbyid/Splunk_TA_windows&lt;/A&gt;&lt;/P&gt;&lt;P&gt;which you can check yourself by simple CURL:&lt;/P&gt;&lt;P&gt;curl -k --user "admin:changeme" &lt;A href="https://127.0.0.1:8089/services/apps/remote/entriesbyid/Splunk_TA_windows" target="_blank"&gt;https://127.0.0.1:8089/services/apps/remote/entriesbyid/Splunk_TA_windows&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This call is getting proxied via SplunkD process to the internet which would end up calling&amp;nbsp; &lt;A href="https://splunkbase.splunk.com/api/apps/entriesbyid/%3cyour_app%3e" target="_blank"&gt;https://splunkbase.splunk.com/api/apps/entriesbyid/&amp;lt;your_app&amp;gt;&lt;/A&gt;&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;which you can check yourself by simple CURL:&lt;/P&gt;&lt;P&gt;curl -k&amp;nbsp; &lt;A href="https://splunkbase.splunk.com/api/apps/entriesbyid/Splunk_TA_windows" target="_blank"&gt;https://splunkbase.splunk.com/api/apps/entriesbyid/Splunk_TA_windows&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now the issues here can be numerous from here on. To give some examples:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Splunk has issues accessing internet from SplunkD process&lt;/LI&gt;&lt;LI&gt;Certificate chain was changed. By default it is configured in server.conf&lt;BR /&gt;[applicationsManagement]&lt;BR /&gt;sslVerifyServerCert = false&lt;/LI&gt;&lt;LI&gt;Proxy and/or Firewall in the middle which is changing certificates.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;One of the ways you can check for networking issues for that is do a tcpdump for packet capture and check the SSL Conversation:&lt;BR /&gt;tcpdump -i &amp;lt;interface&amp;gt; -s 65535 port 443 -w /tmp/port443.pcap&lt;BR /&gt;&lt;BR /&gt;That's for people who are familiar what packet capture looks like and can understand it's contents.&lt;/P&gt;</description>
      <pubDate>Wed, 17 May 2023 15:50:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/App-Upgrade-GUI-Getting-internal-server-error/m-p/643673#M16358</guid>
      <dc:creator>dtsariapkin</dc:creator>
      <dc:date>2023-05-17T15:50:44Z</dc:date>
    </item>
    <item>
      <title>Re: App Upgrade GUI- Getting internal server error?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/App-Upgrade-GUI-Getting-internal-server-error/m-p/643901#M16376</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I will be putting this reply to the posts that I can find.&amp;nbsp; I know it's a late reply to some. But hope this will help you all.&amp;nbsp; And anyone having similar issues in the future.&lt;BR /&gt;&lt;BR /&gt;The issue I will be discussing here is when Splunk update does NOT update from Splunk Web. And when you search for the error you find similar to this:&lt;BR /&gt;&lt;EM&gt;splunk.ResourceNotFound:&amp;nbsp;[HTTP&amp;nbsp;404]&lt;BR /&gt;&lt;/EM&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Explanation on how really it works:&lt;/P&gt;&lt;P&gt;When you try to update the app Splunk Web makes a call to itself 127.0.0.1 on port 8089 for SplunkD&amp;nbsp;&amp;nbsp; at /services/apps/remote/entriesbyid/&amp;lt;your_app&amp;gt; e.g. -&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;A href="https://127.0.0.1:8089/services/apps/remote/entriesbyid/Splunk_TA_windows" target="_blank" rel="nofollow noopener noreferrer"&gt;https://127.0.0.1:8089/services/apps/remote/entriesbyid/Splunk_TA_windows&lt;/A&gt;&lt;/P&gt;&lt;P&gt;which you can check yourself by simple CURL:&lt;/P&gt;&lt;P&gt;curl -k --user "admin:changeme"&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://127.0.0.1:8089/services/apps/remote/entriesbyid/Splunk_TA_windows" target="_blank" rel="nofollow noopener noreferrer"&gt;https://127.0.0.1:8089/services/apps/remote/entriesbyid/Splunk_TA_windows&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This call is getting proxied via SplunkD process to the internet which would end up calling&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://splunkbase.splunk.com/api/apps/entriesbyid/%3cyour_app%3e" target="_blank" rel="nofollow noopener noreferrer"&gt;https://splunkbase.splunk.com/api/apps/entriesbyid/&amp;lt;your_app&amp;gt;&lt;/A&gt;&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;which you can check yourself by simple CURL:&lt;/P&gt;&lt;P&gt;curl -k&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://splunkbase.splunk.com/api/apps/entriesbyid/Splunk_TA_windows" target="_blank" rel="nofollow noopener noreferrer"&gt;https://splunkbase.splunk.com/api/apps/entriesbyid/Splunk_TA_windows&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now the issues here can be numerous from here on. To give some examples:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Splunk has issues accessing internet from SplunkD process&lt;/LI&gt;&lt;LI&gt;Certificate chain was changed. By default it is configured in server.conf&lt;BR /&gt;[applicationsManagement]&lt;BR /&gt;sslVerifyServerCert = false&lt;/LI&gt;&lt;LI&gt;Proxy and/or Firewall in the middle which is changing certificates.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;One of the ways you can check for networking issues for that is do a tcpdump for packet capture and check the SSL Conversation:&lt;BR /&gt;tcpdump -i &amp;lt;interface&amp;gt; -s 65535 port 443 -w /tmp/port443.pcap&lt;BR /&gt;&lt;BR /&gt;That's for people who are familiar what packet capture looks like and can understand it's contents.&lt;/P&gt;</description>
      <pubDate>Fri, 19 May 2023 12:20:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/App-Upgrade-GUI-Getting-internal-server-error/m-p/643901#M16376</guid>
      <dc:creator>dtsariapkin</dc:creator>
      <dc:date>2023-05-19T12:20:07Z</dc:date>
    </item>
  </channel>
</rss>

