Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Plugin fails to login, error 404 #48

Closed
GoogleCodeExporter opened this Issue Aug 23, 2015 · 55 comments

Comments

Projects
None yet
1 participant
*What steps will reproduce the problem?*
1. Enter account details
2. Activate the account in Pidgin

*What is the expected output? What do you see instead?*
Instead of logging in, Pidgin stays in the "connecting" state and nothing 
happens

*What version of the product are you using? On what operating system?*
libsteam 1.1, Windows 7 x64

*Please provide any additional information below.*
Output from the debug window:

 (12:28:48) certificate: Successfully verified certificate for api.steampowered.com
 (12:28:48) steam: post_or_get_ssl_connect_cb
 (12:28:48) steam: Error parsing response: <html>
 <head>
 <title>404 Not Found</title>
 </head>
 <body>
 <h1>Not Found</h1>
 </body>
 </html>

Original issue reported on code.google.com by nullweegee on 24 Apr 2013 at 10:35

I have this same issue, on Ubuntu 13.04, pidgin 2.10.7 and plugin 
libsteam64-1.1.so. 

Original comment by heinusho...@gmail.com on 30 Apr 2013 at 1:34

[deleted comment]
I fixed this issue by restoring an old copy of my .purple directory I had 
laying around.
Perhaps you could try moving your purple directory and having pidgin create a 
new one for you.

Original comment by GW.Ke...@gmail.com on 3 May 2013 at 3:57

Removing the .purple directory doesn't work. I suspect this all has to do with 
the steam guard code, so restoring an old .purple that was working onto the 
same computer may fix. I did a clean install erased the .purple folder and 
started fresh with no luck. I had it working back on my old win7 computer but 
haven't been able to get it to work on this windows 8, probably a change in the 
way steam's api gives guard codes (could be wrong haven't looked into it nor 
have I looked into the source code)

Original comment by aanon...@gmail.com on 3 May 2013 at 4:16

Yeah, it broke again for me. I've been cycling through every Steam Guard code I 
have trying to get it to work.
I even tried disabling steamguard completely using the steam client and that 
didn't work either.

Original comment by GW.Ke...@gmail.com on 3 May 2013 at 5:40

At least I'm getting something different now.

steam: Error parsing response: <html>
<head>
<title>401 Unauthorized</title>
</head>
<body>
<h1>Unauthorized</h1>
</body>
</html>

I can't seem to get a new steam guard code sent

Original comment by GW.Ke...@gmail.com on 3 May 2013 at 5:52

I diffed the two account.xml's I had and the main difference is one has an 
access token string and the other doesn't.
There doesn't seem to be any way to get the plugin to get a new steam guard 
code which means you probably can't get a new access token either.
I've tried recreating my account info with pidgin, making a new steam account, 
rebooting, downgrading, upgrading and it's completely broken with no way to get 
a new code.

Original comment by GW.Ke...@gmail.com on 3 May 2013 at 6:17

http://forums.steampowered.com/forums/showthread.php?t=3113693

Looks like Valve changed around the API.
A solution is in this post

http://forums.steampowered.com/forums/showpost.php?p=34331845&postcount=11

Original comment by GW.Ke...@gmail.com on 3 May 2013 at 6:59

Thanks for the links, GW.Kenta.  Looking into this

Original comment by eionrobb on 6 May 2013 at 11:42

  • Changed state: Accepted
Issue 51 has been merged into this issue.

Original comment by eionrobb on 6 May 2013 at 11:43

Thanks for looking into this, eionrobb. I am getting the exact same error as OP 
nullweegee, on Raspbian Wheezy (Debian Linux), Revision r43, Pidgin 2.10.6.

Original comment by max.laum...@gmail.com on 7 May 2013 at 2:22

Looked into it a bit, and there's no quick fix, sorry.  There's no RSA 
encryption built into libpurple/Pidgin so we have to do some trickery with 
libnss/gnutls.  Will give an update once I've got some more to work with

Original comment by eionrobb on 7 May 2013 at 4:22

  • Changed state: Started
Issue 53 has been merged into this issue.

Original comment by eionrobb on 11 May 2013 at 12:04

Any updates? 

Original comment by GW.Ke...@gmail.com on 15 May 2013 at 12:53

No, sorry, other than 'this is hard' :)

Original comment by eionrobb on 15 May 2013 at 1:16

I'm waiting for an update too, thanks for working on it eionrobb! 

Original comment by cafedjia...@gmail.com on 15 May 2013 at 7:54

Issue 55 has been merged into this issue.

Original comment by eionrobb on 20 May 2013 at 1:09

Sorry for not checking the other issues before submitting mine. Thanks for the 
quick response!

Original comment by katkabel on 20 May 2013 at 1:12

I am having the same issue, any update on this issue yet?

Original comment by michaelk...@gmail.com on 3 Jun 2013 at 6:13

The latest svn code is actually working for me.

You need nss and nspr now. I don't see a makefile anywhere and no build 
instructions...? In the Archlinux AUR package someone has provided a makefile 
and I have only added nss libs.

Original comment by haagch.c...@googlemail.com on 6 Jun 2013 at 6:43

Attachments:

I could have sworn there was a makefile when I built from source a couple weeks 
ago. I wonder if it not being there was an oversight.

at any rate, I will also try building this today and see if it works, thanks 
for posting that Makefile and noting that it appears to be working now, that's 
very exciting news :D

Original comment by a.minor....@gmail.com on 6 Jun 2013 at 6:46

Thanks for testing svn, haagch.christoph. What platform are you testing on? I 
keep getting segfaults on windows which has been preventing me from releasing a 
new version

Original comment by eionrobb on 6 Jun 2013 at 7:36

  • Added labels: Priority-Critical
  • Removed labels: Priority-Medium
I can confirm it works as well. I would have confirmed this a lot earlier but I 
forgot to unmerge the old version portage had installed. 

Original comment by GW.Ke...@gmail.com on 6 Jun 2013 at 7:46

I'm using it on Archlinux, nss 3.14.3, nspr 4.9.6, pidgin/lipurple 2.10.7.

Original comment by haagch.c...@googlemail.com on 6 Jun 2013 at 7:59

[deleted comment]
I tried the dll in post 25, I got 2 or 3 freezes then it worked. It gave me a 
new steam guard code. Logged in fine seems to be working ok now. Not sure what 
caused the initial 3 freezes. Thanks for all your effort hope you can get the 
bugs worked out so everyone can enjoy it. In case it matters I tested it on 
Windows 8 64 bit Version 6.2.9200 Build 9200


Original comment by alec...@gmail.com on 7 Jun 2013 at 6:57

I also just tried the DLL from post 25, no freezes or anything, it just worked 
straight off the bat and looks fine for me. I'm on Windows 7 64-bit version 
6.1, build 7601, SP1. Thanks for all your work!

Original comment by musiKTia...@gmail.com on 7 Jun 2013 at 8:18

Account without steam guard:-
1. Crashed
2. Crashed
3. Crashed
4. Crashed

Account with steam guard:-
1. Worked fine

So, it works fine with steam guard, just, not without. You'd think it'd be the 
opposite, eh?

Original comment by Automati...@gmail.com on 9 Jun 2013 at 8:33

Thanks for the feedback, automatic.coding. What OS was the crash happening on? 
If windows, can you please attach your pidgin.Rpt file from your 
%appdata%/.pidgin folder

Original comment by eionrobb on 9 Jun 2013 at 9:12

For me, it crashed 3 times at various points before starting to work.

Stacktraces are attached.

Original comment by tbj.at...@gmail.com on 10 Jun 2013 at 3:21

Attachments:

:S   Looks like some kind of buffer overflow stack corruption.  Might need to 
run it through valgrind to see what's going on.  Any volunteers for that task 
would be appreciated! :)

Original comment by eionrobb on 10 Jun 2013 at 3:36

I tracked down the crash to the memory allocation during the hexstring->binary 
conversion process from the public key signature.  Couldn't work out exactly 
what's going on, but if anyone wants to try this attached dll, it 'should' do 
the trick

Original comment by eionrobb on 10 Jun 2013 at 6:13

Attachments:

If you can tell me how to do it, I'd be happy to do so. (iirc, valgrind is 
Linux only, so you'll have to help me there).

Something I noticed, when one of my friends logged off and then logged on 
again, the plugin didn't notice they'd logged on again. Not sure if that has 
anything to do with this issue or if I should open a new issue.

Original comment by tbj.at...@gmail.com on 10 Jun 2013 at 6:33

Moved my old .purple folder elsewhere, and tried logging in with the new DLL. 
No crashes for me.

You'd have to get someone that hasn't used it before to be completely sure, but 
it looks like you fixed the crashes.

Thanks a lot. Great work :)

Original comment by tbj.at...@gmail.com on 10 Jun 2013 at 11:37

The -debug dll from #32 works fine for me on Win8 x64. It's a fresh install of 
pidgin on my end.

Original comment by gmattb...@gmail.com on 11 Jun 2013 at 2:48

I've uploaded a v1.2 dll to the Downloads page (a stripped binary of the dll 
from #32).  If someone else can send through some 32bit and 64bit .so's, I'd be 
happy to upload them and close off this issue :)

Big thanks to all those who helped test it :)

Original comment by eionrobb on 15 Jun 2013 at 1:40

I was trying to compile the plugin from the source available to create the 32 
and 64 bit .so files, and I was able to compile successfully!
However, when I attempted to load the plugin, I get this error in Pidgin's 
debug log (via pidgin --debug > debug.log)

$cat debug.log | grep steam
(13:45:00) plugins: probing /home/warren/.purple/plugins/libsteam.so
(13:45:00) plugins: /home/warren/.purple/plugins/libsteam.so is not loadable: 
undefined symbol: json_object_get_boolean_member

I used the provided makefile, and have libjson-glib-dev installed, so I'm not 
sure what is causing the linking to go wrong.

BTW this is on Ubuntu 13.04 Raring Ringtail.

Original comment by warren.p...@gmail.com on 18 Jun 2013 at 9:07

@warren.p.whitman can you upload your .so files to check?  It sounds like 
you're compiling against one version of libjson-glib-dev but running with a 
different version of libjson-glib installed (non-dev package)

Original comment by eionrobb on 19 Jun 2013 at 3:51

Here you are!

I've only attempted to compile a 64 bit version so far, so there's no second 
.so file for 32 bit.

Original comment by warren.p...@gmail.com on 19 Jun 2013 at 8:05

Attachments:

@warren.p.whitman  what version of libjson-glib-dev and libjson-glib do you 
have installed?

Original comment by eionrobb on 19 Jun 2013 at 8:49

@eionrobb The installed versions are both 0.15.2-0ubuntu1:

$apt-show-versions -r libjson-glib*
libjson-glib-1.0-0/raring uptodate 0.15.2-0ubuntu1
libjson-glib-dev/raring uptodate 0.15.2-0ubuntu1

Original comment by warren.p...@gmail.com on 19 Jun 2013 at 8:55

The linux version has the same issue with SteamGuard. I recently updated the 
.so, but now i cannot connect, and no new SteamGuard code is sent.

Original comment by z...@zephmail.co.uk on 19 Jun 2013 at 1:11

I believe I have found the answer! I was looking at other issues where people 
had included json libraries, but were receiving errors that the symbols were 
undefined.
The issue turned out to be that gcc was being told the libraries before it read 
the code, so it would drop all the libraries as they were seen as unnecessary.

I have moved the references in the included makefile around so that the code is 
now defined before the libraries are. Also included is the 64-bit library that 
I compiled an is functional.

Original comment by warren.p...@gmail.com on 23 Jun 2013 at 10:08

Attachments:

Yep, that works. Asked for a code this time.

Original comment by z...@zephmail.co.uk on 24 Jun 2013 at 9:56

I can also confirm the above works for Ubuntu 64 bit as well! Please update the 
downloads section!

Original comment by xylem2...@gmail.com on 26 Jun 2013 at 9:09

32-bit .so compiled on fedora 18 i686.

Original comment by nmBook on 26 Jun 2013 at 11:34

Attachments:

nmBook's 32-bit .so file works for me; it wasn't asking for or sending a code 
before, but after switching in the .so file, it connected properly and sent a 
code.
Only issue now though is that, every time I log out and back in, it fails to 
authenticate, and won't work until I go fetch a new code.
(just in case it matters, I'm using Empathy 2.32.1 on Ubuntu 10.10. Yeah I 
know, stone-age here now.)

Original comment by Geo.devi...@gmail.com on 27 Jun 2013 at 2:02

#43 works for me as well (running Arch Linux 64-bit)

Original comment by darwinpek on 29 Jun 2013 at 7:45

[deleted comment]
[deleted comment]
[deleted comment]
I found that going into accounts.xml and removing the 'access_token' setting 
fixed things for me too. After restarting, I got a new SteamGuard code and used 
it, allowing me to log in again.

So, I guess the answer to the bug is if you get a 4XX error, automatically 
request a new access token. Giving us a menu option to do it manually would 
also be cool.

Original comment by goo...@boffinbrain.com on 22 Nov 2013 at 6:17

Issue 71 has been merged into this issue.

Original comment by eionrobb on 27 Nov 2013 at 8:59

#52 works to prompt for a new code on my computer, but the problem is that 
Steam isn't sending me a new SteamGuard code for Pidgin.  If I'm understanding 
correctly, it should?

I logged into Steam on a different computer and it sent me a new code, so I was 
able to input that code into Pidgin and finally reconnect.

Original comment by ami...@gmail.com on 30 Nov 2013 at 8:30

This should be well and truly sorted now.  Please make sure you have v1.5 of 
the plugin

Original comment by eionrobb on 18 Nov 2014 at 10:53

  • Changed state: Fixed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment