splunk / splunk/splunk-sdk-python

Search Result Export with SSL off doesn't work

Open
#828 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
743
Forks
387
Avg merge
42m
Merged PRs (30d)
4

Description

Describe the bug
When the [sslConfig] enableSplunkdSSL is set to false in server.conf, then export of search results fails, giving the following on-screen error:

Service Unavailable

This was working in the 9.* version, but has been broken in the 10.* version.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'server.conf' and set the [sslConfig] enableSplunkdSSL flag to false. Restart splunk server.
  2. Perform a search in the web search.
  3. Attempt to export the results using the down arrow.
  4. See error

Expected behavior
Results are exported

Logs or Screenshots
This log can be seen in web_service.log:

2026-08-18 06:50:23,399 ERROR	[6a8400af56192cc745880] __init__:874 - SSL error communicating with splunkd, error="[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1046)", path=/servicesNS/admin/search/search/v2/jobs/export
2026-08-18 06:50:23,399 ERROR	[6a8400af56192cc745880] decorators:413 - Splunkd daemon is not responding: ('SSL error communicating with splunkd, error="[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1046)", path=/servicesNS/admin/search/search/v2/jobs/export',)
Traceback (most recent call last):
  File "F:\Program Files\Splunk\Python-3.13\Lib\site-packages\splunk\rest\__init__.py", line 855, in streamingRequest
    conn.connect()
    ~~~~~~~~~~~~^^
  File "F:\Program Files\Splunk\Python-3.13\Lib\http\client.py", line 1499, in connect
    self.sock = self._context.wrap_socket(self.sock,
                ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^
                                          server_hostname=server_hostname)
                                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "F:\Program Files\Splunk\Python-3.13\Lib\ssl.py", line 460, in wrap_socket
    return self.sslsocket_class._create(
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
        sock=sock,
        ^^^^^^^^^^
    ...<5 lines>...
        session=session
        ^^^^^^^^^^^^^^^
    )
    ^
  File "F:\Program Files\Splunk\Python-3.13\Lib\ssl.py", line 1085, in _create
    self.do_handshake()
    ~~~~~~~~~~~~~~~~~^^
  File "F:\Program Files\Splunk\Python-3.13\Lib\ssl.py", line 1381, in do_handshake
    self._sslobj.do_handshake()
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^
ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1046)

Splunk (please complete the following information):

  • Version: 10.4.1
  • OS: Windows
  • Deployment: Single Instance Enterprise

SDK (please complete the following information):

  • Version: As per install
  • Language Runtime Version: As per install
  • OS: As per install

Additional context
I think the problem is in Splunk\Python-3.13\Lib\site-packages\splunk\rest\__init__.py, when it goes to create the "conn" object for the connection, it has an if-else statement. In the "if" part of the statement, it has the "if isssl else httplib.HTTPConnection(host, port, timeout=timeout)" code which will create an HTTPConnection if ssl is not enabled. BUT in the "else" part of the if-else statement, it doesn't have that, so will always attempt to create an HTTPSConnection even if ssl is not enabled.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in Splunk\Python-3.13\Lib\site-packages\splunk\rest_init_.py, around streamingRequest and the conn creation logic, then reproduce the export request with enableSplunkdSSL=false. Verify the connection uses the configured protocol and that search-result export succeeds without the WRONG_VERSION_NUMBER error.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
74/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.