I have the same issue, keep getting logged out… like why? A site to track watching habits is not even remotely a high tier of security vs like a banking site etc.
I agree. Thankyou for taking the trouble to register to post that. I hope it has an effect.
Radio silence from Team Trakt about all this login kerfuffle so far. I’m not expecting anything to change. They’re clearly set on this passwordless future 
+1 on the vote for adjusting this feature (making it workable)
I’m not against security (I actually work in a security related job in the financial sector)… but it just does not work… I’m unable to login on the webpage with the mail-link… it ends up in the loop to the intro app page… very annoying… removing cache, removing cookies, nothing works…
As soon as security becomes a hurdle, people will try to get around it (or just leave)…
I would advise to do a proper risk assessment and take measures in light of this risk… (as they do in banking) and NOT go for the safest option out there (risk management does not equal risk avoidance)
istg this feature is driving me crazy
+1, let me use my autofilled strong password or even better a passkey.
I don’t have my personal emails set up on the computer I use.
Especially tiring with Keep getting Logged Out
Please just let me use my password, I’ve been a member since 2015 and your making me hate this platform.
I wish I found this thread before emailing the team.
I would like passwords to return. There are many reasons for keeping password authentication.
Not everyone’s password will be “123456” (but the code you mail might be)
The sending provider’s IP (who sent your code by email) is 54.240.11.180, which is on several email blacklists. Imagine a frustrated user who doesn’t get the email, because your network is blocked.
Sometimes, people lose permanent access to their email. Even if they know their password, they’re locked out.
Email is insecure, not encrypted. A clever attacker could easily brute force every account with the right knowledge.
You’ve now created a security risk where phishers could say “Please verify your account with a code” and while Trakt.com doesn’t necessarily have anything too sensitive, it’s still bad practice.
You’ve created several points of failure in the login process. Your sending server, the several hops in between, and the receiving server.
And at least a dozen other things I shouldn’t mention, since saying such things would be a violation of the site’s terms.
Bring passwords back.
“Hello sir, this is John from Technical Support. I am sending you a code now for verifying your account for receiving support.”
But at least the random string I use only on one website is safe. 
Is it possible to link a Google account to an existing Trakt account? This would be a sensible compromise. I don’t want to click on “login using Google” to try because I don’t want to risk creating a second account and sinking even deeper.
For the Apple SSO, if you use the same email, it won’t create a second account, but will make the link between your account and this authentication method. I’d try logging in with Google if I was you (and again using the same email both on the google account when you click login, and in the trakt account)
I’ll align email addresses and try. Thank you.
Just chiming in to validate every single aspect of your experience, and it seems like we seem to have a lot of similarities in our implementation approaches, at least as regards email. The complete unpredictability of whether or not the message will arrive, and whether or not it will occur before or after the expiration of the code, is like some puerile, asinine joke. I, too, haven’t bothered to try a different email account since I see no evidence that the issue is caused by anything but a poor implementation of the service rather than some edge case incompatibility between the two servers.
I don’t know the level of visibility you have into your setup, but my host allows me to tail my IMAP server logs in real-time, and I can say with certainty that at least some of the time that I click the button to send the code, either no message is sent at all or it is so malformed that it is lost en route, because there won’t even be a connection attempt from the servers that I see when a code is sent; it’s been years since deliverability has been an issue for me, no matter the sender. The real punchline though, for me at least, is that on a few occasions now when the code has arrived prior to expiration and I’ve entered it into the login page, it fails to generate the cookie and I’m back looking at the login page despite seeing no error message.
I’m truly at a loss to explain how a web site which I held up for years as the paragon of web design form and functionality has completely wrecked itself at such a fundamental level. To have gone from barely ever needing to login to the old site and it being absolutely effortless when I did…to what can only be described as an authentication circus has to be a grave failure on many levels. If this sort of “zero-trust” system is what the site prefers, I only find that tolerable as far as the former username and password system remains available as an opt-in mode for those it suited better, such as myself.
Other thoughts I wish to share, though not directly related to the login issues
In truth, though, my weighing in here at all (against my better judgment) is mostly to exhort those in charge to do better by their users at least in this most basic function. When the V2 site was decommissioned, I cancelled my decade-long VIP subscription and am slowly making my peace with what the site has chosen to become. Currently the only thing that calls me back here is when I get a email about a reply to one of my comments here that I wish to engage with further. While I would’ve enjoyed do that today, my first request for a login code never arrived, and when the second did, it didn’t create a valid cookie and I was back at square one, though for reasons passing understanding it was successful at refreshing my forum login. 
I’m going to miss an awful lot of people from here. This was a really unique community that brought together a ton of people with fascinating insights and the precious ability to communicate them very artfully, such that I never felt like I’d fully examined a piece of media I’d watched until I read the comments about it here. I can only hope that in the purest spirit of the internet, our paths will cross again at the next site to successfully scratch this particular itch.
I’ve been here since the “Kale for Justin” days and up until very recently, I would never have described that as anything but a privilege. Trakt wasn’t just a source of convenience in my media consumption, but it exposed me to things I would never have found on my own that were spectacular experiences, often with the added benefit of people to interact with who felt similarly about them. Best of all, using it was fun. That my time here so nearly coincided with my evolution as a frontend software developer was itself a source of satisfaction, as I would watch this site evolve in ways both big and small and often think to myself, “I’ll know I’ve achieved some mastery at this work when I make something that looks and behaves like this.” The question has come up in at least two job interviews now of which site best exemplified my own design philosophy and both times without hesitation I cited Trakt.
I’m now far enough into my career that I accept that web sites are economic engines at heart and not the canvases for artistic expression I still desperately wish they were, so I’ll spare everyone the impassioned, excoriating remarks I would otherwise let fan out broadly under the circumstances. And to whoever’s calling the shots now, though you’ve thoroughly massacred something I once loved, I hope these decisions are validated by the eventual outcomes; the only way for me to be more displeased about all this would be learning down the road that it all got torn down for nothing. That said, there have only been a few times in my life that I wanted to do this to someone more than I do now over the choices that led to all this…
