-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSLError - Option to skip checking/Max retries? #113
Comments
Hi! I've done that on Feel free to try it out and report back if it still happens too often or if at all. |
Still happening, maybe not as often. Perhaps skip the |
Hmmm, I'll try to look into it more deeply on the bot side too.
So perhaps the endpoint is not related to the issue and wouldn't help that much, hard to say. I'll implement the skip nonetheless. I've also seen some people experiencing https://stackoverflow.com/questions/72468213/sslzeroreturnerror-error-only-in-python-3-10 Perhaps it's worth a shot checking which ones you have installed:
Also, you could check how fast/slow the handshake is by running:
I was getting some intermittent errors (but perhaps it was just you restarting nginx)
|
Oh yeah you’re right, getting the bad request when running that openssl cmd too. I did just update ubuntu/python but if it’s returning a 504 that’s a me issue. Ps: what’s your preferred sponsorship method? |
Sure, I'll keep investigating on my side but do let me know if you happen to find something on yours.
I really don't have a preference, Liberapay is usually the fastest but I really don't mind if any of the ones listed here is used (Paypal, Ko-Fi, etc.): I list so many options mostly for trying to be accommodating for those who want to sponsor, as not all of them are available in all countries, currencies, etc. |
I've had pretty good success not with the retries and some server tuning. I upped the number of connections in nginx. The script will still retry but it usually succeeds on the second or third attempt |
I seem to get this sometimes and Im wondering what could be done to prevent it. Could it be as simple as just ignoring ssl? Or maybe increasing retries? Seems to happen when the site is under load but I haven't seen any ssl issues using the site at the same time myself.
The text was updated successfully, but these errors were encountered: