Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Login fails when connecting to TFS instance with self-signed certificate
See original GitHub issueAttempting to login against our local TFS instance which uses a cert signed by an internal/private CA fails. Adding the --debug switch confirms my suspicion that the cert isn’t trusted. Is there any way to provide an alternate CA bundle? Or to tell the CLI to accept a specific CA or cert?
urllib3.connectionpool : Retrying (Retry(total=2, connect=3, read=3, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:748)'),)': /tfs/defaultcollection2/_apis
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
That’s exactly what I was looking for, and it works great. Thanks for the follow up.
@markjgardner There is a safer way to workaround this issue. You can take your servers certificate, and copy it to a Base-64 encoded X.509 file (In windows you would open the certificate, go to details tab, and choose ‘copy to file…’ button). Then you can set the following environment variable
REQUESTS_CA_BUNDLEto the file path of your cert file. Once this is done you will no longer get verification errors. Can you give this a try?