Jump to content

Emby Premier Key will not register (Version 4.10.0.8 beta)


Go to solution Solved by Bobbybare,

Recommended Posts

Bobbybare
Posted

I could not get Emby Premier key to register on Version 4.10.0.4 beta, all I seem to get when I open the settings menu Emby Preier Tab is the blue rotating waiting circle.

It would allow me to click the save key and inform me that the key was updated, but the Buy Preier logo never disappeared and the feastures don't work (at least I can't download episodes or media to my mobile phone..

I updated to Version 4.10.0.8 beta and I still have the same problem!

How do I fix this please

Bob

hardware_detection-63910796657.txt embyserver (9).txt hardware_detection-63910802873 (1).txt hardware_detection-63910802873.txt embyserver-63910802805.txt hardware_detection-63910802228.txt embyserver-63910802214.txt

pwhodges
Posted

Do you have any firewall or similar software which might be blocking your access to mb3admin.com? That's required for Premiere to validate itself.

Paul

Bobbybare
Posted

Not as far as I know, this worked OK up until a couple of weeks ago? 

Bobbybare
Posted

I am running Emby server on a Terramater NAS, if that helps but access it through my Windows 11 PC

Posted
6 hours ago, Bobbybare said:

all I seem to get when I open the settings menu Emby Preier Tab is the blue rotating waiting circle.

This likely indicates a problem in the browser.  Your server is validating fine.  Look in the browser console for errors.

  • Solution
Bobbybare
Posted

Maybe I posted this problem in the wrong section of the Forum as Emby Server is running on a Terramaster NAS!!!

I found a solution to the problem.

For information:

My Nas has network connections one is 192.168.1.244 and the other is 192.168.1.245. When I updated Emby Server two weeks ago my PC connected on .245 instead of .244, So I fixed the ip addresses when I connect to the server with 192.168.1.245/8096 it works just fine and if I connect with 192.168.1.244/8181 it also works..

I had been trying to connect with 192.168.1.245/8181 the same port as the .244 connection so I guess that was the reason it failed..

Anyway all sorted now Thanks for the help..

Bob

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...