Skip to content
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

Getting "failed to get magic-T" error even when logged in via browser #656

Closed
alexolog opened this issue Aug 19, 2020 · 67 comments
Closed

Comments

@alexolog
Copy link

After multiple reconnection attempts, it will randomly succeed but it can take several minutes of trying.

@dlmarquis
Copy link

I am having the same problem. This week I started having to log in via browser every time I changed IP address; now I can't get in even when logged in via browser.

@Zombie-Ryushu
Copy link

This behavior just started today.

@alexolog
Copy link
Author

Now I cannot connect at all.

Please take a look at it.
I use a different Skype account in Pidgin so I rely on it for communications.

@neil969
Copy link

neil969 commented Aug 19, 2020

This has just started to happen to me too today .. Looks like Skype have changed something.. I can also say that when I try to login using Firefox but changing the user agent to Chrome ( which used to work to allow a log in to fix the Magic T issue) Skype gives an error and wont log in. It will log in on (de-googled) Chromium browser though, but I still get the issue in Pidgin. I imagine that this is related and Web.Skype may be using some new form of browser check?

@alexolog
Copy link
Author

Hmmm, I can login with FF without problems

@neil969
Copy link

neil969 commented Aug 19, 2020

Hmmm, I can login with FF without problems

It normally says "Unsupported Browser" if you try FF .. It has been doing that for years !

@alexolog
Copy link
Author

Sorry, I fake the user agent to Edge 44 on the skype.com domain

@alexolog
Copy link
Author

alexolog commented Aug 19, 2020

Miranda-NG has the same problem, according to their forum.
Microsoft did something.

Edit: There are conflicting reports. Some say it works, others say it does not.

@zevelorgani
Copy link

Miranda-NG has the same problem, according to their forum.
Microsoft did something.

Actually, they say it works fine on their end.

@DeRiderConsultingServices
Copy link

DeRiderConsultingServices commented Aug 20, 2020

Experiencing same issue. Attaching log files. Nothing overtly identifying

(19:12:29) http: Request 02306870 performed successfully.
(19:12:29) g_log: skypeweb_string_get_chunk: assertion `chunk_start' failed
(19:12:29) g_log: skypeweb_string_get_chunk: assertion `chunk_start' failed
(19:12:29) g_log: skypeweb_string_get_chunk: assertion `chunk_start' failed
(19:12:29) connection: Connection error on 0390AC48 (reason: 2 description: Failed getting Magic T value, please try logging in via browser first)

[DebugLog.txt](https://github.com/EionRobb/skype4pidgin/files/5099964/DebugLog.txt)

@alexolog
Copy link
Author

I looked at the Miranda-NG source and they are passing three cookies to https://login.live.com/ppsecure/post.srf: MSPRequ, MSPOK, and CkTst, while Pidgin only passes CkTst

Could that be the problem?

@DeRiderConsultingServices

That could definitely be a source. Definitely worthy of testing if one has both the knowledge, the time and the ability to build the skype plugin from the source.

@boris-petrov
Copy link
Contributor

@alexolog - if Miranda has the same problem then probably these cookies don't matter (that much). Would you mind linking to their issue here?

@neil969
Copy link

neil969 commented Aug 20, 2020

@alexolog - if Miranda has the same problem then probably these cookies don't matter (that much). Would you mind linking to their issue here?

I have had a dig through the issues at Miranda, (forum & Github) but I can't see that they have a an issue with NOT connecting ( maybe an issue with "remaining* connected) with web.skype , so maybe the issue is the two extra cookies?

@SullyvanCrow
Copy link

SullyvanCrow commented Aug 20, 2020

Same problem here, using "Alternative login method" Failed too with
"Login error: No handler found for resource (code 40499)" message

@EionRobb
Copy link
Owner

Using alternate auth with the latest version of the plugin is always preferred, but I'm looking into the "pretend to be a web browser" method too

It looks like it's hitting the "do you want to store these details / stay logged in" screen and getting stuck. There should be one more screen to pretend to click through for the old login method to work

@SullyvanCrow
Copy link

updating pidgin to the latest version and the plugin from 1.5 to 1.6 seems to solve the login problem (with alternative auth method)

@neil969
Copy link

neil969 commented Aug 20, 2020

Using alternate auth with the latest version of the plugin is always preferred, but I'm looking into the "pretend to be a web browser" method too

I have never managed to get anything but an error when I check " Alternative login method" - currently that error is "Login error: No handler found for resource (code 40499)"
So currently it is either that error or the "magic T" error ... At least it is now consistent :)

@ZaxonXP
Copy link

ZaxonXP commented Aug 20, 2020

updating pidgin to the latest version and the plugin from 1.5 to 1.6 seems to solve the login problem (with alternative auth method)

This did not work for me. It says:

Login error: Bad username or password (Profile accrual is required)

@SullyvanCrow
Copy link

updating pidgin to the latest version and the plugin from 1.5 to 1.6 seems to solve the login problem (with alternative auth method)

This did not work for me. It says:

Login error: Bad username or password (Profile accrual is required)

Is the loging ok on the web version of Skype ?

@ZaxonXP
Copy link

ZaxonXP commented Aug 20, 2020

Is the loging ok on the web version of Skype ?

No, it is not. That is why I tried the alternative, but it also did not work for me.

@SullyvanCrow
Copy link

Is the loging ok on the web version of Skype ?

No, it is not. That is why I tried the alternative, but it also did not work for me.

are you sure of your login/password ?

@neil969
Copy link

neil969 commented Aug 20, 2020

OK I can confirm that the the 1.6 fixed the "Login error: No handler found for resource (code 40499)" when using the alt login method, and I am back connected to Skype again...
I REALLY thought I had the most recent version so sorry about that @EionRobb - I think I may have had a beta version from like January .
so "BEFORE DOING ANYTHING ELSE Grab the latest DLL (1.6) from here https://github.com/EionRobb/skype4pidgin/releases & drop it into the plugins directory and restart pidgin with "Alternative login" check as on! :)

@PF4Public
Copy link
Contributor

PF4Public commented Aug 20, 2020

1.6 does not work for me

1.5 alt login: "Login error: No handler found for resource (code 40499)"
1.6 alt login: "Login error: Bad username or password (Profile accrual is required)"

1.5 non-alt login: "Failed getting Magic T value, please try logging in via browser first"
1.6 non-alt login: "Failed getting Magic T value, please try logging in via browser first"

logging in via browser: working good

@ZaxonXP
Copy link

ZaxonXP commented Aug 20, 2020

@PF4Public : I have the same situation as you.
@SullyvanCrow : Yes, I put my login/pass correctly (tried few times).

@SullyvanCrow
Copy link

@ZaxonXP with the last pidgin version (2.14.1) ?

@konto-andrzeja
Copy link

I also have Login error: Bad username or password (Profile accrual is required) error when trying alt method with 1.6 plugin version and 2.14.1 Pidgin version. Can log in using web just fine, so login and password are correct. Tried to verify recent activities as suggested here, but it didn't help.

@SullyvanCrow
Copy link

try to change your ip.. (through VPN, or rebooting your modem/box)

@brianjmurrell
Copy link

@EionRobb

Using alternate auth with the latest version of the plugin is always preferred, but I'm looking into the "pretend to be a web browser" method too

Except that doesn't work using 1.6: Login error: Bad username or password (Profile accrual is required)

@kosilin
Copy link

kosilin commented Aug 24, 2020

@EionRobb

Using alternate auth with the latest version of the plugin is always preferred, but I'm looking into the "pretend to be a web browser" method too

Except that doesn't work using 1.6: Login error: Bad username or password (Profile accrual is required)

Please try to confirm your e-mail from the PC where the skypweb is working on (please see my post a little bit earlier) before using alternative skype login.

Alexey

@PF4Public
Copy link
Contributor

Windows dll
libskypeweb.zip

Immediately after: "Failed getting PPFT value, please try logging in via browser first"
After logging in via browser: "Failed getting Magic T value, please try logging in via browser first"

@brianjmurrell
Copy link

I added an e-mail address to the MS account that I use for skype and reconfigured Pidgin to use that instead of my skype name and now login is still failing with: Login error: Bad username or password (Profile accrual is required)

@vrobolab
Copy link

Try logging out from web.skype.com, if it does not help - try registering an Outlook account and logging in with it.

@kosilin
Copy link

kosilin commented Aug 24, 2020

I added an e-mail address to the MS account that I use for skype and reconfigured Pidgin to use that instead of my skype name and now login is still failing with: Login error: Bad username or password (Profile accrual is required)

I use skype name nevertheless. And that's working for me.

@brianjmurrell
Copy link

brianjmurrell commented Aug 24, 2020

~~I have an outlook account yet trying to log in to skype with my e-mail address is still giving: Login error: Bad username or password (Profile accrual is required)~~Now it works. I guess there must be some delay between adding an e-mail address to one's MS account and it being usable with skype4pidgin.

@dazzzl
Copy link

dazzzl commented Aug 24, 2020

The commit works! Thanks!

@DeRiderConsultingServices

Immediately after: "Failed getting PPFT value, please try logging in via browser first"
After logging in via browser: "Failed getting Magic T value, please try logging in via browser first"

I experienced this behavior with the update also.

@vrobolab
Copy link

The big one - I do not receive new messages (they do not sync?).

If I login with the browser to https://web.skype.com there are several new messages in different chats, and no such messages in Pidgin.

Update: I send and receive messages without problems, i.e. if I send in browser then the same message appears in Pidgin, and replies received do appear in Pidgin too. So no issues with syncing messages after logging in with the browser. But those several messages I was talking above have never appeared in Pidgin.

So make sure to log in with the browser first, to see any new messages that came while you was offline in Pidgin.

@kosilin
Copy link

kosilin commented Aug 24, 2020

Immediately after: "Failed getting PPFT value, please try logging in via browser first"
After logging in via browser: "Failed getting Magic T value, please try logging in via browser first"

I experienced this behavior with the update also.

You should probably switch on "alternative login method" flag in Skypeweb plugin settings.

Best regards,
Alexey

@DeRiderConsultingServices

Immediately after: "Failed getting PPFT value, please try logging in via browser first"
After logging in via browser: "Failed getting Magic T value, please try logging in via browser first"

I experienced this behavior with the update also.

You should probably switch on "alternative login method" flag in Skypeweb plugin settings.

Best regards,
Alexey

That produces the Profile acrual error. And the account is already linked to a MS account because they forced us to do create this Skype account when they migrated everybody over from MSN to skype.

@kosilin
Copy link

kosilin commented Aug 24, 2020

That produces the Profile acrual error. And the account is already linked to a MS account because they forced us to do create this Skype account when they migrated everybody over from MSN to skype.

Yeah. This was producing the similar error for me too 'till I did some magic with my mslive account. Please see my post and try to do something like this.

Best regards,
Alexey

@alexolog
Copy link
Author

If that solves the issue, it should be added to the FAQ.

@bodqhrohro
Copy link
Contributor

Works now with my plain old Skype account, thanks!

@zod6
Copy link

zod6 commented Aug 25, 2020

17e03bb and old skype account.
With new version everything is fine!

@EionRobb
Copy link
Owner

Thanks everyone for the testing and feedback.

I've pushed out a new release at https://github.com/EionRobb/skype4pidgin/releases/tag/1.7 - hopefully should start trickling out to distros at some point :)

@ohhai
Copy link

ohhai commented Aug 27, 2020

Just to share: got it working on Fedora Linux with these versions (no 1.7 update):
pidgin-2.13.0-18.fc32.x86_64
pidgin-skypeweb-1.6-1.fc32.noarch

With following steps:

Enabled alt login method and now it works.

@heeplr
Copy link

heeplr commented Aug 27, 2020

Can confirm it works without outlook address. Just associating any e-mail address with the account was enough.

@ZaxonXP
Copy link

ZaxonXP commented Sep 24, 2020

Today ver 1.6 does not work again. I tried the version 1.7 and it is working correctly.

@alexolog
Copy link
Author

Maybe make that step conditional?

@bodqhrohro
Copy link
Contributor

Maybe make that step conditional?

Done.

New .deb package.

@H0w4rd
Copy link

H0w4rd commented Oct 11, 2021

And it's back again.
Failed getting Magic T value, please try logging in via browser first
Suggested action won't help.
Any solution for 2021? :-)

@H0w4rd
Copy link

H0w4rd commented Oct 12, 2021

Sorry, there seems to be no problem, only that there is an old version 1.2.2 in openSUSE repos. I had to git clone this project and compile it. Now it is working.

@dreamlayers
Copy link

dreamlayers commented Oct 14, 2024

Now, October 14th 2024, with the latest version, I am only able to log in if I am logged in via the browser. If I log out via the browser, then I get "failed to get magic-T" in Pidgin. Fortunately, it still works if I close the browser tab without logging out. I don't think this was needed before.

Edit: Next morning, I again got "failed to get magic-T" in Pidgin. This time when I logged in via the browser, I got "We're updating our terms". Maybe accepting that will fix the problem, like before. It's surprising I didn't get that when I logged in via the browser yesterday.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests