[mteamtp] (testing) Exception (mteamtp): Login failed: Selector "a[href="logout.php"]" didn't match: Parse error

[PN62323424]

Have you checked our Troubleshooting page for your issue?

• I have checked the Troubleshooting page

Is there already an issue for your problem?

• I have checked older issues, open and closed

Have you read our Contributing Guidelines?

• I have read the Contributing Guidelines

Environment

none

Description

https://kp.m-team.cc/ This site has been revamped

Logged Error Messages

none

Screenshots

No response

[ilike2burnthing]

@mynameisbogdan are you seeing this as well, or is the issue here user-side?

[mynameisbogdan]

I can confirm they migrated once again, and now I see I can create a API Key in the user CP but there's no docs on how to use it so we'll have to wait for things to settle down.

[chain710]

I can confirm they migrated once again, and now I see I can create a API Key in the user CP but there's no docs on how to use it so we'll have to wait for things to settle down.

I did some research and found that we can request the new API using cookies, and the new API seems to be more easily integrated.

1. login: POST https://kp.m-team.cc/api/login with plain user & pass, return cookie and user id
2. search: POST https://kp.m-team.cc/api/torrent/search, return list of torrents

I opened a PR in another project, and the code is available for reference.

[mynameisbogdan]

Your research didn't considered to support for accounts with 2FA, so I really rather wait for them to document on how to use the API keys.

[garfield69]

While we wait for the API docs to become available (if ever), are there plans to update the html scraper to at least get the two indexers going again?

[mynameisbogdan]

Scraping is not possible anymore. Already took a look at it today and figured out that Cardigann doesn't have support for POST requests with a JSON body, but anyone else if free to take a jab at it until things get definitive.

[chain710]

Your research didn't considered to support for accounts with 2FA, so I really rather wait for them to document on how to use the API keys.

Abount 2FA: is it possible to add a new indexer M-Team Cookie? I've tested the apis work with cookie
There're already other cookie based implementations like YGGcookie

[ilike2burnthing]

https://github.com/Jackett/Jackett/blob/master/src/Jackett.Common/Definitions/mteamtp2fa.yml

[WangEdward]

While we wait for the API docs to become available (if ever), are there plans to update the html scraper to at least get the two indexers going again?

@mynameisbogdan The API docs are available at https://test2.m-team.cc/api/doc.html#/home after you login through https://test2.m-team.cc/

You may need to switch to the second option to see the user APIs

[mynameisbogdan]

Sadly I don't see anything security related on how to use API keys.

[WangEdward]

Sadly I don't see anything security related on how to use API keys.

You can try calling API with the x-api-key header; the API key can be obtained in the user CP. jxxghp/MoviePilot@bd7ca7f is an example of the migration to x-api-key

If the user provides Jackett with their API key, there is no need to maintain 2 versions (2fa) of the app.

[mynameisbogdan]

Thank you, x-api-key works. 👍

[garfield69]

v0.21.2163