Nothing Special   »   [go: up one dir, main page]
Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Abot AbotX TLS 1.2 Support, Could not create SSL/TLS secure channel #176

Open
wpkramer opened this issue Dec 11, 2017 · 3 comments
Open

Abot AbotX TLS 1.2 Support, Could not create SSL/TLS secure channel #176

wpkramer opened this issue Dec 11, 2017 · 3 comments

Comments

@wpkramer
Copy link

The crawl of a site supporting only TLS 1.2 was failing. Modifying the constructors of the PageRequester assigning the default security protocol resolves the problem for us. This may not be the best home for assigning the SecurityProtocol setting. Also does not future proof for TLS 1.3.

        System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12 | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls;
@sjdirect
Copy link
Owner

Thanks for reporting this. I agree that Abot may not be the best initializer of this setting. I will leave this issue open so others have a workaround.

@alex-jitbit
Copy link

Thanks for leaving the issue open @sjdirect !!!

Took me a while to find it though. Adding the error text I was getting: "Could not create SSL/TLS secure channel" (just so Google indexes it and brings more people to the workaround.)

@sjdirect sjdirect changed the title TLS 1.2 Support Abot AbotX TLS 1.2 Support, Could not create SSL/TLS secure channel Mar 13, 2019
@sjdirect
Copy link
Owner
sjdirect commented Mar 13, 2019 •
edited
Loading

agreed @alex-jitbit , changed the subject for better phrase indexing

Repository owner deleted a comment from rarunkumar454 Nov 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sjdirect @wpkramer @alex-jitbit