"Configure" error in version 4.0

[grinabms]

After installing v4.0, I am trying to follow the instructions to import my AWS account info into the new app. Unfortunately, when I click on CONFIGURE, I get an error stating:
In handler 'targets': Unexpected error "" from python handler: "[SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:595)". See splunkd.log for more details.

The splunkd.log file shows this stack trace. Sorry about the word-wrap in my cut and paste attempt.
09-23-2015 17:16:11.995 +0000 ERROR AdminManagerExternal - Stack trace from python handler:\nTraceback (most recent call last):\n File "/opt/splunk/lib/python2.7/site-packages/splunk/admin.py", line 70, in init\n hand.execute(info)\n File "/opt/splunk/lib/python2.7/s
ite-packages/splunk/admin.py", line 529, in execute\n if self.requestedAction == ACTION_LIST: self.handleList(confInfo)\n File "/opt/splunk/etc/apps/splunk_app_aws/bin/target_handler.py", line 57, in handleList\n targets = self.get_target_manager().list_target
s()\n File "/opt/splunk/etc/apps/splunk_app_aws/bin/target_handler.py", line 89, in _get_target_manager\n return tm.TargetManager(app=self.appName, owner=self.userName, session_key=self.getSessionKey())\n File "/opt/splunk/etc/apps/splunk_app_aws/bin/aws/target_manag
er.py", line 25, in __init\n if CONF_TARGET not in self._service.confs:\n File "/opt/splunk/etc/apps/splunk_app_aws/bin/splunklib/client.py", line 1661, in __contains\n response = self.get(key)\n File "/opt/splunk/etc/apps/splunk_app_aws/bin/splunklib/client.p
y", line 1611, in get\n return super(Collection, self).get(name, owner, app, sharing, **query)\n File "/opt/splunk/etc/apps/splunk_app_aws/bin/splunklib/client.py", line 709, in get\n **query)\n File "/opt/splunk/etc/apps/splunk_app_aws/bin/splunklib/binding.py",
line 241, in wrapper\n return request_fun(self, *args, **kwargs)\n File "/opt/splunk/etc/apps/splunk_app_aws/bin/splunklib/binding.py", line 63, in new_f\n val = f(*args, **kwargs)\n File "/opt/splunk/etc/apps/splunk_app_aws/bin/splunklib/binding.py", line 586, in
get\n response = self.http.get(path, self._auth_headers, **query)\n File "/opt/splunk/etc/apps/splunk_app_aws/bin/splunklib/binding.py", line 1056, in get\n return self.request(url, { 'method': "GET", 'headers': headers })\n File "/opt/splunk/etc/apps/splunk_app
aws/bin/splunklib/binding.py", line 1108, in request\n response = self.handler(url, message, **kwargs)\n File "/opt/splunk/etc/apps/splunk_app_aws/bin/splunklib/binding.py", line 1230, in request\n connection.request(method, path, body, head)\n File "/opt/splunk/l
ib/python2.7/httplib.py", line 1001, in request\n self.send_request(method, url, body, headers)\n File "/opt/splunk/lib/python2.7/httplib.py", line 1035, in _send_request\n self.endheaders(body)\n File "/opt/splunk/lib/python2.7/httplib.py", line 997, in endheade
rs\n self._send_output(message_body)\n File "/opt/splunk/lib/python2.7/httplib.py", line 850, in _send_output\n self.send(msg)\n File "/opt/splunk/lib/python2.7/httplib.py", line 812, in send\n self.connect()\n File "/opt/splunk/lib/python2.7/httplib.py", line
1212, in connect\n server_hostname=server_hostname)\n File "/opt/splunk/lib/python2.7/ssl.py", line 350, in wrap_socket\n _context=self)\n File "/opt/splunk/lib/python2.7/ssl.py", line 566, in __init_\n self.do_handshake()\n File "/opt/splunk/lib/python2.7/s
sl.py", line 788, in do_handshake\n self._sslobj.do_handshake()\nSSLError: [SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:595)\n

[grinabms]

Yes, it is running on http, and definitely not https.

-Pete

[grinabms]

I tried removing the two apps (Splunk for AWS, and the AWS add-on) by removing all files in /opt/splunk/etc/apps/* and /opt/splunk/etc/user/* that was related to those two apps. Current app and previous app related stuff was deleted.

Next, I re-downloaded and re-installed the latest Splunk for AWS, and the add-on. Unfortunately, the SSL error appeared again when I clicked the Configure tab.

I decided to spin up a fresh new EC2 instance, install Splunk v6.3, and the apps. Everything went well, and now I'm able to configure my AWS accounts without a problem.

Regards,
Pete

[pchen_splunk]

Hi Pete, Is your Splunk running on http? You can get the protocol from the leading word of URL. HTTP or HTTPS

[pchen_splunk]

Pete, we guess in your old EC2 instance, the splunkd (port 8089) is running on http but not https. In default, the splunkd is running on https, you can check if URL https://hostname:8089 is working.

[chwang_splunk]

Hi grinabms! Pls try to logout, clean your browser cache/session and re-login. Does it help?

If not, to reproduce this problem, we need some more information about your environment:

Are you using a single instance or some distributed system such as search head clustering?
Have you enabled SSL or set remote target for your instance before upgrade?
What's the version of AWS app and your add-on before upgrade? Have you checked "overwrite" old app option during installation?
Any other modification for configuration before meeting this problem?

Thanks

[grinabms]

The same error happens when I click CONFIGURE on a different browser (Firefox instead of Chrome), so it's not a matter of bad data stuck in cache.

This is a single instance Splunk environment. I couldn't find any evidence of explicit SSL in my old configs... where would that be located?

Regarding version numbers, the "Add-on for AWS" went from 1.1.1 to 2.0.0, and the "App for AWS" went from 3,0 to 4.0.0. I don't remember whether overwrite was checked, but I followed the upgrade instructions carefully.

I made a custom modification in "App for AWS" before version 3.0, but I don't believe it was active in 3.0.

-Pete

Thanks,
Pete

[mreynov_splunk]

Pete,

The number of variables is growing with every message.

Can you enable the old app before going to configure the new app?
Can you ensure that new TA has global permissions?

If none of this helped, how about this:
Remove the old and new TAs and Apps and run through the install again.

Once you do and if the problem is still there, we have a couple of options:
- open a support case and send us a diag
- if you don't have an enterprise license, just send us a diag
- a screenshot of the problem would be useful as well

[rpille_splunk]

Hi grinabms! I can try to help, but first: some context: Are you on Splunk Cloud or Splunk Enterprise on prem? And can you confirm that you have also installed the Splunk Add-on for Amazon Web Services 2.0.0?

[grinabms]

I am running Splunk Enterprise v6.3 on a Linux instance in AWS. The Splunk and Splunk-App-for-AWS have been upgraded from older versions. I had 5 AWS accounts configured in the older app.

Yesterday, I upgraded to Splunk App for AWS v4.0, and the Splunk Add-on for AWS v2.0. I disabled the older versions through the Splunk UI.

Thanks,
Pete (grinabms)