Getting this message on edge and chrome. Initially thought it was Edge since the next click shows safari, chrome, and firefox, but chrome also has this problem.
Not sure what was going on but now Chrome is working (after the page self reloaded 5 times).
Same problem with Samsung’s native web browser. This is a deal breaker for me. I have no interest in using chrome even on desktop or bloat my phone with a bunch of browser apps. I am using what came with my flagship Galaxy S-series phone and it is up to date with the Samsung store. It looks like someone dropped the ball thinking everyone has to use the few web browsers that they are familiar with and hard block everything else.
Well Chrome is broken again. No clue what these people are doing but it’s sad.
What happens when people cant code properly. Seen it in many places where there is a primary browser that everything works on and nothing is guaranteed on anything else. That’s always internal to a company or agency so it’s controlled. For the public it’s unacceptable.
@YasharF WAF rules have been updated to account for Samsung’s underlying engine.
Thanks for the report ![]()
Same message still popping up here on Chrome.
check your chrome version to see if its compatible. go to chrome://version if its less than 140 then it needs to be updated. If you’re still getting that unsupported browser error, do you have any browser addons that you can disable?
@RoiDesRois Do you have any browser addons/extensions that you can disable? I was able to log in on Chrome, Edge, and Firefox with no problem and I’m also able to use my phone Safari, Chrome, Firefox, and Edge so I’m not sure why it’s not working on your end. I saw you already posted your browser versions as well
I got the same message on the most current version of firefox. Let’s just see how many more ways they can ruin their site
it only seems to be affecting a few people since I’ve been able to use the site on all the browsers I listed that everyone is having problems on, I’m not sure its something on their end at that point
I’ve kept it all on a single device (iPad) to make troubleshooting consistent. There are no extensions.
why are you guys blocking lower then Chrome 139 users
From other issues (ui/ux, loading, etc.) I’ve been reading on here, there seems to be browser specific or device specific issues.
Hopefully they understand that codebase doesn’t make all chromium or safari webkit based browsers the same. Something can work solely in one browser and not another.
not browser specific or device specific issue they blocking specify range user agents
From reddit for browser support.
Really love paying for a service I can’t access. I guess that’s a call to my bank. Trakt obviously didn’t think I paid so why bother.
![]()
sign out, then sign in using https://trakt.tv/signin and that should fix the issue. it used to do that to me until i signed in that way
Not sure if that was to me or blackheart321. I did try that way and it didn’t change the behavior.


