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
The request was aborted: Could not create SSL/TLS secure channel. #85
Comments
This reverts commit e6adfc3. Making changes to ServicePointManager inside a library is a _very_ bad idea. This also breaks now since Twitter disabled SSL3 for their servers because of the POODLE vulnerability
I am having the same problem; wondering if maybe the consumer key / secret combination has expired. Since I do not have access to the account that was created for that it may take me awhile to confirm. |
Not sure if this helps however, I downloaded the latest (here in a zip file); removed the Silverlight projects since they had some errors and I don't need them. Built the solution in VS 2010 and put the new Twitterizer2 DLL into my web app and that fixed it. |
I have the same issue.Is there any option to get new framework version? |
I'm currently having that issue, any idea how to fix it? |
worked fine for 3 years - but now getting this issue |
Hi,
I have a Twitterizer2 implementation in my solution, but when I try to use if for social authentication, I get the following error: The request was aborted: Could not create SSL/TLS secure channel. I'm running a copy of the latest version of the master branch.
I tried adding ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls (and other TLS versions) in my code but that doesn't solve the issue. I also overrode the ServerCertificateValidationCallback of ServicePointManager to accept all certificates, but that didn't solve the issue either. Twitter's SSL certificate is fine and is accepted by my machine.
When I run the unit tests in the Twitterizer2 project I can reproduce the error.
P.s., there are some issues in the Silverlight projects regarding missing SearchOptions properties. I had to disable those projects in order to build the .NET projects.
The text was updated successfully, but these errors were encountered: