Just up dated to the latest beta 2021-10-08 on an Mac Mini 2018. The http://10.x.x.x:8089/admin/settings page does not load. All I see is a pair of circular spinning arrows.
Which browser?
Does the browser's javascript console show any error messages?
BackgroundUpdate: _reasonsToNotScheduleUpdates: Failed to check for Maintenance Service Registry Key: [Exception... "Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIUpdateProcessor.getServiceRegKeyExists]" nsresult: "0x80004001 (NS_ERROR_NOT_IMPLEMENTED)" location: "JS frame :: resource://gre/modules/BackgroundUpdate.jsm :: _reasonsToNotScheduleUpdates :: line 243" data: no] BackgroundUpdate.jsm:245
WebExtensions: reset-default-search: starting. api.js:183
WebExtensions: reset-default-search: has already ran once and saw panel, exit. api.js:210
[Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIContentSniffer.getMIMETypeFromContent]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: resource:///modules/FaviconLoader.jsm :: onStopRequest :: line 312" data: no] 2 FaviconLoader.jsm:312:24
AbortError: Actor 'Conduits' destroyed before query 'RuntimeMessage' was resolved ConduitsParent.jsm:312
[Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIContentSniffer.getMIMETypeFromContent]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: resource:///modules/FaviconLoader.jsm :: onStopRequest :: line 312" data: no] 2 FaviconLoader.jsm:312:24
WebExtensionPolicy.canAccessWindow: Argument 1 does not implement interface WindowProxy. Extension.jsm:2295
WebExtensionPolicy.canAccessWindow: Argument 1 does not implement interface WindowProxy. Extension.jsm:2295
WebExtensionPolicy.canAccessWindow: Argument 1 does not implement interface WindowProxy. Extension.jsm:2295
WebExtensionPolicy.canAccessWindow: Argument 1 does not implement interface WindowProxy. Extension.jsm:2295
WebExtensionPolicy.canAccessWindow: Argument 1 does not implement interface WindowProxy. Extension.jsm:2295
WebExtensionPolicy.canAccessWindow: Argument 1 does not implement interface WindowProxy. Extension.jsm:2295
WebExtensionPolicy.canAccessWindow: Argument 1 does not implement interface WindowProxy. Extension.jsm:2295
WebExtensionPolicy.canAccessWindow: Argument 1 does not implement interface WindowProxy. Extension.jsm:2295
WebExtensionPolicy.canAccessWindow: Argument 1 does not implement interface WindowProxy. Extension.jsm:2295
WebExtensionPolicy.canAccessWindow: Argument 1 does not implement interface WindowProxy. Extension.jsm:2295
Error: Can't find profile directory. 2 XULStore.jsm:66:15
WebExtensionPolicy.canAccessWindow: Argument 1 does not implement interface WindowProxy. Extension.jsm:2295
WebExtensionPolicy.canAccessWindow: Argument 1 does not implement interface WindowProxy. Extension.jsm:2295
Error: Can't find profile directory. 2 XULStore.jsm:66:15
The Web Console logging API (console.log, console.info, console.warn, console.error) has been disabled by a script on this page.
Running Big Sur and Firefox 93.0.
Tried: curl command to reload pre-release. Same spinning arrows.
Try again. this is the current Browser Console:
NotFoundError: No such JSWindowActor 'DevToolsFrame'
NotFoundError: No such JSWindowActor 'DevToolsWorker'
WebExtensionPolicy.canAccessWindow: Argument 1 does not implement interface WindowProxy. Extension.jsm:2295
WebExtensionPolicy.canAccessWindow: Argument 1 does not implement interface WindowProxy. Extension.jsm:2295
WebExtensionPolicy.canAccessWindow: Argument 1 does not implement interface WindowProxy. Extension.jsm:2295
WebExtensionPolicy.canAccessWindow: Argument 1 does not implement interface WindowProxy. Extension.jsm:2295
WebExtensionPolicy.canAccessWindow: Argument 1 does not implement interface WindowProxy. Extension.jsm:2295
WebExtensionPolicy.canAccessWindow: Argument 1 does not implement interface WindowProxy. Extension.jsm:2295
Error: Can't find profile directory. 2 XULStore.jsm:66:15
The Web Console logging API (console.log, console.info, console.warn, console.error) has been disabled by a script on this page.
Thanks, Blue
Downloaded the OSMac version of channels. When I tried to install, the software tells me Channels DVR is running.
Is it the same problem in Safari or Chrome?
Seems like you're running some plugin or extension that is interfering
Using Safari, same spinning arrows:
Console:
Service worker registration succeeded:
ServiceWorkerRegistration
active: ServiceWorker {scriptURL: "http://localhost:8089/service-worker.js", state: "activated", onstatechange: null, onerror: null, postMessage: function, …}
installing: null
onupdatefound: null
scope: "http://localhost:8089/"
updateViaCache: "imports"
waiting: null
ServiceWorkerRegistration Prototype
active
constructor: function()
installing
onupdatefound
scope
unregister()
update()
updateViaCache
waiting
Symbol(Symbol.toStringTag): "ServiceWorkerRegistration"
EventTarget Prototype
addEventListener(type, listener, [useCapture=false])
constructor: function()
dispatchEvent(event)
removeEventListener(type, listener, [useCapture=false])
Symbol(Symbol.toStringTag): "EventTarget"
Object Prototype
defineGetter(propertyName, getterFunction)
defineSetter(propertyName, setterFunction)
lookupGetter(propertyName)
lookupSetter(propertyName)
constructor: function()
hasOwnProperty(propertyName)
isPrototypeOf(property)
propertyIsEnumerable(propertyName)
toLocaleString()
toString()
valueOf()
From the Channels DVR installer program, I stopped the DVR and then restarted it. The WEB UI is back.
What version number is showing as running now? Is it still on prerelease?
Version: 2021.10.08.0020
Great. Not sure what happened but happy its working again.
I've had this a couple of times recently with the pre-releases. Is there a way to manually stop the DVR and restart it using some commands in Putty on the PR4100? I'm experiencing the same issue, but starting and stopping the App from the WD interface doesn't resolve the issue for me. The only thing that has resolved this in the past is a full reboot of the NAS, but I was curious if I could resolve it without a reboot.