Jump to content

Emby Premiere key not recognised in v3.4.1.0


Recommended Posts

Posted

I just upgraded from v3.2.50.0 to v3.4.1.0. 

I have an Emby Premiere key stored in my server.

 

The new version does not display the little gold rosette and does display the banner saying "Support the Emby Team.  Enjoy Bonus Features".

 

The key is still visible in the Premiere settings page and re-saving the key does not fix the problem.

Guest plexman
Posted

Try this, it worked for me. Remove the key, save, restart the server and then insert the key again.

Posted

Interesting.  Would be curious to know what's changed to make this necessary.

Posted

Try this, it worked for me. Remove the key, save, restart the server and then insert the key again.

 

your solution doesn't work for me.  I even gave it an extra restart after setting the key again.

Posted

your solution doesn't work for me.  I even gave it an extra restart after setting the key again.

 

More than likely, the update caused your Firewall (or other security software) to automatically create a blocking rule.  Please check on that and let us know how it goes.

 

My Emby Key Says it is Invalid or Missing

Posted

More than likely, the update caused your Firewall (or other security software) to automatically create a blocking rule.  Please check on that and let us know how it goes.

 

My Emby Key Says it is Invalid or Missing

 

You've missed the point.  The key is accepted without issue.  The problem is simply that the dashboard still displays the prompt to get people to get Premiere.

Posted

If you are seeing that prompt, then something is not validating properly.

Posted

@@Banjo, are you referring to the front page of the emby server dashboard? If so, then can you please pull up your server dashboard in the browser, and then check the browser debug console and let us know if it showing any errors?

 

Thanks !

Posted

Yes @@Luke, I am talking about the dashboard.

 

I cleared the log and refreshed the page.  I have replaced my domain and username, but otherwise the log is unaltered:

app is hidden
apphost.js:1:4579
Begin ConnectionManager constructor
connectionmanager.js:1:14242
loading ApiClient singleton
site.js:1:8266
creating ApiClient singleton
site.js:1:8374
ApiClient serverAddress: https://media.mydomain.com
apiclient.js:1:2387
ApiClient appName: Emby Mobile
apiclient.js:1:2442
ApiClient appVersion: 3.4.1.0
apiclient.js:1:2485
ApiClient deviceName: Firefox
apiclient.js:1:2534
ApiClient deviceId: 8385350aaf5c0db28493a30f7c952f3b5255d8f5
apiclient.js:1:2583
credentials initialized with: {"Servers":[{"DateLastAccessed":1525938166000,"LastConnectionMode":2,"ManualAddress":"https://media.mydomain.com","Id":"c5919ae83fa1448192f308554daa6f5e","Name":"media.mydomain.com","LocalAddress":"http://172.18.0.6:8096","RemoteAddress":"https://media.mydomain.com:443","UserId":"8b2a7b120ad14865a5e429d33b5cd7fc","AccessToken":"0579fb6254c44533a421378f75a0049f","WakeOnLanInfos":[{"MacAddress":"02-42-AC-12-00-06"}]}]}
credentials.js:1:179
loaded ApiClient singleton
site.js:1:8708
initAfterDependencies promises resolved
site.js:1:16977
Using default fonts
site.js:1:18467
Loading installed plugins
site.js:1:29657
Loading plugin: bower_components/emby-webcomponents/playback/playbackvalidation
pluginmanager.js:1:571
Loading plugin: bower_components/emby-webcomponents/playback/playaccessvalidation
pluginmanager.js:1:571
Loading plugin: bower_components/emby-webcomponents/playback/experimentalwarnings
pluginmanager.js:1:571
Loading plugin: bower_components/emby-webcomponents/htmlaudioplayer/plugin
pluginmanager.js:1:571
Loading plugin: bower_components/emby-webcomponents/htmlvideoplayer/plugin
pluginmanager.js:1:571
Loading plugin: bower_components/emby-webcomponents/photoplayer/plugin
pluginmanager.js:1:571
Loading plugin: bower_components/emby-webcomponents/sessionplayer
pluginmanager.js:1:571
Loading plugin: bower_components/emby-webcomponents/youtubeplayer/plugin
pluginmanager.js:1:571
Setting page base to /web
router.js:1:13733
returning instance from getOrAddApiClient
connectionmanager.js:1:17159
Begin onAppReady
site.js:1:31533
onAppReady - loading dependencies
site.js:2:27
Loaded dependencies in onAppReady
site.js:2:122
Defining core routes
site.js:1:18946
Defining route: /addplugin.html
site.js:1:18780
Defining route: /appservices.html
site.js:1:18780
Defining route: /autoorganizelog.html
site.js:1:18780
Defining route: /channelsettings.html
site.js:1:18780
Defining route: /connectlogin.html
site.js:1:18780
Defining route: /dashboard.html
site.js:1:18780
Defining route: /dashboardgeneral.html
site.js:1:18780
Defining route: /dashboardhosting.html
site.js:1:18780
Defining route: /device.html
site.js:1:18780
Defining route: /devices.html
site.js:1:18780
Defining route: /devicesupload.html
site.js:1:18780
Defining route: /dlnaprofile.html
site.js:1:18780
Defining route: /dlnaprofiles.html
site.js:1:18780
Defining route: /dlnaserversettings.html
site.js:1:18780
Defining route: /dlnasettings.html
site.js:1:18780
Defining route: /edititemmetadata.html
site.js:1:18780
Defining route: /encodingsettings.html
site.js:1:18780
Defining route: /forgotpassword.html
site.js:1:18780
Defining route: /forgotpasswordpin.html
site.js:1:18780
Defining route: /home.html
site.js:1:18780
Defining route: /list.html
site.js:1:18780
Defining route: /index.html
site.js:1:18780
Defining route: /itemdetails.html
site.js:1:18780
Defining route: /library.html
site.js:1:18780
Defining route: /librarydisplay.html
site.js:1:18780
Defining route: /librarysettings.html
site.js:1:18780
Defining route: /livetv.html
site.js:1:18780
Defining route: /livetvguideprovider.html
site.js:1:18780
Defining route: /livetvseriestimer.html
site.js:1:18780
Defining route: /livetvsettings.html
site.js:1:18780
Defining route: /livetvstatus.html
site.js:1:18780
Defining route: /livetvtuner.html
site.js:1:18780
Defining route: /log.html
site.js:1:18780
Defining route: /login.html
site.js:1:18780
Defining route: /metadataadvanced.html
site.js:1:18780
Defining route: /metadataimages.html
site.js:1:18780
Defining route: /metadatanfo.html
site.js:1:18780
Defining route: /movies.html
site.js:1:18780
Defining route: /music.html
site.js:1:18780
Defining route: /mypreferencesdisplay.html
site.js:1:18780
Defining route: /mypreferenceshome.html
site.js:1:18780
Defining route: /mypreferencessubtitles.html
site.js:1:18780
Defining route: /mypreferenceslanguages.html
site.js:1:18780
Defining route: /mypreferencesmenu.html
site.js:1:18780
Defining route: /myprofile.html
site.js:1:18780
Defining route: /offline/offline.html
site.js:1:18780
Defining route: /managedownloads.html
site.js:1:18780
Defining route: /mysync.html
site.js:1:18780
Defining route: /camerauploadsettings.html
site.js:1:18780
Defining route: /mysyncjob.html
site.js:1:18780
Defining route: /mysyncsettings.html
site.js:1:18780
Defining route: /notifications.html
site.js:1:18780
Defining route: /notificationsetting.html
site.js:1:18780
Defining route: /notificationsettings.html
site.js:1:18780
Defining route: /nowplaying.html
site.js:1:18780
Defining route: /playbackconfiguration.html
site.js:1:18780
Defining route: /plugincatalog.html
site.js:1:18780
Defining route: /plugins.html
site.js:1:18780
Defining route: /scheduledtask.html
site.js:1:18780
Defining route: /scheduledtasks.html
site.js:1:18780
Defining route: /search.html
site.js:1:18780
Defining route: /selectserver.html
site.js:1:18780
Defining route: /serversecurity.html
site.js:1:18780
Defining route: /streamingsettings.html
site.js:1:18780
Defining route: /support.html
site.js:1:18780
Defining route: /supporterkey.html
site.js:1:18780
Defining route: /syncactivity.html
site.js:1:18780
Defining route: /syncsettings.html
site.js:1:18780
Defining route: /tv.html
site.js:1:18780
Defining route: /useredit.html
site.js:1:18780
Defining route: /userlibraryaccess.html
site.js:1:18780
Defining route: /usernew.html
site.js:1:18780
Defining route: /userparentalcontrol.html
site.js:1:18780
Defining route: /userpassword.html
site.js:1:18780
Defining route: /userprofiles.html
site.js:1:18780
Defining route: /wizardagreement.html
site.js:1:18780
Defining route: /wizardremoteaccess.html
site.js:1:18780
Defining route: /wizardcomponents.html
site.js:1:18780
Defining route: /wizardfinish.html
site.js:1:18780
Defining route: /wizardlibrary.html
site.js:1:18780
Defining route: /wizardsettings.html
site.js:1:18780
Defining route: /wizardstart.html
site.js:1:18780
Defining route: /wizarduser.html
site.js:1:18780
Defining route: /videoosd.html
site.js:1:18780
Defining route: /configurationpage
site.js:1:18780
Defining route: /
site.js:1:18780
returning instance from getOrAddApiClient
connectionmanager.js:1:17159
Begin connect
connectionmanager.js:1:28513
Begin getAvailableServers
connectionmanager.js:1:19368
Begin getConnectServers
connectionmanager.js:1:8167
Content Security Policy: The report URI (about:blank) should be an HTTP or HTTPS URI.
Content Security Policy: The page’s settings observed the loading of a resource at https://media.mydomain.com/web/serviceworker.js (“worker-src”). A CSP report is being sent.
Begin connectToServers, with 1 servers
connectionmanager.js:1:20022
begin connectToServer
connectionmanager.js:1:20571
beginning connection tests
connectionmanager.js:1:20933
testing connection mode 2 with server media.mydomain.com
connectionmanager.js:1:10665
tryConnect url: https://media.mydomain.com/emby/system/info/public
connectionmanager.js:1:3014
ConnectionManager requesting url: https://media.mydomain.com/emby/system/info/public
connectionmanager.js:1:2483
fetchWithTimeout: timeoutMs: 20000, url: https://media.mydomain.com/emby/system/info/public
connectionmanager.js:1:1893
fetchWithTimeout: succeeded connecting to url: https://media.mydomain.com/emby/system/info/public
connectionmanager.js:1:2159
ConnectionManager response status: 200, url: https://media.mydomain.com/emby/system/info/public
connectionmanager.js:1:2601
calling onSuccessfulConnection with connection mode 2 with server media.mydomain.com
connectionmanager.js:1:11149
ConnectionManager requesting url: https://media.mydomain.com/emby/System/Info
connectionmanager.js:1:2483
ConnectionManager response status: 200, url: https://media.mydomain.com/emby/System/Info
connectionmanager.js:1:2601
returning instance from getOrAddApiClient
connectionmanager.js:1:17159
Begin updateServerInfo. connectionMode: 2
apiclient.js:1:17807
Setting server address to https://media.mydomain.com
apiclient.js:1:18051
Requesting url without automatic networking: https://media.mydomain.com/emby/Sessions/Capabilities/Full
apiclient.js:1:12503
calling apiClient.ensureWebSocket
connectionmanager.js:1:5249
opening web socket with url: wss://media.mydomain.com/embywebsocket?api_key=0579fb6254c44533a421378f75a0049f&deviceId=8385350aaf5c0db28493a30f7c952f3b5255d8f5
apiclient.js:1:16223
Requesting url without automatic networking: https://media.mydomain.com/emby/Users/8b2a7b120ad14865a5e429d33b5cd7fc
apiclient.js:1:12503
returning instance from getOrAddApiClient
connectionmanager.js:1:17159
Requesting url without automatic networking: https://media.mydomain.com/emby/DisplayPreferences/usersettings?userId=8b2a7b120ad14865a5e429d33b5cd7fc&client=emby
apiclient.js:1:12503
Firefox can’t establish a connection to the server at wss://media.mydomain.com/embywebsocket?api_key=0579fb6254c44533a421378f75a0049f&deviceId=8385350aaf5c0db28493a30f7c952f3b5255d8f5.
apiclient.js:1:16285
web socket closed
apiclient.js:1:5376
nulling out web socket
apiclient.js:1:5441
Requesting url without automatic networking: https://media.mydomain.com/emby/Users/8b2a7b120ad14865a5e429d33b5cd7fc
apiclient.js:1:12503
resolving connectToServers with result.State: SignedIn
connectionmanager.js:1:20292
appRouter - processing path request /web/dashboard.html
router.js:1:6188
appRouter - user is authenticated
router.js:1:6709
Requesting url without automatic networking: https://media.mydomain.com/emby/Users/8b2a7b120ad14865a5e429d33b5cd7fc
apiclient.js:1:12503
Requesting url without automatic networking: https://media.mydomain.com/emby/Notifications/8b2a7b120ad14865a5e429d33b5cd7fc/Summary
apiclient.js:1:12503
Requesting url without automatic networking: https://media.mydomain.com/emby/Sessions
apiclient.js:1:12503
Requesting url without automatic networking: https://media.mydomain.com/emby/ScheduledTasks
apiclient.js:1:12503
Requesting url without automatic networking: https://media.mydomain.com/emby/System/Info
apiclient.js:1:12503
Requesting url without automatic networking: https://media.mydomain.com/emby/News/Product?StartIndex=0&Limit=4
apiclient.js:1:12503
Requesting url without automatic networking: https://media.mydomain.com/emby/System/ActivityLog/Entries?startIndex=0&limit=7&minDate=2018-05-09T07%3A43%3A18.400Z
apiclient.js:1:12503
Requesting url without automatic networking: https://media.mydomain.com/emby/LiveTv/Recordings?UserId=8b2a7b120ad14865a5e429d33b5cd7fc&IsInProgress=true&Fields=CanDelete%2CPrimaryImageAspectRatio&EnableTotalRecordCount=false&EnableImageTypes=Primary%2CThumb%2CBackdrop
apiclient.js:1:12503
Requesting url without automatic networking: https://media.mydomain.com/emby/web/configurationpages?pageType=PluginConfiguration&EnableInMainMenu=true
apiclient.js:1:12503
ConnectionManager requesting url: https://mb3admin.com/admin/service/registration/validateDevice?serverId=c5919ae83fa1448192f308554daa6f5e&deviceId=8385350aaf5c0db28493a30f7c952f3b5255d8f5&deviceName=Firefox&appName=Emby%20Mobile&appVersion=3.4.1.0&embyUserName=myuser&viewOnly=true
connectionmanager.js:1:2483
ConnectionManager request failed to url: https://mb3admin.com/admin/service/registration/validateDevice?serverId=c5919ae83fa1448192f308554daa6f5e&deviceId=8385350aaf5c0db28493a30f7c952f3b5255d8f5&deviceName=Firefox&appName=Emby%20Mobile&appVersion=3.4.1.0&embyUserName=myuser&viewOnly=true
connectionmanager.js:1:2852
getRegistrationInfo response: undefined
connectionmanager.js:1:27445
getRegistrationInfo failed: TypeError: NetworkError when attempting to fetch resource.
connectionmanager.js:1:26568
ConnectionManager request failed to url: https://mb3admin.com/admin/service/registration/validateDevice?serverId=c5919ae83fa1448192f308554daa6f5e&deviceId=8385350aaf5c0db28493a30f7c952f3b5255d8f5&deviceName=Firefox&appName=Emby%20Mobile&appVersion=3.4.1.0&embyUserName=myuser&viewOnly=true
connectionmanager.js:1:2852
getRegistrationInfo response: undefined
connectionmanager.js:1:27445
getRegistrationInfo failed: TypeError: NetworkError when attempting to fetch resource.
connectionmanager.js:1:26568
Requesting url without automatic networking: https://media.mydomain.com/emby/Packages/Updates?PackageType=UserInstalled
apiclient.js:1:12503
Requesting url without automatic networking: https://media.mydomain.com/emby/Packages/Updates?PackageType=System
apiclient.js:1:12503
Requesting url without automatic networking: https://media.mydomain.com/emby/System/Endpoint
apiclient.js:1:12503
Requesting url without automatic networking: https://media.mydomain.com/emby/Playback/BitrateTest?Size=500000
apiclient.js:1:12503
Requesting url without automatic networking: https://media.mydomain.com/emby/Playback/BitrateTest?Size=1000000
apiclient.js:1:12503
Requesting url without automatic networking: https://media.mydomain.com/emby/Playback/BitrateTest?Size=3000000
apiclient.js:1:12503
app is hidden
apphost.js:1:4579

Posted

Argh, the forum mangled my text formatting.  I had highlighted the error lines in red.

 

For reference, there's a pair of CSP errors around /web/serviceworker.js and a failure to connect to /embywebsocket.

Posted

Something is blocking validation:

getRegistrationInfo failed: TypeError: NetworkError when attempting to fetch resource.

You don't have Privacy Badger, right?

Posted

Yes, but that wasn't the problem.  uMatrix was blocking mb3admin.com.   I wasn't expecting the server to be calling out to anything for Premiere since I have a locally installed key. 

 

Is there any documentation on precisely what mb3admin.com is used for?

Posted

I wasn't expecting the server to be calling out to anything for Premiere since I have a locally installed key. 

 

Step 3 of the topic I pointed you to specifically states that we need to be able to access mb3admin.com for validation.

 

Step 4 says to check all security software as some will block it.

 

What would have made this more obvious so you could have solved it sooner?

Posted

Step 3 of the topic I pointed you to specifically states that we need to be able to access mb3admin.com for validation.

 

Step 4 says to check all security software as some will block it.

 

What would have made this more obvious so you could have solved it sooner?

 

Sure, but since your post did not appear to relate to my issue, I ignored the link.  The key was accepted on input (which is when I would expect any remote validation to be attempted).  I just thought you'd misunderstood the problem.

 

 

Interestingly, I re-blocked mb3admin.com and the problem did not recur.  I am beginning to wonder whether this is simply a caching issue.

Posted

There are different places that check individually and then cache individually, so you won't be able to just enter the key into your server and then block our domain.

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