Not connecting to plex - not sure what's going on

[Greenysmac]

The first time I installed this, for a couple of weeks (somewhere around 2.10 or so), this was working wonderfully. About three weeks ago, or so, it stopped functioning. Recently, I completely removed this plugin and reinstalled it several times, recent versions

What's happening now is that I have the play button selected, and I have to sign in each time I start my Stream Deck.

It chooses to connect to Plex. I sign in with email, get to the sign-in window, and get the response: "We were unable to complete this request."

The first time I did this, it succeeded, and that was in the Stream Deck application itself. Now, having encountered this problem, I am getting a browser tab, not the Stream Deck window.

I enabled the diagnostics and hit test player/server

Meanwhile, PlexAmp itself runs fine.

Server is a homelab on my local network.

[FrankyDE]

I have also problems connecting. As it tells me that a device is alleready connected.
Oh and I installed the pulg-in today. 2026-08-19 😅

[FrankyDE]

I have also problems connecting. As it tells me that a device is alleready connected. Oh and I installed the pulg-in today. 2026-08-19 😅

✅ OK I got it working

Basically I did an "manual" setting as it was told in the installation instructions.
A few things that I did wrong:

• I looked at the token in the network settings, but looking at the Sourcecode did it.
  Just look for "X-Plex-Token" as described in the Manual #RTFM 😅
• Then the Client Name is your Nick at the PleskServer ....

So what I should have done was to read the manual ... #Sigh

Thanks, now I can enjoy the covers. 🙏🙏🙏

[DreadHeadHippy]

@Greenysmac Sorry I didn't see this earlier. Thanks for the detailed report, and sorry you’re running into this.

A quick note first: in recent versions, the Plex sign-in is expected to open in your system browser (not inside Stream Deck).
What is not expected is needing to sign in again every reboot.

To narrow this down, could you share the following?

1. Environment
2. OS + version
3. Stream Deck app version
4. Ampdeck+ plugin version
5. Repro details
6. Does sign-in succeed if you use a private/incognito window (or another browser) for the auth flow?
7. Are any adblock/privacy extensions active in the browser used for Plex sign-in?
8. After a successful sign-in, do both Test Player and Test Server pass?
9. After reboot, does it immediately show signed out, or only fail when pressing Play?
10. Diagnostics/logs
11. Enable plugin diagnostics/debug.
12. Capture logs for this exact sequence:
13. Click Sign in with Plex
14. Complete Plex authorization
15. Confirm setup succeeds
16. Restart Stream Deck app (or reboot)
17. Try Play again

Please include screenshots of:

• The setup status right after successful sign-in
• The status after restart when it asks to sign in again

Why I’m asking: this looks like either browser/Plex auth completion failure on that machine, or settings persistence not sticking after restart. These logs will let me pinpoint which path it is quickly.

[Greenysmac]

I'll try and answer as much of this as I can. The environment of my Plex server is in my house on Ubuntu inside of a Docker container. I'm using this on OS X 10 (that would be Tahoe 26.5.2). My stream deck version is 7.5.0 (that'd be 22885) and in fact I've just upgraded to 7.5.1, checking the version I'm using AmpdeckPlus 2.0.21.0 I don't know how I can sign in via a private incognito window unless you mean into Plex itself. I was able to sign in to Plex and get media to play on Chrome, Zen, and Firefox without any problems. There are no Adblock or privacy extensions active that are used for the Plex sign-in. I can't get it to sign in or test the player or server, despite giving the server information locally. This used to work. It stopped working a couple weeks ago. Even under Advanced Settings, from what little I can understand, I know: * what a Plex token is * what the client name is * what my URL from my player and my server is The Test Server button and the Plus Test Player button both say "Test Server" and "Please enter my server URL and token." I dig through the XML and get the token. I put the token in, and then I get "server connection failed. Failed to fetch." I've done multiple restarts of my computer, stream deck, and my Plex server. I'd give you the debug logging logs but I don't know where it is. I even removed the plugin, removed the residue from com.dreadheadhippy.ampdeckplus folder, reinstalled it… I'm open for ideas. Best, Jeff I. Green berg Linkedin ( https://linkedin.com/in/jeffgreenberg ) Reddit@ Greeny smac ( https://reddit.com/u/greenysmac ) (Time Zone: EST/EDT)

…

On Wed, Aug 19, 2026 at 3:09 PM, DreadHeadHippy < ***@***.*** > wrote: *DreadHeadHippy* left a comment (DreadHeadHippy/ AmpdeckPlus#22) ( #22 (comment) ) @ Greenysmac ( https://github.com/Greenysmac ) Sorry I didn't see this earlier. Thanks for the detailed report, and sorry you’re running into this. A quick note first: in recent versions, the Plex sign-in is expected to open in your system browser (not inside Stream Deck). What is not expected is needing to sign in again every reboot. To narrow this down, could you share the following? * Environment * OS + version * Stream Deck app version * Ampdeck+ plugin version * Repro details * Does sign-in succeed if you use a private/incognito window (or another browser) for the auth flow? * Are any adblock/privacy extensions active in the browser used for Plex sign-in? * After a successful sign-in, do both Test Player and Test Server pass? * After reboot, does it immediately show signed out, or only fail when pressing Play? * Diagnostics/logs * Enable plugin diagnostics/debug. * Capture logs for this exact sequence: * Click Sign in with Plex * Complete Plex authorization * Confirm setup succeeds * Restart Stream Deck app (or reboot) * Try Play again *Please include screenshots of:* * The setup status right after successful sign-in * The status after restart when it asks to sign in again Why I’m asking: this looks like either browser/Plex auth completion failure on that machine, or settings persistence not sticking after restart. These logs will let me pinpoint which path it is quickly. — Reply to this email directly, view it on GitHub ( #22?email_source=notifications&email_token=AHFJT7N7NJD3GNUDMPPUPH35KX3ODA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMZUGY3TSNRSGQ2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5346796244 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AHFJT7IIRZ6246VDPOJV4HD5KX3ODAVCNFSNUABGKJSXA33TNF2G64TZHMYTCNRQGYYTOOJRHA5US43TOVSTWNJQHE4TAOBXG42DLILWAI ). You are receiving this because you were mentioned. Message ID: <DreadHeadHippy/AmpdeckPlus/issues/22/5346796244 @ github. com>

[DreadHeadHippy]

On the same Mac running Stream Deck, can you open this URL in Chrome or another browser and see an XML response?

http://YOUR_PLEX_SERVER_IP:32400/identity

For example: http://192.168.1.100:32400/identity

[Greenysmac]

Yup <MediaContainer size =" 0 " apiVersion =" 1.2.2 " claimed =" 1 " machineIdentifier =" 08f2307d57d60764cc781065942e0e27f335dac1 " version =" 1.43.3.10896-cb3ebc72d " > </MediaContainer> Super visible. Best, Jeff I. Green berg Linkedin ( https://linkedin.com/in/jeffgreenberg ) Reddit@ Greeny smac ( https://reddit.com/u/greenysmac ) (Time Zone: EST/EDT)

…

On Fri, Aug 21, 2026 at 7:43 PM, DreadHeadHippy < ***@***.*** > wrote: *DreadHeadHippy* left a comment (DreadHeadHippy/ AmpdeckPlus#22) ( #22 (comment) ) On the same Mac running Stream Deck, can you open this URL in Chrome or another browser and see an XML response? http://YOUR_PLEX_SERVER_IP:32400/identity For example: http:/ / 192. 168. 1. 100:32400/ identity ( http://192.168.1.100:32400/identity ) — Reply to this email directly, view it on GitHub ( #22?email_source=notifications&email_token=AHFJT7OB3WQXG3EPBIGRDZ35LDNANA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMZXGY2TEMBRGAY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5376520101 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AHFJT7LWNNUZL2THB6F5CID5LDNANAVCNFSNUABGKJSXA33TNF2G64TZHMYTCNRQGYYTOOJRHA5US43TOVSTWNJQHE4TAOBXG42DLILWAI ). You are receiving this because you were mentioned. Message ID: <DreadHeadHippy/AmpdeckPlus/issues/22/5376520101 @ github. com>

[DreadHeadHippy]

Could you try signing in once more with a fresh session?

• Fully quit Stream Deck.
• Wait 10–15 minutes.
• Reopen Stream Deck, select one Ampdeck+ action, and click Sign in with Plex once.
• Complete the sign-in promptly in the browser tab that opens. Please do not refresh the tab or retry during that attempt.

If Plex still says “We were unable to complete this request,” please send a screenshot with the address bar visible and the URL with the value after code= redacted.

[DreadHeadHippy]

@Greenysmac Any updates? Has this issue corrected itself?

[DreadHeadHippy]

Closing this due to inactivity. If the issue persists or additional problems occur, please feel free to create a new issue. Thank you.