Premier Key Not Working

[JMGNYC 10]

I have had a permier key for years. I happened to go to the Emby dashboard today and my premier key was missing. I re-entered it but it doesn't seem to like it. It's there but still says it is missing or invalid.

 

I'm sure the key is correct. I even retrieved it just to double check using the Forgot Key button.

 

Plus Emby Theater won't start. It hangs on a black screen and I have to close it.

 

Any ideas what I can do to get this working?

[Happy2Play 9783]

You would need to post your logs. Possibly a connectivity issue with the validation server.

[JMGNYC 10]

EmbyLog.txt

 

Here's the log.

 

 

[Luke 42081]

Can you please provide the log from when you entered the key? thanks.

[JMGNYC 10]

I just re-entered the key, clicked save and here is the log.

 

Log.txt

 

 

[JMGNYC 10]

It just worked. I don't know what could have been wrong.

[Luke 42081]

Thanks for reporting back.

[JMGNYC 10]

So my key is back to not working again. This is the third time it has happened. Always fixes itself for no reason, no reboot or anything.

 

Is there a problem with my key? Could it be related to my server?

[ebr 16187]

So my key is back to not working again. This is the third time it has happened. Always fixes itself for no reason, no reboot or anything.

 

Is there a problem with my key? Could it be related to my server?

 

Without seeing a log and knowing exactly what "not working" means its hard to be sure but everything looks okay with your key on our end.

 

Can you describe exactly what the issue is?  Does the dashboard report you as not a supporter or is it just a particular app or feature that isn't recognizing it?

[JMGNYC 10]

Log.txt

 

The key is entered and has been. Going to the Dashboard I see a button in the upper right hand corner to "Support the Emby Team. Enjoy Bonus Features"

 

Going to the Emby Premier menu item I see "Emby Premiere key is missing or invalid." Even though it is entered, same as it has been for years.

 

Emby Theater does not work fully.

Edited December 13, 2016 by JMGNYC

[ebr 16187]

Can you please PM me the key you have in the dash?  Thanks.

[dlloyda 0]

I had this exact same issue starting around this exact same time frame.  it was working great since May and just stopped with same error.  I even accidentally purchased it again and entered the key again.  it worked for a day and stopped again.

[ebr 16187]

I had this exact same issue starting around this exact same time frame.  it was working great since May and just stopped with same error.  I even accidentally purchased it again and entered the key again.  it worked for a day and stopped again.

 

More than likely, something is blocking your server's access to our server.  Check your firewall setup and post a server log from when you save the key if you can't figure it out.

[dlloyda 0]

More than likely, something is blocking your server's access to our server.  Check your firewall setup and post a server log from when you save the key if you can't figure it out.

 

Ah ha!  Thanks for your response.  you are correct, I found it in my firewall URL filter.  The URL of mb3admin.com has been labeled globally by Palo Alto Networks (https://urlfiltering.paloaltonetworks.com/testasite/urlquery) as a Parked Domain.  and parked domains are on the block list for url recommendations.  their wording is, "parked —Domains registered by individuals, oftentimes later found to be used for credential phishing. These domains may be similar to legitimate domains, for example, pal0alto0netw0rks.com, with the intent of phishing for credentials or personal identify information. Or, they may be domains that an individual purchases rights to in hopes that it may be valuable someday, such as panw.net"

 

As soon as I opened it up in the url filter, that worked.  Thanks again.

[ebr 16187]

Thanks.  I have contacted them to have them remove us from that list.

[wae08 1]

if anyone currently deals with this i figured out setting the dns on your router (or if it was manually set on your pc) to 8.8.8.8 and 8.8.4.4 fixes this and then you can change it back to whatever you were using