app.emby.media - Not Secured

[blim5001 8]

RequireJS error: TypeError: newView is undefined. Failed modules: site.js:1:10796
Uncaught (in promise) TypeError: newView is undefined
    loadView https://app.emby.media/components/viewcontainer-lite.js?v=3.6.0.75:1
    loadView https://app.emby.media/bower_components/emby-webcomponents/viewmanager/viewmanager.js?v=3.6.0.75:1
    loadContent https://app.emby.media/bower_components/emby-webcomponents/router.js?v=3.6.0.75:1
    loadContentUrl https://app.emby.media/bower_components/emby-webcomponents/router.js?v=3.6.0.75:1
    execCb https://app.emby.media/bower_components/alameda/alameda.js:1
    defineModule https://app.emby.media/bower_components/alameda/alameda.js:1
    depFinished https://app.emby.media/bower_components/alameda/alameda.js:1
    waitForDep https://app.emby.media/bower_components/alameda/alameda.js:1
viewcontainer-lite.js:1:1116

Just tried Firefox and it just shows a black screen and the above in the console

[Luke 42078]

13 minutes ago, mike3821 said:

Please attach the complete contents of the browser debug console. Thanks.

[mike3821 67]

4 minutes ago, Luke said:

Please attach the complete contents of the browser debug console. Thanks.

Can somebody else grab this for Luke? I’m in the middle of driving.

[blim5001 8]

Forced a refresh in Firefox and it works now on Firefox, but still stuck on Chrome

Not sure if this is what you want, but this is from my console in chrome

serviceworker start
serviceworker-app.js:1 serviceworker cache opened
serviceworker-app.js:1 serviceworker cache read
serviceworker-app.js:1 appVersion: 4.6.4.53
serviceworker-app.js:1 Setting require baseUrl to https://app.emby.media
serviceworker-app.js:1 loadFirstLevelPolyfills
alameda.js:1 importScripts: https://app.emby.media/modules/babelhelpers.js
serviceworker-app.js:1 loadSecondLevelPolyfills
serviceworker-app.js:1 loadServiceLocator
serviceworker-app.js:1 loading appstorage
alameda.js:1 importScripts: https://app.emby.media/modules/emby-apiclient/appstorage-cache.js
alameda.js:1 importScripts: https://app.emby.media/modules/apphost.js
alameda.js:1 importScripts: https://app.emby.media/modules/browser.js
alameda.js:1 importScripts: https://app.emby.media/modules/common/appsettings.js
alameda.js:1 importScripts: https://app.emby.media/modules/emby-apiclient/events.js
alameda.js:1 importScripts: https://app.emby.media/modules/common/servicelocator.js
serviceworker-app.js:1 appstorage.init
serviceworker-app.js:1 appstorage.init complete
alameda.js:1 importScripts: https://app.emby.media/modules/emby-apiclient/connectionmanager.js
alameda.js:1 importScripts: https://app.emby.media/modules/emby-apiclient/credentials.js
alameda.js:1 importScripts: https://app.emby.media/modules/emby-apiclient/apiclient.js
alameda.js:1 importScripts: https://app.emby.media/modules/emby-apiclient/wakeonlan.js
connectionmanager.js:1 Begin ConnectionManager constructor
alameda.js:1 importScripts: https://app.emby.media/modules/common/globalize.js
alameda.js:1 importScripts: https://app.emby.media/modules/common/usersettings/usersettings.js
alameda.js:1 importScripts: https://app.emby.media/modules/common/usersettings/usersettingsbuilder.js
serviceworker.js:166 Uncaught (in promise) Error: Request for https://app.emby.media/index.html?_sw-precache=7c528127ef0b68cf319f50cace93d7fb returned a response with status 404
    at https://app.emby.media/serviceworker.js:166:25
    at async Promise.all (index 75)
(anonymous) @ serviceworker.js:166
/#!/home:1 The resource https://app.emby.media/modules/fonts/material-icons/LDItaoyNOAY6Uewc665JcIzCKsKc_M9flwmP_1.woff2 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
credentials.js:1 credentials initialized with: {}

 

[mike3821 67]

So my issue is fixed. Not the Chrome related issue but my server problems. After issuing a new certificate, Emby had the old one cached. I needed to delete that and restart Emby to pull the latest certificate in.

Now people that were complaining are able to get to the server. One of my fixes was turning on plain http traffic. However, the Apple client still wouldn’t work. 
 

Anyhow, the problem is fixed. But chrome still has issues accessing https://apps.Emby.media

 

 

[Luke 42078]

16 hours ago, mike3821 said:

But chrome still has issues accessing https://apps.Emby.media

 

 

I found the issue with that. Please give it another try. Thanks.

[mike3821 67]

Just now, Luke said:

I found the issue with that. Please give it another try. Thanks.

Worked right away.

Thanks for looking into this.

[Luke 42078]

Thanks for the feedback.

[blim5001 8]

The issues that were occurring seem to be fixed, thanks.

But I am not totally sure this is exactly what should happen...

it is a bit confusing as there 2 very similar urls apps.emby.media and app.emby.media

This is an example of what happens in an incognito window. So it should not see me as logged in

on this url 

https://apps.emby.media/

I see this:

as it loads the main emby webpage but it is using the cert for emby.tv, but the url ends in .media

So then clicking Sign in, I get sent to: the non https version of 

http://app.emby.media/#!/startup/welcome.html

which loads successfully and If I change the http to https then the page also loads successfully

[Luke 42078]

Apps.emby.media is not a url that we've ever used or advertised before.

[blim5001 8]

2 hours ago, Luke said:

But chrome still has issues accessing https://apps.Emby.media

ahh sorry,, that was the url that was posted here, hence my confusion.

[Luke 42078]

19 minutes ago, blim5001 said:

ahh sorry,, that was the url that was posted here, hence my confusion.

Not a problem.