-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
SSL3_GET_RECORD:wrong version number exception during requests to Google Analytics API #37
Comments
yeah, it's just some communication badness happening under the hood -- not much we can do at this level other than just retry (as you're doing). |
Are you sure this has nothing to do with disabling SSL_V3? Any chance we could move this into the library so future users don't waste time attempting to debug — happy to investigate a PR. |
@jessepollak Were you by any chance using the same |
Not explicitly, but it could have been happening under the hood? |
For sure. For example if you created a service with You can confirm, at least, that you were using |
Hm, so we are using it inside of Flask, which I'm pretty sure spins up multiple threads (at least in local environments), so yes. |
Somewhat "confirms" what our other experience indicates. If you're still having this issue, check out: It'll increase the memory consumption a teensy bit (i.e. just by the size of one instance) but you won't have these issues where one thread eats the bytes intended for another. |
Cool, thank you for the response!! |
Sure thing. Before we knew what was causing the error I collected lots of similar bugs on the web (including this one). I figured since this helped confirm it was a real issue, I should give back a little bit. |
👍 |
Thank you for the solution @dhermes and thank you for posting this issue @jessepollak . |
I was having the same problem. What was happening is that I had 2 connections one in two different scopes, try to use it as a singleton and see if it works. |
More import/lint cleanup.
I was having similar issue when working with google apis in threads. Turns out, I had to build individual services for each threads. Thanks so much |
When using the client to make requests to the Google Analytics, API, we see the following exception occasionally. It can usually be solved by making retrying the request.
The text was updated successfully, but these errors were encountered: