purple-discord icon indicating copy to clipboard operation
purple-discord copied to clipboard

Connection error: Unable to connect to discordapp.com: SSL Handshake Failed.

Open Nic-Wow1 opened this issue 6 years ago • 9 comments

I get this error when connecting: Connection error: Unable to connect to discordapp.com: SSL Handshake Failed.

Nic-Wow1 avatar Oct 19 '18 20:10 Nic-Wow1

What version of Pidgin are you using? If it's not the current latest (2.13.0) then you'll want to use the NSS Preferences plugin to change the TLS max version setting until it works

failing that, attach a debug log (from the buddy list, Help->Debug Window) as you reconnect to the account

EionRobb avatar Oct 19 '18 22:10 EionRobb

I have just compiled purple-discord and try to use it as a Spectrum2 gateway backend … and I get the same error. Here are the lines from the logfile:

5674: 2018-10-22 02:05:38,087 INFO  libpurple: proxy:Attempting connection to 104.16.59.5
5674: 2018-10-22 02:05:38,087 INFO  libpurple: proxy:Connecting to discordapp.com:443 with no proxy
5674: 2018-10-22 02:05:38,087 INFO  libpurple: proxy:Connection in progress
5674: 2018-10-22 02:05:38,101 INFO  libpurple: proxy:Connecting to discordapp.com:443.
5674: 2018-10-22 02:05:38,101 INFO  libpurple: proxy:Connected to discordapp.com:443.
5674: 2018-10-22 02:05:38,118 INFO  libpurple: nss:Handshake failed  (-12286)
5674: 2018-10-22 02:05:38,118 ERROR backend: g_log discord_update_cookies: assertion 'headers != NULL' failed
5674: 2018-10-22 02:05:38,118 ERROR backend: GLib g_strstr_len: assertion 'haystack != NULL' failed
5674: 2018-10-22 02:05:38,118 INFO  libpurple: connection:Connection error on 0xaaab15da9530 (reason: 0 description: Connection error: Unable to connect to discordapp.com: SSL Handshake Failed.)

According to the startup message, TLSv1.0 (0x301) - TLSv1.3 (0x304) is supported and allowed:

5674: 2018-10-22 02:04:31,551 INFO  libpurple: nss:TLS supported versions: 0x0301 through 0x0304
5674: 2018-10-22 02:04:31,551 INFO  libpurple: nss:TLS versions allowed by default: 0x0301 through 0x0303
5674: 2018-10-22 02:04:31,551 INFO  libpurple: nss:Changed allowed TLS versions to 0x0301 through 0x0304

mbirth avatar Oct 22 '18 00:10 mbirth

this is also affecting me. latest version of pidgin isn't in Ubuntu repos yet, but using the NSS Prefs plugin to change Max TLS version to 1.2 (down from 1.3) did indeed help. attaching error log here anyway, in case that is still of any use to you. https://gist.github.com/mindcombatant/8fc323e4ce4c02f2425b642c3341b02c

mindcombatant avatar Oct 22 '18 07:10 mindcombatant

@EionRobb Do you know how to set max_tls with Spectrum2's [purple] section?

mbirth avatar Oct 26 '18 12:10 mbirth

Getting this as well with 2.12.0:

Couldn't connect to gateway

(09:57:20) proxy: Connecting to gateway.discord.gg:443. (09:57:20) proxy: Connected to gateway.discord.gg:443. (09:57:20) nss: Handshake failed (-12286) (09:57:20) connection: Connection error on 0x55e677102e70 (reason: 0 description: Couldn't connect to gateway)

Will try with 2.13...

Updated: updating to 2.13 resolved the issue for me.

psi29a avatar Nov 07 '18 08:11 psi29a

I had also same issue while using Pidgin 2.12.0 from LM repos. Using 'NSS Preferences' plugin and changing TLS max version from 1.0 to 1.2 solved it.

Sawiq avatar Dec 20 '18 14:12 Sawiq

Same here with bitlbee

wvffle avatar Oct 28 '19 10:10 wvffle

Today this problem surfaced for me too, using the nss preferences plugin and setting the max version of TLS from 1.3 to 1.2 solved the issue. Yesterday I updated nss from 3.57 to 3.58 on Artix Linux, which may be why the problem surfaced.

Penaz91 avatar Oct 21 '20 20:10 Penaz91

This new issue I found may be related to #313.

Penaz91 avatar Oct 22 '20 19:10 Penaz91