grover

Was there any update to this issue? I've been running Sonarr/Radarr etc for years with no issue. Recently update unraid to 6.12 (from 6.9 I think) and now no end of issues with corrupt dbs. Regretting the upgrade now.

My unifi video docker has just updated/downgraded and I'm back on 3.9.0 but now all my cameras are not connecting, unifi is reporting "Firmware Not Supported". All cams (G3-AF and G3 dome) are on 4.2.13 which is the latest available on the Unifi website. Any ideas? Would my cameras have auto updated their firmware, do I need to downgrade the cameras?

Cheers Squid. Docker run command below: [b]Command:[/b] root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="sabnzbd" --net="bridge" -e TZ="Europe/London" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -p 8080:8080/tcp -p 9090:9090/tcp -v "/mnt/user/Usenet/":"/downloads":rw -v "/mnt/user/Usenet/incomplete/":"/incomplete-downloads":rw -v "/mnt/user/appdata/sabnzbd":"/config":rw linuxserver/sabnzbd f2098efe1b32822c054bd315f9ea460454441ea5faf60e5bdad3c70199197513 The command finished successfully!

I've just installed this Docker, but all I get if I go to the WebUI is the spinning cog. config all totally standard. dirs as below: /incomplete-downloads <-> /mnt/user/Usenet/incomplete /config <-> /mnt/user/appdata/sabnzbd /downloads <-> /mnt/user/Usenet/complete Last few lines of the logs look like this: 2016-11-25 15:26:12,314::INFO::[sabnzbdplus:1347] SSL potentially supported protocols ['SSLv23', 'TLSv1', 'TLSv1_1', 'TLSv1_2'] 2016-11-25 15:26:12,315::INFO::[sabnzbdplus:1348] SSL actually supported protocols ['v23', 't12', 't11', 't1'] 2016-11-25 15:26:12,319::INFO::[sabnzbdplus:1495] Starting web-interface on 0.0.0.0:8080 2016-11-25 15:26:12,325::INFO::[_cplogging:217] [25/Nov/2016:15:26:12] ENGINE Bus STARTING 2016-11-25 15:26:12,330::INFO::[_cplogging:217] [25/Nov/2016:15:26:12] ENGINE Started monitor thread '_TimeoutMonitor'. 2016-11-25 15:26:12,533::INFO::[_cplogging:217] [25/Nov/2016:15:26:12] ENGINE Serving on http://0.0.0.0:8080 2016-11-25 15:26:12,535::INFO::[_cplogging:217] [25/Nov/2016:15:26:12] ENGINE Bus STARTED 2016-11-25 15:26:12,538::INFO::[panic:269] Launching browser with http://127.0.0.1:8080/sabnzbd 2016-11-25 15:26:12,539::INFO::[sabnzbdplus:1567] Starting sabnzbdplus-1.1.1 2016-11-25 15:26:12,545::INFO::[dirscanner:318] Dirscanner starting up 2016-11-25 15:26:12,547::INFO::[urlgrabber:71] URLGrabber starting up Any thoughts? I've tried removing and reinstalling a couple of time, no change.

I'm having a similar issue installing Community Applications: plugin: installing: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg plugin: downloading https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg plugin: downloading: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg ... done Warning: simplexml_load_file(): /tmp/plugins/community.applications.plg:116: parser error : Premature end of data in tag CHANGES line 15 in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): - Pop up free in appfe in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): /tmp/plugins/community.applications.plg:116: parser error : Premature end of data in tag PLUGIN line 13 in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): - Pop up free in appfe in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 plugin: xml parse error No VPN. I was using google DNS but that was causing a different problem (document is empty error as per previous posts), so I've reverted to default ISP DNS which seems to have made some progress. I've inspected community.applications.plg manually and the xml looks good to me.