Python 3.13 / OpenSSL 3.5.5 crashes on Windows with OPENSSL_Uplink ... no OPENSSL_Applink when SSLKEYLOGFILE is set
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Bug report
Bug description:
Title: Python 3.13 / OpenSSL 3.5.5 crashes on Windows with OPENSSL_Uplink ... no OPENSSL_Applink when SSLKEYLOGFILE is set
Environment:
- OS: Windows
- Python: 3.13.12, 64-bit
- OpenSSL: OpenSSL 3.5.5 27 Jan 2026
- Application: ComfyUI Desktop / ComfyUI Manager
- GPU: NVIDIA RTX 3060
Problem:
When SSLKEYLOGFILE is set, Python exits immediately during HTTPS/network activity with:
OPENSSL_Uplink(...): no OPENSSL_Applink
There is no Python traceback because the process aborts in native OpenSSL code.
Reproduction:
- Set an environment variable:
SSLKEYLOGFILE=E:\AI\Apps\Wireshark\sslkeys.log
- Start ComfyUI with Manager public/network mode enabled.
- During ComfyUI-Manager startup network/cache fetches, Python exits with:
OPENSSL_Uplink(...): no OPENSSL_Applink
Observed:
The process exits with code 1. No Python exception is raised.
Expected:
Setting SSLKEYLOGFILE should enable TLS key logging or fail gracefully, not abort the Python process.
Investigation:
import sslworks.import aiohttp.resolverworks.import requests,urllib3,github, andhuggingface_hubwork.- ComfyUI runs in offline mode.
- ComfyUI Manager public mode crashes during online cache/network fetching.
- ProcMon showed access to
E:\AI\Apps\Wireshark\sslkeys.logimmediately before the crash. - Clearing the environment variable fixes the issue:
set SSLKEYLOGFILE=
After removing SSLKEYLOGFILE, ComfyUI Manager starts successfully in public mode.
Workaround:
Remove SSLKEYLOGFILE from User/System environment variables.
Question:
Is this a known issue with Python 3.13 / OpenSSL 3.5.x on Windows when TLS key logging is enabled?
CPython versions tested on:
3.13
Operating systems tested on:
Windows
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the SSLKEYLOGFILE failure on Windows with Python 3.13 and OpenSSL 3.5.5 during the described HTTPS activity; the report names no CPython source file or test. Done means determining whether CPython is responsible and ensuring key logging no longer aborts the process, with the ComfyUI Manager public-mode scenario as validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100