Open chainria opened 2 years ago
I have revisited this issue. Unfortunately, it stays broken, even with re-enabled developer mode on the Discord App and using that token. What seems obvious at first is that the token got much longer. I also pasted a debug log, just cut out the unrelated information.
(14:32:37) discord: Fetching url https://discord.com/api/v9/auth/login (14:32:37) discord: With postdata ###PASSWORD REMOVED### (14:32:37) http: Performing new request 0x561c02b8e600 to discord.com. (14:32:37) dnsquery: Performing DNS lookup for discord.com (14:32:37) dns: Created new DNS child 16780, there are now 1 children. (14:32:37) dns: Successfully sent DNS request to child 16780 (14:32:37) dns: Got response for 'discord.com' (14:32:37) dnsquery: IP resolved for discord.com (14:32:37) proxy: Attempting connection to 162.159.136.232 (14:32:37) proxy: Connecting to discord.com:443 with no proxy (14:32:37) proxy: Connection in progress (14:32:37) proxy: Connecting to discord.com:443. (14:32:37) proxy: Connected to discord.com:443. (14:32:38) nss: SSL version 3.4 using 128-bit AES-GCM with 128-bit AEAD MAC Server Auth: 256-bit TLS 1.3, Key Exchange: 255-bit TLS 1.3, Compression: NULL Cipher Suite Name: TLS_AES_128_GCM_SHA256 (14:32:38) nss: subject=CN=sni.cloudflaressl.com,O="Cloudflare, Inc.",L=San Francisco,ST=California,C=US issuer=CN=Cloudflare Inc ECC CA-3,O="Cloudflare, Inc.",C=US (14:32:38) nss: subject=CN=Cloudflare Inc ECC CA-3,O="Cloudflare, Inc.",C=US issuer=CN=Baltimore CyberTrust Root,OU=CyberTrust,O=Baltimore,C=IE (14:32:38) nss: partial certificate chain (14:32:38) certificate/x509/tls_cached: Starting verify for discord.com (14:32:38) certificate/x509/tls_cached: Checking for cached cert... (14:32:38) certificate/x509/tls_cached: ...Found cached cert (14:32:38) nss/x509: Loading certificate from /home/chain/.purple/certificates/x509/tls_peers/discord.com (14:32:38) certificate/x509/tls_cached: Peer cert matched cached (14:32:38) nss/x509: Exporting certificate to /home/chain/.purple/certificates/x509/tls_peers/discord.com (14:32:38) util: Writing file /home/chain/.purple/certificates/x509/tls_peers/discord.com (14:32:38) nss: Trusting CN=sni.cloudflaressl.com,O="Cloudflare, Inc.",L=San Francisco,ST=California,C=US (14:32:38) certificate: Successfully verified certificate for discord.com ... (xml files being written) ... (14:32:38) http: Request 0x561c02b8e600 performed without success. (14:32:38) discord: Got response: {"code": 50035, "errors": {"email": {"_errors": [{"code": "INVALID_LOGIN", "message": "Login or password is invalid."}]}, "password": {"_errors": [{"code": "INVALID_LOGIN", "message": "Login or password is invalid."}]}}, "message": "Invalid Form Body"} (14:32:38) connection: Connection error on 0x561c02923140 (reason: 2 description: Bad username/password)
Hm... the "/auth/login" bit in the first line suggests that its using the regular username/password to login, rather than the token
Can you try unsetting the password on your account in Pidgin, which should pop up with a QR Code that you can scan on your phone?
The password was saved in a keychain, I removed all of them, still the same.
I explicitely compiled it with QR Support, but I never really get a QR Code. Am I doing something wrong? I just get the dreaded "Need CAPTCHA to login. Consider using Harmony first, then retry." message.
Edit: QR Code support is compiled in:
ldd /usr/lib64/purple-2/libdiscord.so | grep qr libqrencode.so.4 => /usr/lib64/libqrencode.so.4 (0x00007f8c26cce000)
It should only show the QR Code if the password field is blank in the account
After I restarted Secret Service it works again. Don't know what strange fluke this was, but it all started with a reboot. Still, haven't seen any QR Code dialog at all, whatever I tried.
Out of the blue I get this error. Cannot log in any more. Got token from the browser, Still the same problem. Haven't changed password at all. Does anybody know anything about this?
Using Pidgin Pidgin 2.14.8 (libpurple 2.14.8) 5076f03ecaaa4eb77a6a9bd3892455f90551eaad And Plugin 0.9.2022.05.04.git.0a864c5
Edit: Updating to the newest commit did not help as well