Emby Premiere Lifetime License Still Prompts for Upgrade

[plaidstallion 11]

I am trying to figure out an issue with my Emby Premiere pro key. I have had a lifetime license since Nov 2018 and never had any problems with it until recently but now with the key entered it is still prompting me to upgrade to premiere. I have tried removing the key and restarting the container and then reentering the key. It saves it and says it is valid but I still get prompted. Any help here?

[Luke 43549]

Hi, when and where exactly are you getting prompted ?

[ebr 17032]

Hi.  Please open the browser console while that circle is spinning.  What error is shown there?

Do you use a reverse-proxy?

[plaidstallion 11]

43 minutes ago, ebr said:

Hi.  Please open the browser console while that circle is spinning.  What error is shown there?

Do you use a reverse-proxy?

Thanks ebr and Luke, the reverse proxy question was the right lead. I got it sorted.

The cause was my Traefik security headers middleware. It was sending a Content-Security-Policy with no connect-src directive, so the browser fell back to default-src ‘self’ and refused to let the Emby web UI call mb3admin.com. In the browser dev tools (Network tab), the validateDevice and getStatus POSTs to mb3admin.com showed a status of CSP and never left the browser. That left the Premiere page spinning and showing the buy prompt even though the key was accepted. Accessing Emby by local IP worked fine because that path bypasses the proxy and its headers.

The fix was to give Emby its own headers middleware with connect-src added:

connect-src 'self' wss: https://mb3admin.com https://*.mb3admin.com https://*.emby.media;

Note for anyone else using Traefik: I had to swap the Emby router over to a chain containing the new middleware, not just append it after the default one, because the original CSP was still winning when both were applied.

After that the requests went through and the Premiere status showed correctly. If you see the same thing behind a reverse proxy, check the response headers for a Content-Security-Policy and look for CSP-blocked requests to mb3admin.com in the Network tab.

Thanks again for the pointer.