Jump to content

Trakt plugin unable to Get PIN


Recommended Posts

Posted

Emby Server 4.9.5.0

Trakt Plugin 3.8.5.0

I've never setup or used this plugin before but I installed it several days ago. Go to my user profile (Emby web) > app settings > user preferences > Trakt.

I see the option for Get Pin. Clicking that link opens a new browser tab at:

https://trakt.tv/oauth/authorize?response_type=code&client_id=...&redirect_uri=urn:ietf:wg:oauth:2.0:oob

(... is some random id that I have redacted)

That page responds with nothing. Looking through the network traffic, I see:

image.thumb.png.bb0019eab280be75f6de930129ec5e01.png

All of the above is with me having previously been signed in with Trakt in this browser. If I clear data for trakt.tv, that URL hits me with a Trakt login prompt but as soon as enter my credentials, the page just spins in Chrome. Safari gives the message "Safari cannot open the page because the address is invalid."

This is with the latest google Chrome and Safari on macOS. Ad blockers disabled.

I could provide server logs but that seems pointless, all of this is happening in a browser from the link Emby provided.

I've tried every day for the last 5 days with no improvement.

  • Agree 1
BlakeJFarber
Posted (edited)

I've been a Emby (with Trakt plugin) user for years, and I'm having the same experience for the last few days.

Noticed watched status hadn’t been syncing from Emby to Trakt for a few days, and on the odd occasion this happens in the past, I simply get a new PIN via 'Get PIN' in Emby server settings. But this time when I click on 'Get PIN' I get routed to this URL, which produces a blank page:

https://trakt.tv/oauth/authorize?response_type=code&client_id=c4eb7ab4ec2ad77255a739f62102bed03a2f56514ab9d20a3001b87f6d465358&redirect_uri=urn:ietf:wg:oauth:2.0:oob

Where typically, I’d see this screen:

https://us1.discourse-cdn.com/flex002/uploads/trakt/original/3X/8/b/8bb57bdacae07cd72a1438fda54d8b93a531d1cb.jpeg

embyserver.txt

Edited by BlakeJFarber
Edited to include log
  • Like 1
  • Thanks 1
Posted

Thanks for the links, yes that looks like the same problem. 

I don't think all app connections with Trakt are broken. I have a couple of Kodi skins that I have successfully connected with Trakt via a PIN in the last few days.

"stupid password-less login"

I could not agree more, I absolutely cannot stand Trakt's new login pattern. Just let me enter my freaking password, you jerks.

Blueskies278
Posted

kodi or jellyfin has no issues. getting a pin

 

Posted

And neither do I in my testing. We'll have to keep an eye on it.

Blueskies278
Posted
1 hour ago, Luke said:

And neither do I in my testing. We'll have to keep an eye on it.

Have you revoked your pin, then try to get a new one?

Posted (edited)
2 hours ago, Luke said:

And neither do I in my testing. We'll have to keep an eye on it.

https://forums.trakt.tv/t/broken-sign-in/117443/5

Quote

Is there a new Emby plugin available? It looks like they are using PIN authentication, but that has been unsupported for years now. Here is what should happen:

Emby generates and display a code in their app
You go to https://trakt.tv/activate and enter that code
Emby refreshes and you’re connected

Hopefully there is a new plugin with the correct type of device authentication. If not, Emby needs to update the plugin to use device authentication.

I'm using the latest Emby plugin. 

Edited by signde
Posted
2 hours ago, Blueskies278 said:

Have you revoked your pin, then try to get a new one?

I have the problem, tried what you said and all i get is a black web page.

  • Agree 1
Posted

Same here get pin goes nowhere. And from Trakts forums I found this:
 

justinDirector
2h
 

Is there a new Emby plugin available? It looks like they are using PIN authentication, but that has been unsupported for years now. Here is what should happen:

  • Emby generates and display a code in their app
  • You go to https://trakt.tv/activate and enter that code
  • Emby refreshes and you’re connected

Hopefully there is a new plugin with the correct type of device authentication. If not, Emby needs to update the plugin to use device authentication.

  • Like 1
Posted (edited)

I just tried the new plugin 3.8.6.0 plugin and still get a blank screen

Edited by locutus
  • Agree 1
Blueskies278
Posted (edited)

Tried jellyfin Authorised without issue. jellyfin's Trakt plugin uses the modern Device Authorization flow (/oauth/device/code)

Emby's built-in Trakt plugin uses the old, legacy PIN flow.

Edited by Blueskies278
Posted

Could not wait for Emby to fix their outdated legacy PIN flow. I got Trakt working again. I'm in the middle of two plugin projects — this was holding me back. Not sure when Emby are going to realise their outdated legacy PIN flow urgently needs updating.

Posted

I am using Version 4.10.0.20 beta, with Trakt plugin V 3.8.6. When I click on get PIN a browser window opens with this url:  https://trakt.tv/oauth/authorize?response_type=code&client_id=<user_id>&redirect_uri=urn:ietf:wg:oauth:2.0:oob -  (I replaced user_id) and I get a blank page. According to what I found :oauth:2.0:oob is obsolete for logging in to Trakt. 

In other words, I'm locked out from using the Trakt plugin till the plugin is updated.

devsky88
Posted

Definitely not related to the 1 app authorization. I have VIP and have for years and have the same issue. Definitely an issue with using an authentication method that Trakt no longer supports.

Posted

I also have this issue and my watch history hasn't updated since 16 July

devsky88
Posted

Any updates when we can expect an update for this? Seems now that the plugin is completely broken until it is updated.

Blueskies278
Posted

Well, according to Luke, he doesn't have this issue. The moment he said that, I fixed it myself.

devsky88
Posted
7 minutes ago, Blueskies278 said:

Well, according to Luke, he doesn't have this issue. The moment he said that, I fixed it myself.

Yeah I saw that. There isn't any way he's not having this issue now. Trakt has said that's no longer supported. I had to change to a third party Emby player to continue to use Trakt until it gets fixed. @Lukechecking in to see if your now having this issue.

yingste
Posted

Will add, mine also stopped updating sometime last week (12-13th). No changes in sign-in on my end. Both Jellyfin and PlexTraktSync appear to be updating without any intervention on my part. 
 

2026-07-17 00:01:43.500 Info HttpClient: Http response 400 from https://api.trakt.tv/oauth/token after 84ms
2026-07-17 00:01:43.503 Error Trakt: Exception handled sending status update
	*** Error Report ***
	Version: 4.9.5.0
	Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
	Operating system: Linux version 7.0.0-27-generic (buildd@lcy02-amd64-114) (x86_64-linux-gnu-gcc (Ubuntu 15.2.0-16ubuntu1) 15.2.0, GNU ld (GNU Binutils for Ubuntu) 2.46)
	OS/Process: x64/x64
	Framework: .NET 8.0.25
	Runtime: opt/emby-server/system/System.Private.CoreLib.dll
	Processor count: 28
	Data path: /var/lib/emby
	Application path: /opt/emby-server/system
	MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: BadRequest
	   at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod)
	   at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsync(HttpRequestOptions options, String httpMethod)
	   at Trakt.Api.TraktApi.GetResponseFromTrakt(HttpRequestOptions options, String method, CancellationToken cancellationToken)
	   at Trakt.Api.TraktApi.PostToTrakt(String url, Object data, TraktUser traktUser, CancellationToken cancellationToken)
	   at Trakt.Api.TraktApi.RefreshUserAuth(TraktUser traktUser, CancellationToken cancellationToken)
	   at Trakt.Api.TraktApi.SetRequestHeaders(HttpRequestOptions options, TraktUser traktUser, CancellationToken cancellationToken)
	   at Trakt.Api.TraktApi.PostToTrakt(String url, Object data, TraktUser traktUser, CancellationToken cancellationToken)
	   at Trakt.Api.TraktApi.SendEpisodeStatusUpdateAsyncInternal(List`1 episodeDatas, MediaStatus status, TraktUser traktUser, CancellationToken cancellationToken)
	   at Trakt.Api.TraktApi.SendEpisodeStatusUpdateAsync(Episode episode, MediaStatus status, TraktUser traktUser, Single progressPercent, CancellationToken cancellationToken)
	   at Trakt.ServerMediator._sessionManager_PlaybackProgress(Object sender, PlaybackProgressEventArgs e)
	Source: Emby.Server.Implementations
	TargetSite: Void MoveNext()

 

Blueskies278
Posted (edited)
1 hour ago, yingste said:

Will add, mine also stopped updating sometime last week (12-13th). No changes in sign-in on my end. Both Jellyfin and PlexTraktSync appear to be updating without any intervention on my part. 
 

2026-07-17 00:01:43.500 Info HttpClient: Http response 400 from https://api.trakt.tv/oauth/token after 84ms
2026-07-17 00:01:43.503 Error Trakt: Exception handled sending status update
	*** Error Report ***
	Version: 4.9.5.0
	Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
	Operating system: Linux version 7.0.0-27-generic (buildd@lcy02-amd64-114) (x86_64-linux-gnu-gcc (Ubuntu 15.2.0-16ubuntu1) 15.2.0, GNU ld (GNU Binutils for Ubuntu) 2.46)
	OS/Process: x64/x64
	Framework: .NET 8.0.25
	Runtime: opt/emby-server/system/System.Private.CoreLib.dll
	Processor count: 28
	Data path: /var/lib/emby
	Application path: /opt/emby-server/system
	MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: BadRequest
	   at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod)
	   at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsync(HttpRequestOptions options, String httpMethod)
	   at Trakt.Api.TraktApi.GetResponseFromTrakt(HttpRequestOptions options, String method, CancellationToken cancellationToken)
	   at Trakt.Api.TraktApi.PostToTrakt(String url, Object data, TraktUser traktUser, CancellationToken cancellationToken)
	   at Trakt.Api.TraktApi.RefreshUserAuth(TraktUser traktUser, CancellationToken cancellationToken)
	   at Trakt.Api.TraktApi.SetRequestHeaders(HttpRequestOptions options, TraktUser traktUser, CancellationToken cancellationToken)
	   at Trakt.Api.TraktApi.PostToTrakt(String url, Object data, TraktUser traktUser, CancellationToken cancellationToken)
	   at Trakt.Api.TraktApi.SendEpisodeStatusUpdateAsyncInternal(List`1 episodeDatas, MediaStatus status, TraktUser traktUser, CancellationToken cancellationToken)
	   at Trakt.Api.TraktApi.SendEpisodeStatusUpdateAsync(Episode episode, MediaStatus status, TraktUser traktUser, Single progressPercent, CancellationToken cancellationToken)
	   at Trakt.ServerMediator._sessionManager_PlaybackProgress(Object sender, PlaybackProgressEventArgs e)
	Source: Emby.Server.Implementations
	TargetSite: Void MoveNext()

 

I also uploaded my Emby log, which mirrors yours, and Luke pretty much brushed it off, not having an issue with his testing.

Hopefully the emby team can resolve this bug soon.

Edited by Blueskies278
  • Agree 2
Posted

Looks like they updated Trakt to version 3.8.8 but it didn't make any difference in fixing the issue that it's having. 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...