ak96ss 10 Posted February 28, 2022 Posted February 28, 2022 This morning I tried to open Emby as usual in Microsoft Edge by going to the local server address, port 8096. All I get is the Emby logo on the screen, it goes no further. I am able to open the Emby Theater app successfully; I can access it just fine in Firefox; and, in Edge, if I go to app.emby.media, it opens the way it should. I cleared my cookies, restarted Edge, restarted the Emby server service, restarted the server - but no luck. I've attached the console log - any thoughts? 192.168.1.120-1646060113152.log
Abobader 3470 Posted February 28, 2022 Posted February 28, 2022 Hello ak96ss, ** This is an auto reply ** Please wait for someone from staff support or our members to reply to you. It's recommended to provide more info, as it explain in this thread: Thank you. Emby Team
ak96ss 10 Posted February 28, 2022 Author Posted February 28, 2022 And now app.emby.media is not working in Edge... Still works fine in Firefox, and the Emby Theater app still works. app.emby.media-1646065121884.log
Luke 42085 Posted February 28, 2022 Posted February 28, 2022 HI, if you have any browser extensions, try removing them.
ak96ss 10 Posted February 28, 2022 Author Posted February 28, 2022 Removed them, restarted the browser, no luck. app.emby.media-1646065121884.log 192.168.1.120-1646060113152.log
Luke 42085 Posted February 28, 2022 Posted February 28, 2022 OK I'm afraid I don't know, sorry. Something in your browser configuration is interfering with our JavaScript, and you'll need to hunt down what that is. You can see it in the console log: content-scripts.js:1 INS: content-ads.js loaded: http://192.168.1.120:8096/web/index.html content-scripts.js:1 TSS: content-tss.js loaded: http://192.168.1.120:8096/web/index.html content-scripts.js:1 INS: content-blocked-items.js loaded: http://192.168.1.120:8096/web/index.html content-scripts.js:1 TSS: Excluding content tss (trigger: send-mesage) content-scripts.js:1 CONTENT_SHELL: Page allowed. Skipping shell injection blocks bower_components/ala…meda.js?v=4.6.7.0:1 Uncaught SyntaxError: Invalid or unexpected token app.js?v=4.6.7.0:1 Uncaught ReferenceError: define is not defined at startInfo (app.js?v=4.6.7.0:1:44970) at start (app.js?v=4.6.7.0:1:63684) at app.js?v=4.6.7.0:1:66486 at app.js?v=4.6.7.0:1:66494 index.html:1 Whatever content-tss.js is, or content-blocked-items.js, or content-ads.js...none of those are Emby javascript.
ak96ss 10 Posted March 1, 2022 Author Posted March 1, 2022 So I'm reasonably confident that the content-tss.js and such were related to the fact that I had the Malwarebytes extension enabled. It has been uninstalled, and that notice no longer appears in the console - but the Uncaught SyntaxError: Invalid or unexpected token app.js?v=4.6.7.0:1 is still there, and that is I think your code, since that v4.6.7.0 is the version of the Emby server I am running. And app.emby.media is now working in Edge, but I still get the errors when I try to go to the server URL:8096.
Luke 42085 Posted March 1, 2022 Posted March 1, 2022 Right I think the syntax error is a result of something interfering with or modifying the JavaScript. You could try clearing browsing data and seeing if that helps
ak96ss 10 Posted March 1, 2022 Author Posted March 1, 2022 Did that, deleted all Emby cookies, deleted all cookies, repaired Edge installation, no joy. It refused to open in Edge, but would open everywhere else. Then, on a whim, I changed the local http port, now it works. You've got me, I have no idea.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now