[turktorrent] (updating) Login failed: Selector "div#member_info_bar" didn't match about jackett HOT 10 CLOSED

The login selector didn't match is a sign that TurkTorrent rejected the cookie you used as not valid to represent Jackett as a session continuation of the browser session you used to fetch the cookie.
TurkTorrent are using cloudflare for DDoS protection so I would have expected the cookie you fetched to have contained a cf_clearance cookie string. Is this not the case?

from jackett.

Hi @garfield69
I've pressed F12 and copied the values from the request cookie as is.
I don't think TurkTorrent.us uses CloudFlare DDoS protection (BitTurk.net does and that one works with FlareSolverr configured).
It does have an annoying puzzle you need to solve where you need to match the animals, perhaps thats the problem.
I have attached a screenshot of the cookies here:

from jackett.

I normally visit the sites torrent browse page and fetch my cookie from there.
If you have passed on the browser any kind of challenge, then the cookie should contain a clearance for that challenge.
Without it Jackett will not pass the cookie session match, and turktorrent will re-issue the challenge which is what is prevent Jackett from seeing the login selector post login check.

from jackett.

Well I guess the clearance and login session should all be stored in tsue_member then.
Because when I browse the list of torrents, the cookie stays the same.
If you (or any other developer) would like to try it out, I could send over my login details in a PM.

from jackett.

ok. you have not mentioned anyplace that you also copied over the useragent. did you do that too?

from jackett.

Yes, that field is also required.
I have more trackers requiring cookies, including the user agent string, like IPT and TD and they work fine.
I suspect its a recent change to the turktorrent.us website that broke it.

Edit sorry different account

from jackett.

and you are using a browser on the same machine that is running Jackett, i.e. same ip address?

from jackett.

well at first I didn't, so I setup a dynamic (socks5) SSH tunnel to the server running Jackett and made sure to verify I'm connecting using the same public IP by checking www.whatismyip.com.
I then proceeded to login once more, but the cookie value stays the same and I'm still getting the same error message when trying to add it to Jackett.

from jackett.

@ilike2burnthing at this point I'm out of suggestions and would welcome your input. Thanks.

from jackett.

Nevermind I got it to work :)
It seems I had to properly decode the %3D%3D part to == of the tsue_member value.
Furthermore I need to leave out the other two values tsue_guest_language=1 and shoutboxChannelID=1.

from jackett.