Jackett: [teamhd] Login Failed, got redirected. (Config)

[Prosecutor]

Hey! Getting this type of error

Jackett version: 0.12.1582.0

Error:

Jackett.Common.ExceptionWithConfigData: Login Failed, got redirected. at Jackett.Common.Indexers.CardigannIndexer.TestLogin() in /home/appveyor/projects/jackett/src/Jackett.Common/Indexers/CardigannIndexer.cs:line 788 at Jackett.Common.Indexers.CardigannIndexer.ApplyConfiguration(JToken configJson) in /home/appveyor/projects/jackett/src/Jackett.Common/Indexers/CardigannIndexer.cs:line 949 at Jackett.Server.Controllers.IndexerApiController.UpdateConfig(ConfigItem[] config) in /home/appveyor/projects/jackett/src/Jackett.Server/Controllers/IndexerApiController.cs:line 94 at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfIActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask`1 actionResultValueTask) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited|19_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope) at Microsoft.AspNetCore.Routing.EndpointMiddleware.g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger) at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context) at Microsoft.AspNetCore.Builder.Extensions.UsePathBaseMiddleware.Invoke(HttpContext context) at Jackett.Server.Middleware.CustomExceptionHandler.Invoke(HttpContext httpContext) in /home/appveyor/projects/jackett/src/Jackett.Server/Middleware/CustomExceptionHandler.cs:line 73

[jackettbot[bot]]

Duplicate of #6661

Hi @Prosecutor,

This issue looks similar to #6661.

To prevent issue tracker clutter, this issue will now be closed. If you feel this issue isn't a duplicate of #6661, then feel free to post a comment on this issue stating why it's not a duplicate. Your comment will automatically re-open this issue.

[Prosecutor]

It's not a dupe. The Jackett is hosted on the same server from which I'm loggined to the tracker.

https://prnt.sc/qpaukj

[garfield69]

is this the first time you are adding the teamhd indexer to Jackett?

[Prosecutor]

@garfield69 Yes, exactly.

[garfield69]

you opened #5728 previously but did not get a solve...
Are you now able to open a browser on the same jackett machine to copy the cookie with the same ip address as jackett?
@n-ozerov is this indexer working for you?

[Prosecutor]

@garfield69 It was solved. That was on my previous Dedi with other account, also that error was just related with captcha.

I’ve mentioned, that I’m doing it from the same machine where jackett is located and getting this type of error.

[n-ozerov]

@garfield69

I'm getting same error when trying to login via cookies. I'm pretty much sure that cookies become invalid when user agent changes because every browser update drops session.

Is there a way to set user agent in definition?

[garfield69]

easy enough to test.
so shutdown your jackett service and edit the teamhd.yml indexer and add the following

    headers:
      User-Agent: ["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.117 Safari/537.36"]

just after the Search: key, replacing the useragent keyword and string with whatever one your browser is using when you grab your cookie
startup the service and test.

if it works I can amend the indexer to add a config option so you can update it at the same time you update the cookie.

[n-ozerov]

Maybe i'm doing smth wrong, still getting redirect. :(

But i'm pretty sure login depends upon user-agent.

[garfield69]

i've a couple indexers that use
https://github.com/Jackett/Jackett/blob/593680f8d3390d43da3e353002575d746e699f21/src/Jackett.Common/Definitions/torrentquest.yml#L44-L46

[dimqua]

  search:
    headers:
      User-Agent: ["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.117 Safari/537.36"]
      Accept: ["text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8"]  

It doesn't work for me either.

[garfield69]

beyond my skills. open to volunteers who can help.

[Lonli-Lokli]

@n-ozerov You should change user-agent within your browser (from which you are copying the cookie) to the same user agent as Jackett use. On details how it can be done you can follow steps 2 & 3 from https://github.com/Jackett/Jackett/issues/6070#issuecomment-545607603

[Prosecutor]

@Lonli-Lokli How to do it in Chrome?

I added in teamhd.yml file these lines and still getting an error.

Same user agent uses jackett/teamhd.

headers:
      User-Agent: ["Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.122 Safari/537.36"]

[Lonli-Lokli]

@Prosecutor You should follow this instructions https://winaero.com/blog/change-user-agent-chrome/ and set custom user agent, same as in teamhd.yml, before fetching the cookie.

[Prosecutor]

@Lonli-Lokli Still not working for me.

https://prnt.sc/r8oll3

https://prnt.sc/r8olr1

https://prnt.sc/r8olcj

[janot]

@Prosecutor works on my side

I'm not sure if exact steps matter, but here they are:

• open teamhd
• logout
• change user-agent to Jackett's (you have to use user-agent from your installed Jackett's version, not from this thread) in Chrome dev tools
• delete all teamhd cookies and ctrl+f5
• log in teamhd and get cookie as usual

Looks like

search: headers: User-Agent:

doesn't work. I've checked that Jackett's user agent still remains the same.
Probably because of this: #7786
upd: actually, setting user-agent this way was never supported by Jackett https://github.com/Jackett/Jackett/issues/7786#issuecomment-616613811

[Prosecutor]

@janot Does not works for me. I'm logging TeamHD where jackett is running(same machine), so the User-Agent is exactly the same for both of them, no need to change them.

[janot]

@Prosecutor No, Jackett has it's own user-agent which is hardcoded:
https://github.com/Jackett/Jackett/blob/3f01a615108f08e6665c6702590c513e19725ed4/src/Jackett.Common/Utils/BrowserUtil.cs#L9-L11
There's link in my previous comment to the issue exactly about that.

[Prosecutor]

@janot Yep, it works.

[Erythros]

Ended up facing the same issue. Since it's still open, is there a solution for this?