-
Notifications
You must be signed in to change notification settings - Fork 573
Open
Labels
bugSomething isn't workingSomething isn't working
Description
This issue respects the following points:
- This is a bug, not a question or a configuration issue; Please visit our forum first to troubleshoot with volunteers, before creating a report. The links can be found here.
- This issue is not already reported on GitHub (I've searched it).
- I'm using an up to date version of OpenBullet2. We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
- I agree to follow OpenBullet's Code of Conduct.
- This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.
Description of the bug
Hi, I saw someone reported this bug but for ob1 which was later marked fixed for it.
but I keep on getting failed to connect to ssl on ob2 when selecting version of tls manually rurilib customsyphersuits.
Also the proxy i am using is http type premium proxy without credentials.
Reproduction steps
- open openbullet2
- make any test config
- create httpreq block
- keep any url
- set http library as - rurilibhttp
- security protocol as tls 1.0 or 1.1 or any other
then try to make a get req and you will get the same error "Failed to connect ssl"
What is the current bug behavior?
just doesn't fetch the website using the tls as it is supposed to instead we get the error
What is the expected correct behavior?
open the website/url using tls request as it is supposed to.
Version of the client
0.3.2
Type of client
Native client
Environment
- OS: win10
- Virtualization:
- Browser: native clientOpenBullet2 logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Relevant LoliCode if needed
Additional information
No response
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working