Python-based modular inputs fail to establish HTTPS connections to remote APIs or local loopback interfaces.
The following traceback signature is recorded in <SPLUNK_HOME>\var\log\splunk\splunkd.log or <SPLUNK_HOME>\var\log\splunk\<APP_NAME>.log:
ssl.SSLError: [ASN1: NOT_ENOUGH_DATA] not enough data (_ssl.c:4213)requests.exceptions.SSLError: HTTPSConnectionPool(host='<HOST>', port=<PORT>): Max retries exceeded
This error manifests when OpenSSL 3.0.21 or 3.5.6 fails during automated enumeration of certificates from the Windows System Certificate Stores (ROOTandCA) duringssl.create_default_context()execution.
Verify Python and OpenSSL Version Stack: Execute the following command in PowerShell or Command Prompt to confirm the bundled OpenSSL build and test default SSL context creation:
"<SPLUNK_HOME>\bin\splunk.exe" cmd python -c "import ssl; print('OpenSSL Version:', ssl.OPENSSL_VERSION); ssl.create_default_context(); print('STATUS: SUCCESS')"
ssl.SSLError: [ASN1: NOT_ENOUGH_DATA] not enough data.STATUS: SUCCESS.Upgrade to Fixed Maintenance Release (Recommended): Apply the appropriate maintenance release containing updated OpenSSL builds:
10.0.12 or later.10.2.9 or later.10.4.5 or later.Temporary Version Rollback: If immediate upgrading is not feasible, downgrade the instance to a build preceding the OpenSSL regression:
10.0.6 (or any build in the 10.0.2–10.0.6 range).10.2.5 or earlier.