Need some help with claiming a Plex server in Sparkbox Environment - New UGreen NAS 4800 Brand new drives and completely reformatted NAS is in separate VLAN - can access via WebUI or SSH without incident All other SB apps are working perfectly - have downloaded data from QB Error - "Not Authorized" First launch - entered Claim code, but Plex never returned that it accepted it Subsequent launches - get Not Authorized error What I have tried - Moving PC to same VLAN as Plex - No help When accessing Plex UI direct from browser (32400) - works, but option to claim sever is not available Attempted to add a Plex Claim variable to Docker...I think the SB Docker containers are not editable Hoping someone can help! Thanks
5 replies
Chris wrote:
Got it — this is an automatic acknowledgment from Chris, your AI support representative. Your post is in the support queue, and we’ll get to it as soon as we can. Legend members receive priority replies. If you’d like faster support while helping fund the project’s goals and continued development, consider becoming a Legend backer. <!-- chris-support-queue-ack:v1 --
Chris wrote:
The separate VLAN and moving the PC do not fix this particular first-claim path: SparkBox Plex is port-mapped, so Plex’s LAN auto-detection may not claim it. The supported no-SSH route is to open the Plex app from the SparkBox dashboard, choose the Claim your Plex server prompt, generate a fresh code at https://plex.tv/claim while signed in to the owning Plex account, paste it immediately, and let SparkBox restart Plex. The code expires after about four minutes. Please do not edit the container manually or post the code here. If that prompt is absent, reply with your SparkBox version and whether Plex is enabled in the dashboard; do not paste credentials or the claim code.
XF942 wrote:
Thanks. I had tried all of that as well and those stesp ultimately didn't fix it. What DID fix it was using a new Private Window for the browser. It was a "Plex cookie thing" that was causing the new un-claimed server to not show. It's all good now. Thanks!
Chris wrote:
Thanks for confirming. That points to stale browser session data rather than a VLAN problem or a bad Plex claim code. The server is working now, so no container or configuration change is needed.
Chris wrote:
Thanks for sharing what actually fixed it—I’m glad the server is showing correctly now. That points to stale browser session data in this case; I appreciate the correction.