squarepeg 6 Posted December 14, 2022 Posted December 14, 2022 Hi, I am having major problems with TOS5. If I have to shut Emby down for whatever reason, it won't start back up. I get an error somwhere in the 500s, I think it's 504 or something similar. I have to delete the 'Emby' shared folder from the NAS, Emby will then start but I have to set everything up from scratch - users, libraries, everything. Could you please have a look at what is causing this? I've gone back to Plex for the time being but I really much prefer Emby. Thanks p.s. It doesn't matter which Emby package I install, I've tried the stable one and loads of different betas all with the same result.
squarepeg 6 Posted December 15, 2022 Author Posted December 15, 2022 (edited) Hi guys I've got two problems with Emby at the moment; I keep getting 'get emby premiere' in the top-right even though I have already entered my key. I have tried removing the key, made sure that all firewall configs are correct and that I can reach the website (I can't remember the url now), restarting, adding again and restarting, uninstalling and doing a fresh install of Emby (including deleting the folders from the NAS) and have tried various versions - 4.7.10, 4.8.0.19 and 4.8.0.21. I also occasionally have a problem where Emby won't start up and I have to remove the shared folder that it creates on install/run. I have attached log files although I wasn't sure which logs to attach so I've added all of them This is really annoying and only seems to be since I 'upgraded', if you can call it that, to TOS 5. I did go back to Plex for a brief time but I much prefer Emby embyserver-63806716547.txt embyserver-63806716673.txt embyserver-63806719404.txt embyserver-63806722420.txt embyserver.txt hardware_detection-63806716486.txt hardware_detection-63806716617.txt hardware_detection-63806716894.txt hardware_detection-63806719586.txt hardware_detection-63806722490.txt Edited December 15, 2022 by squarepeg forgot to add something
trebordal 1 Posted December 15, 2022 Posted December 15, 2022 I have exactly the same problem with Emby (latest and beta versions) with TOS 5.0.176-00227.
Luke 39631 Posted December 15, 2022 Posted December 15, 2022 hi @squarepeg when this happens, can you please supply the contents of the browser debug console? Thanks !
trebordal 1 Posted December 16, 2022 Posted December 16, 2022 (edited) Hi @Luke Added the console log but I see there is not much in it. I added in the network trace info as well as well (no payload for the request, response as per @squarepegscreenshot above). One other observation, in the App Centre->Installed screenshot you will see that on power up that TOS has Emby marked as disabled. If you click that Enable button then there is a short pause followed by an "Operation failed" message being displayed (and the status remains as "Disabled" and there are no new entries in the Emby logs. Finally, when I SSH into the Terramaster NAS I dont see any Emby processes running which equates to Emby being marked as Disabled console-export-2022-12-16_8-27-19.txt Edited December 16, 2022 by trebordal Missed the SSH comment 1
squarepeg 6 Posted December 16, 2022 Author Posted December 16, 2022 @trebordal This is exactly the same behaviour as I am getting. Are you having the same issue with premiere too?
trebordal 1 Posted December 16, 2022 Posted December 16, 2022 >Are you having the same issue with premiere too? Yes, I did notice that and was on my list to look at. Unfortunately, I first needed to shutdown the NAS to add additional disks but when it powered up again Emby was dead. I have a couple of days of Emby configuration and library scans so I didn't want to lose that. ToS4 + Emby was rock solid so I am regretting the shift to ToS5.
squarepeg 6 Posted December 16, 2022 Author Posted December 16, 2022 22 minutes ago, trebordal said: I have a couple of days of Emby configuration and library scans so I didn't want to lose that. ToS4 + Emby was rock solid so I am regretting the shift to ToS5. That's exactly the same position as me - really regretting the 'upgrade' to TOS5.
squarepeg 6 Posted December 19, 2022 Author Posted December 19, 2022 I've just tried installing Emby again and tried to access via the Brave browser, worked fine but still can't validate Emby Premiere. I've pasted the contents of the console: app.js?v=4.8.0.21:1 Setting require baseUrl to http://192.168.1.68:8181/emby/web alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/browser.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: http://192.168.1.68:8181/emby/web/modules/babelhelpers.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/polyfills/crypto.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/emby-apiclient/appstorage-localstorage.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/apphost.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/shell.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/servicelocator.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/appsettings.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/emby-apiclient/events.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/fullscreen/fullscreenmanager.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/dom.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/textencoding.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/iap.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/layoutmanager.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/globalize.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/emby-apiclient/connectionmanager.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/usersettings/usersettings.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/usersettings/usersettingsbuilder.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/emby-apiclient/credentials.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/querystring/querystring.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/emby-apiclient/apiclient.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/emby-apiclient/wakeonlan.js?v=4.8.0.21 connectionmanager.js?v=4.8.0.21:1 Begin ConnectionManager constructor app.js?v=4.8.0.21:1 creating ApiClient singleton credentials.js?v=4.8.0.21:1 credentials initialized with: {"Servers":[{"ManualAddress":"http://192.168.1.68:8181/emby","ManualAddressOnly":true,"IsLocalServer":true,"AccessToken":"87a5cbc61ed94a12ade3d2843267ade6","UserId":"0f6b945f6b574319b835df2157c48ca4","DateLastAccessed":1671456750473,"LastConnectionMode":2,"Type":"Server","Name":"TNAS-5F92","Id":"8c48a807157448119b2fd12e39f15cd5","LocalAddress":"http://192.168.1.68:8096","RemoteAddress":"http://31.111.82.126:8096"}]} apiclient.js?v=4.8.0.21:1 ApiClient serverAddress: http://192.168.1.68:8181/emby apiclient.js?v=4.8.0.21:1 ApiClient appName: Emby Web apiclient.js?v=4.8.0.21:1 ApiClient appVersion: 4.8.0.21 apiclient.js?v=4.8.0.21:1 ApiClient deviceName: Chrome apiclient.js?v=4.8.0.21:1 ApiClient deviceId: 8bc0cca1-3fc3-4149-8757-d82ec21388c5 connectionmanager.js?v=4.8.0.21:1 returning instance from getOrAddApiClient app.js?v=4.8.0.21:1 loaded ApiClient singleton app.js?v=4.8.0.21:1 loadFirstLevelPresentationDependencies app.js?v=4.8.0.21:1 loadPlugins alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/approuter.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/itemhelper.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/pluginmanager.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/skinmanager.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/loading/loading.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/viewmanager/viewmanager.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/backdrop/backdrop.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/pagejs/page.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/focusmanager.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/playback/playbackmanager.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/methodtimer.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/playback/playqueuemanager.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/input/api.js?v=4.8.0.21 approuter.js?v=4.8.0.21:1 router href: http://192.168.1.68:8181/emby/web/index.html?#!/dashboard approuter.js?v=4.8.0.21:1 router self.location.pathname: /emby/web/index.html approuter.js?v=4.8.0.21:1 router getRequestFile() result: /index.html approuter.js?v=4.8.0.21:1 router baseUrl: http://192.168.1.68:8181/emby/web approuter.js?v=4.8.0.21:1 router self.location.pathname: /emby/web/index.html approuter.js?v=4.8.0.21:1 router getRequestFile() result: /index.html approuter.js?v=4.8.0.21:1 Setting page base to /emby/web app.js?v=4.8.0.21:1 Loading installed plugins app.js?v=4.8.0.21:1 Loading plugin module: ./modules/common/playback/playbackvalidation.js alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/playback/playbackvalidation.js?v=4.8.0.21 app.js?v=4.8.0.21:1 Loading plugin module: ./modules/common/playback/playaccessvalidation.js alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/playback/playaccessvalidation.js?v=4.8.0.21 app.js?v=4.8.0.21:1 Loading plugin module: ./modules/common/playback/experimentalwarnings.js alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/playback/experimentalwarnings.js?v=4.8.0.21 app.js?v=4.8.0.21:1 Loading plugin module: ./modules/logoscreensaver/plugin.js alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/logoscreensaver/plugin.js?v=4.8.0.21 app.js?v=4.8.0.21:1 Loading plugin module: ./modules/backdropscreensaver/plugin.js alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/backdropscreensaver/plugin.js?v=4.8.0.21 app.js?v=4.8.0.21:1 Loading plugin module: ./modules/photoscreensaver/plugin.js alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/photoscreensaver/plugin.js?v=4.8.0.21 app.js?v=4.8.0.21:1 Loading plugin module: ./modules/htmlaudioplayer/plugin.js alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/htmlaudioplayer/plugin.js?v=4.8.0.21 app.js?v=4.8.0.21:1 Loading plugin module: ./modules/htmlvideoplayer/plugin.js alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/htmlvideoplayer/plugin.js?v=4.8.0.21 app.js?v=4.8.0.21:1 Loading plugin module: ./modules/photoplayer/plugin.js alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/photoplayer/plugin.js?v=4.8.0.21 app.js?v=4.8.0.21:1 Loading plugin module: ./modules/sessionplayer.js alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/sessionplayer.js?v=4.8.0.21 app.js?v=4.8.0.21:1 Loading plugin module: ./modules/chromecast/chromecastplayer.js alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/chromecast/chromecastplayer.js?v=4.8.0.21 app.js?v=4.8.0.21:1 Loading plugin module: ./modules/youtubeplayer/plugin.js alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/youtubeplayer/plugin.js?v=4.8.0.21 app.js?v=4.8.0.21:1 Loading plugin module: ./modules/confirmstillplaying/plugin.js alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/confirmstillplaying/plugin.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/inputmanager.js?v=4.8.0.21 pluginmanager.js?v=4.8.0.21:1 creating plugin instance pluginmanager.js?v=4.8.0.21:1 loading plugin strings pluginmanager.js?v=4.8.0.21:1 creating plugin instance pluginmanager.js?v=4.8.0.21:1 loading plugin strings pluginmanager.js?v=4.8.0.21:1 creating plugin instance pluginmanager.js?v=4.8.0.21:1 loading plugin strings pluginmanager.js?v=4.8.0.21:1 creating plugin instance pluginmanager.js?v=4.8.0.21:1 loading plugin strings pluginmanager.js?v=4.8.0.21:1 creating plugin instance pluginmanager.js?v=4.8.0.21:1 loading plugin strings pluginmanager.js?v=4.8.0.21:1 creating plugin instance pluginmanager.js?v=4.8.0.21:1 loading plugin strings alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/htmlvideoplayer/htmlmediahelper.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/htmlvideoplayer/basehtmlplayer.js?v=4.8.0.21 pluginmanager.js?v=4.8.0.21:1 creating plugin instance pluginmanager.js?v=4.8.0.21:1 loading plugin strings pluginmanager.js?v=4.8.0.21:1 creating plugin instance chromecastplayer.js?v=4.8.0.21:1 Refused to load the script 'https://www.gstatic.com/cv/js/sender/v1/cast_sender.js' because it violates the following Content Security Policy directive: "default-src 'self' *.terra-master.com *.cloudfront.net *.baidu.com *.bdimg.com *.virtualearth.net *.ditu.live.com *.bing.com 'unsafe-inline' 'unsafe-eval' blob: data: ws: wss:". Note that 'script-src-elem' was not explicitly set, so 'default-src' is used as a fallback. (anonymous) @ chromecastplayer.js?v=4.8.0.21:1 pluginmanager.js?v=4.8.0.21:1 loading plugin strings pluginmanager.js?v=4.8.0.21:1 creating plugin instance pluginmanager.js?v=4.8.0.21:1 loading plugin strings connectionmanager.js?v=4.8.0.21:1 returning instance from getOrAddApiClient pluginmanager.js?v=4.8.0.21:1 creating plugin instance pluginmanager.js?v=4.8.0.21:1 loading plugin strings pluginmanager.js?v=4.8.0.21:1 creating plugin instance pluginmanager.js?v=4.8.0.21:1 loading plugin strings pluginmanager.js?v=4.8.0.21:1 creating plugin instance pluginmanager.js?v=4.8.0.21:1 loading plugin strings pluginmanager.js?v=4.8.0.21:1 creating plugin instance pluginmanager.js?v=4.8.0.21:1 loading plugin strings app.js?v=4.8.0.21:1 loadExternalScripts app.js?v=4.8.0.21:1 loadHeader alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/appheader/appheader.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/datetime.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/maintabsmanager.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/navdrawer/navdrawer.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/navdrawer/navdrawercontent.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/emby-elements/emby-button/paper-icon-button-light.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/emby-elements/emby-button/emby-button.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/emby-elements/emby-tabs/emby-tabs.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/emby-elements/emby-scroller/emby-scroller.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/shortcuts.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/listview/listview.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/cardbuilder/cardbuilder.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/emby-elements/emby-collapse/emby-collapse.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/emby-elements/emby-itemscontainer/emby-itemscontainer.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/scroller/smoothscroller.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/headroom/headroom.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/commandprocessor.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/mediainfo/mediainfo.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/indicators/indicators.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/itemcontextmenu.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/imageloader/imageloader.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/emby-elements/userdatabuttons/emby-ratingbutton.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/emby-elements/userdatabuttons/emby-playstatebutton.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/humanedate/humanedate.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/emby-elements/emby-checkbox/emby-checkbox.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/virtual-scroller/virtual-scroller.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/itemsrefresher.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/lazyloader/lazyloader-intersectionobserver.js?v=4.8.0.21 app.js?v=4.8.0.21:1 onAppReady app.js?v=4.8.0.21:1 Loaded dependencies in onAppReady app.js?v=4.8.0.21:1 Defining core routes approuter.js?v=4.8.0.21:1 Defining route: /startup/connectlogin.html approuter.js?v=4.8.0.21:1 Defining route: /startup/connectsignup.html approuter.js?v=4.8.0.21:1 Defining route: /startup/welcome.html approuter.js?v=4.8.0.21:1 Defining route: /startup/forgotpassword.html approuter.js?v=4.8.0.21:1 Defining route: /startup/forgotpasswordpin.html approuter.js?v=4.8.0.21:1 Defining route: /home approuter.js?v=4.8.0.21:1 Defining route: /home/home.html approuter.js?v=4.8.0.21:1 Defining route: /home.html approuter.js?v=4.8.0.21:1 Defining route: /home_horiz/home.html approuter.js?v=4.8.0.21:1 Defining route: /list/list.html approuter.js?v=4.8.0.21:1 Defining route: /item approuter.js?v=4.8.0.21:1 Defining route: /item/item.html approuter.js?v=4.8.0.21:1 Defining route: /livetv approuter.js?v=4.8.0.21:1 Defining route: /startup/login.html approuter.js?v=4.8.0.21:1 Defining route: /startup/manuallogin.html approuter.js?v=4.8.0.21:1 Defining route: /games approuter.js?v=4.8.0.21:1 Defining route: /videos approuter.js?v=4.8.0.21:1 Defining route: /music approuter.js?v=4.8.0.21:1 Defining route: /videoosd/videoosd.html approuter.js?v=4.8.0.21:1 Defining route: /settings approuter.js?v=4.8.0.21:1 Defining route: /settings/keyboard.html approuter.js?v=4.8.0.21:1 Defining route: /settings/notifications.html approuter.js?v=4.8.0.21:1 Defining route: /settings/playback.html approuter.js?v=4.8.0.21:1 Defining route: /settings/subtitles.html approuter.js?v=4.8.0.21:1 Defining route: /settings/display.html approuter.js?v=4.8.0.21:1 Defining route: /settings/homescreen.html approuter.js?v=4.8.0.21:1 Defining route: /settings/profile.html approuter.js?v=4.8.0.21:1 Defining route: /settings/password.html approuter.js?v=4.8.0.21:1 Defining route: /search approuter.js?v=4.8.0.21:1 Defining route: /startup/manualserver.html approuter.js?v=4.8.0.21:1 Defining route: /startup/selectserver.html approuter.js?v=4.8.0.21:1 Defining route: /tv approuter.js?v=4.8.0.21:1 Defining route: /plugins/install approuter.js?v=4.8.0.21:1 Defining route: /database approuter.js?v=4.8.0.21:1 Defining route: /dashboard approuter.js?v=4.8.0.21:1 Defining route: /dashboard.html approuter.js?v=4.8.0.21:1 Defining route: /dashboard/settings approuter.js?v=4.8.0.21:1 Defining route: /devices approuter.js?v=4.8.0.21:1 Defining route: /network approuter.js?v=4.8.0.21:1 Defining route: /devices/device.html approuter.js?v=4.8.0.21:1 Defining route: /devices/cameraupload.html approuter.js?v=4.8.0.21:1 Defining route: /metadatamanager approuter.js?v=4.8.0.21:1 Defining route: /transcoding approuter.js?v=4.8.0.21:1 Defining route: /librarysetup/libraries approuter.js?v=4.8.0.21:1 Defining route: /librarysetup/advanced approuter.js?v=4.8.0.21:1 Defining route: /livetvsetup/guideprovider.html approuter.js?v=4.8.0.21:1 Defining route: /livetvsetup/livetvsettings.html approuter.js?v=4.8.0.21:1 Defining route: /livetvsetup/livetvstatus.html approuter.js?v=4.8.0.21:1 Defining route: /livetvsetup/channels approuter.js?v=4.8.0.21:1 Defining route: /livetvsetup/livetvtuner.html approuter.js?v=4.8.0.21:1 Defining route: /logs approuter.js?v=4.8.0.21:1 Defining route: /log approuter.js?v=4.8.0.21:1 Defining route: /server/notifications/notificationsetting.html approuter.js?v=4.8.0.21:1 Defining route: /server/notifications/notificationsettings.html approuter.js?v=4.8.0.21:1 Defining route: /plugincatalog approuter.js?v=4.8.0.21:1 Defining route: /plugins approuter.js?v=4.8.0.21:1 Defining route: /scheduledtask approuter.js?v=4.8.0.21:1 Defining route: /dashboard/releasenotes.html approuter.js?v=4.8.0.21:1 Defining route: /scheduledtasks approuter.js?v=4.8.0.21:1 Defining route: /serveractivity approuter.js?v=4.8.0.21:1 Defining route: /apikeys approuter.js?v=4.8.0.21:1 Defining route: /embypremiere approuter.js?v=4.8.0.21:1 Defining route: /serverdownloads approuter.js?v=4.8.0.21:1 Defining route: /conversions approuter.js?v=4.8.0.21:1 Defining route: /serverdownloadsettings approuter.js?v=4.8.0.21:1 Defining route: /users/user approuter.js?v=4.8.0.21:1 Defining route: /users/new approuter.js?v=4.8.0.21:1 Defining route: /users approuter.js?v=4.8.0.21:1 Defining route: /wizard/wizardagreement.html approuter.js?v=4.8.0.21:1 Defining route: /wizard/wizardremoteaccess.html approuter.js?v=4.8.0.21:1 Defining route: /wizard/wizardfinish.html approuter.js?v=4.8.0.21:1 Defining route: /wizard/wizardlibrary.html approuter.js?v=4.8.0.21:1 Defining route: /wizard/wizardsettings.html approuter.js?v=4.8.0.21:1 Defining route: /wizard/wizardstart.html approuter.js?v=4.8.0.21:1 Defining route: /wizard/wizarduser.html approuter.js?v=4.8.0.21:1 Defining route: /configurationpage approuter.js?v=4.8.0.21:1 Defining route: /genericui approuter.js?v=4.8.0.21:1 Defining route: /index.html approuter.js?v=4.8.0.21:1 Defining route: / connectionmanager.js?v=4.8.0.21:1 Begin connect connectionmanager.js?v=4.8.0.21:1 Begin getAvailableServers connectionmanager.js?v=4.8.0.21:1 Begin getConnectServers alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/emby-apiclient/serverdiscovery.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/thememediaplayer.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/transparencymanagement.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/autobackdrops.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/notifications.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/dockedtabs/dockedtabs.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/nowplayingbar/nowplayingbar.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/playback/remotecontrolautoplay.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/input/keyboard.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/fullscreen/fullscreen-dc.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/input/gamepadtokey.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/playback/mediasession.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/input/mouse.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/screensavermanager.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/actionsheet/actionsheet.js?v=4.8.0.21 connectionmanager.js?v=4.8.0.21:1 Begin connectToServers, with 1 servers connectionmanager.js?v=4.8.0.21:1 begin connectToServer connectionmanager.js?v=4.8.0.21:1 tryReconnect: http://192.168.1.68:8181/emby connectionmanager.js?v=4.8.0.21:1 tryReconnectToUrl: http://192.168.1.68:8181/emby connectionmanager.js?v=4.8.0.21:1 ConnectionManager requesting url: http://192.168.1.68:8181/emby/emby/system/info/public alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/appfooter/appfooter.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/dialoghelper/dialoghelper.js?v=4.8.0.21 connectionmanager.js?v=4.8.0.21:1 ConnectionManager response status: 200, url: http://192.168.1.68:8181/emby/emby/system/info/public connectionmanager.js?v=4.8.0.21:1 connectionManager.resolveIfAvailable: http://192.168.1.68:8181/emby connectionmanager.js?v=4.8.0.21:1 connectionManager.onSuccessfulConnection: http://192.168.1.68:8181/emby connectionmanager.js?v=4.8.0.21:1 connectionManager.afterConnectValidated: http://192.168.1.68:8181/emby connectionmanager.js?v=4.8.0.21:1 connectionManager.validateAuthentication: http://192.168.1.68:8181/emby connectionmanager.js?v=4.8.0.21:1 ConnectionManager requesting url: http://192.168.1.68:8181/emby/emby/System/Info?api_key=87a5cbc61ed94a12ade3d2843267ade6 connectionmanager.js?v=4.8.0.21:1 ConnectionManager response status: 200, url: http://192.168.1.68:8181/emby/emby/System/Info?api_key=87a5cbc61ed94a12ade3d2843267ade6 connectionmanager.js?v=4.8.0.21:1 connectionManager.afterConnectValidated: http://192.168.1.68:8181/emby connectionmanager.js?v=4.8.0.21:1 returning instance from getOrAddApiClient apiclient.js?v=4.8.0.21:1 Setting server address to http://192.168.1.68:8181/emby connectionmanager.js?v=4.8.0.21:1 connectionManager.afterConnectValidated result.State: SignedIn connectionmanager.js?v=4.8.0.21:1 calling apiClient.ensureWebSocket apiclient.js?v=4.8.0.21:1 opening web socket with url: ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5 connectionmanager.js?v=4.8.0.21:1 returning instance from getOrAddApiClient alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/browserdeviceprofile.js?v=4.8.0.21 apiclient.js?v=4.8.0.21:1 WebSocket connection to 'ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5' failed: value @ apiclient.js?v=4.8.0.21:1 apiclient.js?v=4.8.0.21:1 web socket closed apiclient.js?v=4.8.0.21:1 nulling out web socket alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/registrationservices/registrationservices.js?v=4.8.0.21 connectionmanager.js?v=4.8.0.21:1 resolving connectToServers with result.State: SignedIn approuter.js?v=4.8.0.21:1 appRouter - processing path: /emby/web#!/dashboard, isBack: undefined approuter.js?v=4.8.0.21:1 appRouter - user is authenticated alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: http://192.168.1.68:8181/emby/web/dashboard/dashboard.js?v=4.8.0.21 registrationservices.js?v=4.8.0.21:1 validateFeature: themes connectionmanager.js?v=4.8.0.21:1 ConnectionManager requesting url: https://mb3admin.com/admin/service/registration/validateDevice?serverId=8c48a807157448119b2fd12e39f15cd5&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5&deviceName=Chrome&appName=Emby%20Web&appVersion=4.8.0.21&viewOnly=true Refused to connect to '<URL>' because it violates the following Content Security Policy directive: "default-src 'self' *.terra-master.com *.cloudfront.net *.baidu.com *.bdimg.com *.virtualearth.net *.ditu.live.com *.bing.com 'unsafe-inline' 'unsafe-eval' blob: data: ws: wss:". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback. Refused to connect to '<URL>' because it violates the following Content Security Policy directive: "default-src 'self' *.terra-master.com *.cloudfront.net *.baidu.com *.bdimg.com *.virtualearth.net *.ditu.live.com *.bing.com 'unsafe-inline' 'unsafe-eval' blob: data: ws: wss:". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback. Refused to connect to '<URL>' because it violates the following Content Security Policy directive: "default-src 'self' *.terra-master.com *.cloudfront.net *.baidu.com *.bdimg.com *.virtualearth.net *.ditu.live.com *.bing.com 'unsafe-inline' 'unsafe-eval' blob: data: ws: wss:". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback. Refused to connect to '<URL>' because it violates the following Content Security Policy directive: "default-src 'self' *.terra-master.com *.cloudfront.net *.baidu.com *.bdimg.com *.virtualearth.net *.ditu.live.com *.bing.com 'unsafe-inline' 'unsafe-eval' blob: data: ws: wss:". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback. Refused to connect to '<URL>' because it violates the following Content Security Policy directive: "default-src 'self' *.terra-master.com *.cloudfront.net *.baidu.com *.bdimg.com *.virtualearth.net *.ditu.live.com *.bing.com 'unsafe-inline' 'unsafe-eval' blob: data: ws: wss:". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback. connectionmanager.js?v=4.8.0.21:1 Refused to connect to 'https://mb3admin.com/admin/service/registration/validateDevice?serverId=8c48a807157448119b2fd12e39f15cd5&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5&deviceName=Chrome&appName=Emby%20Web&appVersion=4.8.0.21&viewOnly=true' because it violates the document's Content Security Policy. getFetchPromise @ connectionmanager.js?v=4.8.0.21:1 connectionmanager.js?v=4.8.0.21:1 getRegistrationInfo response: undefined connectionmanager.js?v=4.8.0.21:1 getRegistrationInfo failed: TypeError: Failed to fetch alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/viewmanager/baseview.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: http://192.168.1.68:8181/emby/web/components/activitylog.js?v=4.8.0.21 approuter.js?v=4.8.0.21:1 appRouter.sendRouteToViewManager - processing path: isBack: undefined alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/morphdom/morphdom.js?v=4.8.0.21 viewmanager.js?v=4.8.0.21:1 viewManager.onBeforeChange - processing path: isBack: undefined apiclient.js?v=4.8.0.21:1 apiclient starting message listener Sessions with options 0,1500,0,true,true apiclient.js?v=4.8.0.21:1 apiclient starting message listener ScheduledTasksInfo with options 0,1000 connectionmanager.js?v=4.8.0.21:1 ConnectionManager requesting url: https://mb3admin.com/admin/service/registration/validateDevice?serverId=8c48a807157448119b2fd12e39f15cd5&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5&deviceName=Chrome&appName=Emby%20Web&appVersion=4.8.0.21&viewOnly=true connectionmanager.js?v=4.8.0.21:1 Refused to connect to 'https://mb3admin.com/admin/service/registration/validateDevice?serverId=8c48a807157448119b2fd12e39f15cd5&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5&deviceName=Chrome&appName=Emby%20Web&appVersion=4.8.0.21&viewOnly=true' because it violates the document's Content Security Policy. getFetchPromise @ connectionmanager.js?v=4.8.0.21:1 apiclient.js?v=4.8.0.21:1 apiclient starting message listener ActivityLogEntry with options 0,1500 apiclient.js?v=4.8.0.21:1 apiclient starting message listener ActivityLogEntry with options 0,1500 connectionmanager.js?v=4.8.0.21:1 getRegistrationInfo response: undefined connectionmanager.js?v=4.8.0.21:1 getRegistrationInfo failed: TypeError: Failed to fetch cardbuilder.js?v=4.8.0.21:1 getImageWidth: card bannerCard bannerCard activeSession card-hoverable sideFooterCard focusable withsidefooter1920normal cardbuilder.js?v=4.8.0.21:1 width: 78 cardbuilder.js?v=4.8.0.21:1 getImageWidth: card backdropCard backdropCard card-hoverable focusable1920normal cardbuilder.js?v=4.8.0.21:1 width: 337 apiclient.js?v=4.8.0.21:1 opening web socket with url: ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5 apiclient.js?v=4.8.0.21:1 WebSocket connection to 'ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5' failed: value @ apiclient.js?v=4.8.0.21:1 apiclient.js?v=4.8.0.21:1 web socket closed apiclient.js?v=4.8.0.21:1 nulling out web socket apiclient.js?v=4.8.0.21:1 opening web socket with url: ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5 apiclient.js?v=4.8.0.21:1 WebSocket connection to 'ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5' failed: value @ apiclient.js?v=4.8.0.21:1 apiclient.js?v=4.8.0.21:1 web socket closed apiclient.js?v=4.8.0.21:1 nulling out web socket apiclient.js?v=4.8.0.21:1 opening web socket with url: ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5 apiclient.js?v=4.8.0.21:1 WebSocket connection to 'ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5' failed: value @ apiclient.js?v=4.8.0.21:1 apiclient.js?v=4.8.0.21:1 web socket closed apiclient.js?v=4.8.0.21:1 nulling out web socket apiclient.js?v=4.8.0.21:1 opening web socket with url: ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5 apiclient.js?v=4.8.0.21:1 WebSocket connection to 'ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5' failed: value @ apiclient.js?v=4.8.0.21:1 apiclient.js?v=4.8.0.21:1 web socket closed apiclient.js?v=4.8.0.21:1 nulling out web socket apiclient.js?v=4.8.0.21:1 opening web socket with url: ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5 apiclient.js?v=4.8.0.21:1 WebSocket connection to 'ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5' failed: value @ apiclient.js?v=4.8.0.21:1 apiclient.js?v=4.8.0.21:1 web socket closed apiclient.js?v=4.8.0.21:1 nulling out web socket apiclient.js?v=4.8.0.21:1 opening web socket with url: ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5 apiclient.js?v=4.8.0.21:1 WebSocket connection to 'ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5' failed: value @ apiclient.js?v=4.8.0.21:1 apiclient.js?v=4.8.0.21:1 web socket closed apiclient.js?v=4.8.0.21:1 nulling out web socket approuter.js?v=4.8.0.21:1 appRouter - processing path: /emby/web#!/embypremiere, isBack: undefined approuter.js?v=4.8.0.21:1 appRouter - user is authenticated alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: embypremiere/embypremiere.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/emby-elements/emby-input/emby-input.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/dialogs/confirm.js?v=4.8.0.21 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/dialog/dialog.js?v=4.8.0.21 approuter.js?v=4.8.0.21:1 appRouter.sendRouteToViewManager - processing path: isBack: undefined apiclient.js?v=4.8.0.21:1 apiclient stopping message listener Sessions apiclient.js?v=4.8.0.21:1 apiclient stopping message listener ScheduledTasksInfo viewmanager.js?v=4.8.0.21:1 viewManager.onBeforeChange - processing path: isBack: undefined embypremiere.js?v=4.8.0.21:1 Refused to connect to 'https://mb3admin.com/admin/service/registration/getStatus' because it violates the document's Content Security Policy. (anonymous) @ embypremiere.js?v=4.8.0.21:1 embypremiere.js?v=4.8.0.21:1 Uncaught (in promise) TypeError: Failed to fetch at embypremiere.js?v=4.8.0.21:1:1260 at embypremiere.js?v=4.8.0.21:1:1462 alameda.js?v=4.8.0.21:1 getJsUrlWithExtension: modules/common/dialogs/alert.js?v=4.8.0.21 registrationservices.js?v=4.8.0.21:1 validateFeature: themes connectionmanager.js?v=4.8.0.21:1 ConnectionManager requesting url: https://mb3admin.com/admin/service/registration/validateDevice?serverId=8c48a807157448119b2fd12e39f15cd5&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5&deviceName=Chrome&appName=Emby%20Web&appVersion=4.8.0.21&viewOnly=true connectionmanager.js?v=4.8.0.21:1 Refused to connect to 'https://mb3admin.com/admin/service/registration/validateDevice?serverId=8c48a807157448119b2fd12e39f15cd5&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5&deviceName=Chrome&appName=Emby%20Web&appVersion=4.8.0.21&viewOnly=true' because it violates the document's Content Security Policy. getFetchPromise @ connectionmanager.js?v=4.8.0.21:1 connectionmanager.js?v=4.8.0.21:1 getRegistrationInfo response: undefined connectionmanager.js?v=4.8.0.21:1 getRegistrationInfo failed: TypeError: Failed to fetch embypremiere.js?v=4.8.0.21:1 Refused to connect to 'https://mb3admin.com/admin/service/registration/getStatus' because it violates the document's Content Security Policy. (anonymous) @ embypremiere.js?v=4.8.0.21:1 embypremiere.js?v=4.8.0.21:1 Uncaught (in promise) TypeError: Failed to fetch at embypremiere.js?v=4.8.0.21:1:1260 at embypremiere.js?v=4.8.0.21:1:1462 apiclient.js?v=4.8.0.21:1 opening web socket with url: ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5 apiclient.js?v=4.8.0.21:1 WebSocket connection to 'ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5' failed: value @ apiclient.js?v=4.8.0.21:1 apiclient.js?v=4.8.0.21:1 web socket closed apiclient.js?v=4.8.0.21:1 nulling out web socket apiclient.js?v=4.8.0.21:1 opening web socket with url: ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5 apiclient.js?v=4.8.0.21:1 WebSocket connection to 'ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5' failed: value @ apiclient.js?v=4.8.0.21:1 value @ apiclient.js?v=4.8.0.21:1 value @ connectionmanager.js?v=4.8.0.21:1 onAppResume @ approuter.js?v=4.8.0.21:1 trigger @ events.js?v=4.8.0.21:1 onAppVisible @ apphost.js?v=4.8.0.21:1 apiclient.js?v=4.8.0.21:1 web socket closed apiclient.js?v=4.8.0.21:1 nulling out web socket apiclient.js?v=4.8.0.21:1 opening web socket with url: ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5 apiclient.js?v=4.8.0.21:1 WebSocket connection to 'ws://192.168.1.68:8181/embywebsocket?api_key=87a5cbc61ed94a12ade3d2843267ade6&deviceId=8bc0cca1-3fc3-4149-8757-d82ec21388c5' failed: value @ apiclient.js?v=4.8.0.21:1 value @ apiclient.js?v=4.8.0.21:1 value @ connectionmanager.js?v=4.8.0.21:1 onAppResume @ approuter.js?v=4.8.0.21:1 trigger @ events.js?v=4.8.0.21:1 onAppVisible @ apphost.js?v=4.8.0.21:1 apiclient.js?v=4.8.0.21:1 web socket closed apiclient.js?v=4.8.0.21:1 nulling out web socket
dljasani14 0 Posted January 3, 2023 Posted January 3, 2023 (edited) Found a temporary solution to the problem! Currently Emby on tos 5 having following errors! 1. Asking Emby premier key even though applying key in sever 2. getting 502- Bad gateway while opening emby ( this error starts all of a sudden and randomly ) 3. once 502-bad gateway error comes when i see under app center - installed app found Emby Server gets disable. if you try to enable it gives you operation fail I did not found any solution to error -1. If you ended up with error 2 and 3 mentioned above then do this. " Go to the user group in control panel and give the media group the permissions corresponding to the shared folder " If you have done this already before even though just go there and again save the configuration. Try enabling the emby server after. for me it worked. Not sure though how long the server will stay up!. but i guess if this work for you it will be temp fix. Edited January 3, 2023 by dljasani14
trebordal 1 Posted January 3, 2023 Posted January 3, 2023 Folks, I got bored with these continuing Terramaster Tos5 issues; the lack of reliable Emby being the most visible to the family but the reliability issues were also across other NAS apps as well even to disks dropping offline or a power cycle breaking the NAS configuration. So, I went down the path before Xmas of adding additional memory to my Terramaster and then replacing the TOS 5 operating system with the free open source TrueNAS Scale operating system. It meant I had to reformat all the disks to ZFS and restore their contents from USB backups but for me was well worth it as since then, Emby and all other NAS apps have had 100% uptime and all that unreliability and niggling issues, including the Emby Premier key issue, just vanished. Restarting Emby today for the latest Emby upgrade just worked (albeit with the 1 extra manual step to work around a minor known TrueNas shares issue). This migration away from TOS was an absolute pain to do but the NAS and Emby in particular is now fully available and Emby navigation is quite a bit faster and more fluid than with the native Terramaster ToS 4 and 5 so I am very happy. If anyone is interested in doing the same to get back to a reliable Emby just type "How To Install TrueNAS Scale On A Terramaster NAS" into your search engine of choice. Needs a hardware upgrade to add more memory and a bit of reading on how to configure but it was pretty easy in the end; just ensure that your Emby media backups are all up to date due to the need to reformat the disks and hence recopying all the films and shows back on to them again. One last point, the TrueNas file shares issue just means apps like Emby wont start if there are active shares so just disable them, restart Emby and reenable the shares and you're good to go.
gh0stwriter 3 Posted January 11, 2023 Posted January 11, 2023 (edited) The reason premiere doesn't work is becasue of the NGINX reverse proxy ( think this can work its just missconfigured) Since you can still connnect directly to emby you can just change the port in the URL and it will work as intended... since this is unlikely to get fixed on TOS, it would be nice if there was a redirection option in emby to correct the port if it is opened with the wrong port (probably a checkbox). Probably pretty simple to do with some JS in a global template (or however emby does this but globally). Edited January 11, 2023 by gh0stwriter
squarepeg 6 Posted January 11, 2023 Author Posted January 11, 2023 Plex had issues too. I even tried a full wipe, installing and configuring everything from scratch but ran into the same issues so I gave up and went back to TOS4 - works perfectly. TOS5 just isn't ready.
Luke 39631 Posted January 11, 2023 Posted January 11, 2023 Quote TOS5 just isn't ready. I agree (unfortunately). 1
gh0stwriter 3 Posted January 11, 2023 Posted January 11, 2023 49 minutes ago, Luke said: I agree (unfortunately). Probably going to rebuild the Teramaster I got for my parents on TrueNAS Core... same as my personal QNAP. At least then there is a high chance it stays secure for the year or two between updates it usually takes. (the NAS is 5000 miles away). 1
Bluntspoon2 0 Posted February 28 Posted February 28 On 1/2/2023 at 7:53 PM, dljasani14 said: Found a temporary solution to the problem! Currently Emby on tos 5 having following errors! 1. Asking Emby premier key even though applying key in sever 2. getting 502- Bad gateway while opening emby ( this error starts all of a sudden and randomly ) 3. once 502-bad gateway error comes when i see under app center - installed app found Emby Server gets disable. if you try to enable it gives you operation fail I did not found any solution to error -1. If you ended up with error 2 and 3 mentioned above then do this. " Go to the user group in control panel and give the media group the permissions corresponding to the shared folder " If you have done this already before even though just go there and again save the configuration. Try enabling the emby server after. for me it worked. Not sure though how long the server will stay up!. but i guess if this work for you it will be temp fix. After hours (and hours, and HOURS) of searching - "Go to the user group in control panel and give the media group the permissions corresponding to the shared folder " solved my problem of Emby Server not enabling. Holy moly Batman that was frustrating
Luke 39631 Posted February 28 Posted February 28 6 minutes ago, Bluntspoon2 said: After hours (and hours, and HOURS) of searching - "Go to the user group in control panel and give the media group the permissions corresponding to the shared folder " solved my problem of Emby Server not enabling. Holy moly Batman that was frustrating Hi, thanks for following up! What led you to that?
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