mirror of
https://github.com/Glitchy-Sheep/boosty-downloader.git
synced 2026-10-14 21:33:23 +00:00
[GH-ISSUE #174] SSL certificate verify failed #29
Labels
No labels
api-drift
bug
ci
documentation
enhancement
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Glitchy-Sheep/boosty-downloader#29
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @print423 on GitHub (Aug 29, 2026).
Original GitHub issue: https://github.com/Glitchy-Sheep/boosty-downloader/issues/174
🐛 What happened?
When I try to run the script, I get an SSL certificate verification error. I updated the certifi, but nothing has changed. Is this a problem on my end or on their server?
📋 Error output
🖥️ Environment
debug-file:
@print423 commented on GitHub (Aug 31, 2026):
Maybe this will be helpful to someone.
I downloaded cacert.pem from the official website, then passed it to Python and ran the script (the contents of the batch file are shown below), after which the script started working.
@echo off
set SSL_CERT_FILE=O:\Python314\Scripts\cacert.pem
set REQUESTS_CA_BUNDLE=O:\Python314\Scripts\cacert.pem
boosty-downloader.exe download --username [author_name]
pause
@Glitchy-Sheep commented on GitHub (Aug 31, 2026):
Interesting, I'll check this out a little bit later, thank you very much
@Glitchy-Sheep commented on GitHub (Oct 3, 2026):
@print423
Just to confirm: did the connection fail with the default settings, then work after you set
SSL_CERT_FILEtocacert.pem?On Windows, Python uses CA certificates from the Windows certificate stores and OpenSSL's default paths. The error does not tell us which certificate had expired.
Where did you download
cacert.pem? Was it https://curl.se/ca/cacert.pem?If the problem still occurs without the workaround:
Check your system date and time.
Press
Win + Rand open these separately:These show user and computer certificates. Under Trusted Root Certification Authorities and Intermediate Certification Authorities, open Certificates and check the validity dates. Please leave the certificates unchanged; an expired entry alone does not prove it caused the error.
In Command Prompt, check the certificate trust list:
Please share any errors and the
LastSyncTimevalue from the output.@Glitchy-Sheep commented on GitHub (Oct 3, 2026):
Since providing a fresh CA bundle resolved the issue for you, I'm closing this for now. Current tests also pass with certificate verification enabled. Please reopen the issue if it happens again.