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

Can't update Twitter, HTTP Error #35 : SSL Connect Error #122

Closed
ARealSnake opened this Issue Jun 7, 2015 · 7 comments

Comments

Projects
None yet
3 participants
@ARealSnake

ARealSnake commented Jun 7, 2015

So it's seems like I can't connect/update my Twitter Feed anymore. Everytime Taiga just send me the HTTP Error #35
I tried to get into debug mode to see where the problem was at and the only thing was :

2015-06-07 12:20:03 [Debug] http_callback.cpp:123 base::http::Client::DebugHandler | schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.

After that Taiga close the connection and send the error.

@erengy

This comment has been minimized.

Show comment
Hide comment
@erengy

erengy Jun 7, 2015

Owner

Previously: #44, #63, #114

Could it be that your computer's time and date setting is incorrect? From what I read, this seems to be one of the causes of the 0x80092013 error. Some people mention that changing the DNS setting (e.g. to Google Public DNS or OpenDNS) resolves the issue. Others say that it's related to AVG's security products... In any case, it seems to be a local and temporary issue.

Owner

erengy commented Jun 7, 2015

Previously: #44, #63, #114

Could it be that your computer's time and date setting is incorrect? From what I read, this seems to be one of the causes of the 0x80092013 error. Some people mention that changing the DNS setting (e.g. to Google Public DNS or OpenDNS) resolves the issue. Others say that it's related to AVG's security products... In any case, it seems to be a local and temporary issue.

@ARealSnake

This comment has been minimized.

Show comment
Hide comment
@ARealSnake

ARealSnake Jun 7, 2015

The thing is, I have the right time, I already use Google Public DNS and I already checked my antivirus (Which is BitDefender)

ARealSnake commented Jun 7, 2015

The thing is, I have the right time, I already use Google Public DNS and I already checked my antivirus (Which is BitDefender)

@ARealSnake ARealSnake changed the title from Can't update Twitter, HTTP Error #35 : SSL Conecct Error to Can't update Twitter, HTTP Error #35 : SSL Connect Error Jun 7, 2015

@erengy

This comment has been minimized.

Show comment
Hide comment
@erengy

erengy Jun 7, 2015

Owner

Does this suggestion work?

The problem persists until I do a restart of the machine OR I open Internet Explorer and try to reach the same website. After that everything works fine again.

I assume Internet Explorer does some kind of 'reset' of the schannel-component and after that it works fine again.

Owner

erengy commented Jun 7, 2015

Does this suggestion work?

The problem persists until I do a restart of the machine OR I open Internet Explorer and try to reach the same website. After that everything works fine again.

I assume Internet Explorer does some kind of 'reset' of the schannel-component and after that it works fine again.

@ARealSnake

This comment has been minimized.

Show comment
Hide comment
@ARealSnake

ARealSnake Jun 8, 2015

Still no improve sadly, I also restarted my computer to check and... Nope still nothing

ARealSnake commented Jun 8, 2015

Still no improve sadly, I also restarted my computer to check and... Nope still nothing

@mchubby

This comment has been minimized.

Show comment
Hide comment
@mchubby

mchubby Aug 8, 2015

I had the same issue with BitDefender Total Security 2015.
The workaround I found was to temporarily disable the firewall (Protection > Firewall > uncheck the blue mark).
After you log in, the client reuses its HttpClient, so you can re-enable the FW afterwards. However, if you quit and launch Taiga again, the same problem will occur.

(Note: all sorts of SSL analysis is turned off in Web Protection, too)

EDIT: the same issue as a fellow user of Bitdefender I mean. Not using Twitter.
EDIT2: now works by disabling (Protection > Firewall > uncheck "Block Internet Connection Sharing")

mchubby commented Aug 8, 2015

I had the same issue with BitDefender Total Security 2015.
The workaround I found was to temporarily disable the firewall (Protection > Firewall > uncheck the blue mark).
After you log in, the client reuses its HttpClient, so you can re-enable the FW afterwards. However, if you quit and launch Taiga again, the same problem will occur.

(Note: all sorts of SSL analysis is turned off in Web Protection, too)

EDIT: the same issue as a fellow user of Bitdefender I mean. Not using Twitter.
EDIT2: now works by disabling (Protection > Firewall > uncheck "Block Internet Connection Sharing")

@mchubby

This comment has been minimized.

Show comment
Hide comment
@mchubby

mchubby Oct 22, 2015

More info from rust-lang/cargo#1689 (comment)
Setting network adapter to "trusted" and stealth enabled completely solves the issue without resorting to toggling off the Bitdefender firewall.

mchubby commented Oct 22, 2015

More info from rust-lang/cargo#1689 (comment)
Setting network adapter to "trusted" and stealth enabled completely solves the issue without resorting to toggling off the Bitdefender firewall.

@erengy

This comment has been minimized.

Show comment
Hide comment
@erengy

erengy Jan 13, 2016

Owner

I'll consider this issue resolved, thanks to @mchubby.

Owner

erengy commented Jan 13, 2016

I'll consider this issue resolved, thanks to @mchubby.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment