-
Notifications
You must be signed in to change notification settings - Fork 88
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
Comments
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. |
This behavior just started today. |
Now I cannot connect at all. Please take a look at it. |
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? |
Hmmm, I can login with FF without problems |
It normally says "Unsupported Browser" if you try FF .. It has been doing that for years ! |
Sorry, I fake the user agent to Edge 44 on the skype.com domain |
Miranda-NG has the same problem, according to their forum. Edit: There are conflicting reports. Some say it works, others say it does not. |
Actually, they say it works fine on their end. |
Experiencing same issue. Attaching log files. Nothing overtly identifying
|
I looked at the Miranda-NG source and they are passing three cookies to Could that be the problem? |
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. |
@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? |
Same problem here, using "Alternative login method" Failed too with |
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 |
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) |
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)" |
This did not work for me. It says:
|
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 ? |
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... |
1.6 does not work for me 1.5 alt login: "Login error: No handler found for resource (code 40499)" 1.5 non-alt login: "Failed getting Magic T value, please try logging in via browser first" logging in via browser: working good |
@PF4Public : I have the same situation as you. |
@ZaxonXP with the last pidgin version (2.14.1) ? |
I also have |
try to change your ip.. (through VPN, or rebooting your modem/box) |
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 |
Immediately after: "Failed getting PPFT value, please try logging in via browser first" |
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: |
Try logging out from web.skype.com, if it does not help - try registering an Outlook account and logging in with it. |
I use skype name nevertheless. And that's working for me. |
~~I have an outlook account yet trying to log in to skype with my e-mail address is still giving: |
The commit works! Thanks! |
I experienced this behavior with the update also. |
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. |
You should probably switch on "alternative login method" flag in Skypeweb plugin settings. Best regards, |
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, |
If that solves the issue, it should be added to the FAQ. |
Works now with my plain old Skype account, thanks! |
17e03bb and old skype account. |
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 :) |
Just to share: got it working on Fedora Linux with these versions (no 1.7 update): With following steps:
Enabled alt login method and now it works. |
Can confirm it works without outlook address. Just associating any e-mail address with the account was enough. |
Today ver 1.6 does not work again. I tried the version 1.7 and it is working correctly. |
Maybe make that step conditional? |
|
And it's back again. |
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. |
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. |
After multiple reconnection attempts, it will randomly succeed but it can take several minutes of trying.
The text was updated successfully, but these errors were encountered: