be4con

No new supervisord.log file created unfortunately 😧 The last log file listed for the container within the unraid UI is 23 hours ago, is that any use, it's showing errors?

Yes, that's where I looked but I don't have that value - there is no DEBUG field. Sorry for being a pain on this...

Not sure how to complete this step: 3. Set the env var key "DEBUG" to a value of "true". Can you give me a pointer?

total 69252 drwxrwxrwx+ 1 nobody users 19 Jul 18 14:47 ./ drwxrwxrwx 1 nobody users 152 Jan 4 2018 ../ drwxrwxrwx 1 nobody users 54 Jul 15 14:35 archive/ -rw------- 1 nobody users 56 May 30 2017 auth -rw-rw-rw- 1 nobody users 7654644 Mar 17 09:45 blocklist.cache -rw-rw-rw- 1 nobody users 308 Mar 17 09:45 blocklist.conf -rw-rw-rw- 1 nobody users 308 Mar 13 09:45 blocklist.conf~ -rw-rw-rw- 1 nobody users 202981 Jul 19 10:13 deluge-web.log -rw-rw-rw- 1 nobody users 1355 Jul 19 09:42 deluged.log -rw-rw-rw- 1 nobody users 5635 Mar 19 20:53 dht.state -rw-rw-rw- 1 nobody users 115 Jun 1 2017 extractor.conf -rw-rw-rw- 1 nobody users 114 May 31 2017 extractor.conf~ -rw------- 1 nobody users 260 Jul 15 14:36 hostlist.conf -rw-rw-rw- 1 nobody users 168 May 30 2017 hostlist.conf.1.2.old -rw------- 1 nobody users 209 Jul 15 14:36 hostlist.conf.bak drwxrwxrwx 1 nobody users 299 Jan 12 2019 icons/ -rw-rw-rw- 1 nobody users 43206 Jan 16 2019 label.conf -rw-rw-rw- 1 nobody users 43148 Jan 16 2019 label.conf~ -rw-rw-rw- 1 nobody users 150 Apr 11 2018 ltconfig.conf -rw-rw-rw- 1 nobody users 79 Apr 11 2018 ltconfig.conf~ -rw-r--r-- 1 nobody users 162 May 30 2017 perms.txt drwxrwxrwx 1 nobody users 46 Apr 11 2018 plugins/ -rw-rw-rw- 1 nobody users 6115 Mar 19 20:53 session.state drwxrwxrwx 1 nobody users 56 May 30 2017 ssl/ drwxrwxrwx 1 nobody users 62 Jul 16 09:48 state/ -rw-r--r-- 1 nobody users 10353688 Jul 19 09:42 supervisord.log -rw-r--r-- 1 nobody users 10485974 Mar 19 2018 supervisord.log.1 -rw-r--r-- 1 nobody users 10485820 Mar 11 2018 supervisord.log.2 -rw-r--r-- 1 nobody users 10486229 Mar 4 2018 supervisord.log.3 -rw-r--r-- 1 nobody users 10485976 Feb 16 2018 supervisord.log.4 -rw-r--r-- 1 nobody users 10486150 Feb 9 2018 supervisord.log.5 -rw------- 1 nobody users 751 Jul 15 14:36 web.conf -rw-rw-rw- 1 nobody users 683 May 31 2017 web.conf.bak -rw-rw-rw- 1 nobody users 683 May 30 2017 web.conf~

I assume it's default - I don't think I changed anything. Currently set to 000

Thanks again. That certainly allowed me access, but unfortunately hasn't changed anything. I stopped the container, deleted the file and then restarted the container. It didn't regenerate the core.conf file though, so I no longer have one at all. I tried rebooting unraid, that didn't help and finally I removed and reinstalled the deluge container (but not the image), but again still no core.conf file. Am I going to have to delete everything and start again with a fresh deluge install? If so can I recover my torrent state - I assume that will be the state folder and the session.state file?

Sorry, thanks for your help with this but I'm going to need further direction. I have done that and I'm still unable to make any changes to, or delete, either the core.conf or the core.conf.bak files. I'm new to linux so this is all a bit bewildering to me. Have I got this right?

Ah OK, makes sense. I'm struggling to take ownership of the bak file to restore it. Any suggestions?

Suddenly I'm unable to connect to the deluge web UI on 192.168.11.208:8112 Everything was working fine yesterday morning, but today I get a 'This page cannot be displayed' error. I've tried rebooting Unraid and restarting the docker but to no avail. Launching the wb UI from within the docker fails too. I've tried changing the port, disabling my AV and firewall, and restarting my VPN just in case that was causing problems but nada. All other connectivity is fine, and I can access my shares without any issue. No settings have been changed on the docker. The only thing I can think may be related is that we had a power failure yesterday and my UPS also failed. After an unclean shutdown all my shares went missing until I rebooted Unraid. I don't recall for certain at what point after that deluge started playing up, but I'm pretty sure I accessed the web UI after the power failure issue. Not even sure where to start troubleshooting this so any advice would be gratefully received. EDIT: It looks like this is an issue with deluge 2.0. I tried rolling back to 1.3 and bingo, problem resolved. It looks like deluge must have updated yesterday at some point and that broke the web UI. EDIT2: Looks like I spoke too soon. The web UI is back now I've rolled back but I can't start the daemon - it just shows as offline in Connection Manager and doesn't respond when I click 'Start Daemon' So... any suggestions on what to try next? Thanks

I've not been able to resolve the issue I was having and the container stops spontaneously all the time. Is there anyone who can help me work through this to resolve it?

My unRaid is 6.3.5. I'll upgrade that as a start then! Once I've done that I'll give it another try and report back. Thanks EDIT: After the upgrade I have it installed and working now, thanks. However, it is constantly stopping and I keep having to restart the docker. Any suggestions?

I did install via your CA plugin Squid. But, unless I enable also search dockerHub in the CA settings, I don't find the mymediaalexa container: When I install it that way I don't see any relevant template to select and without selecting a specific template these are the only configurable options: I'm obviously missing a crucial step, but I have no idea what

Thanks. I didn't see that option when I installed so I started again and still can't see where I would make that change. There doesn't seem to be a relevant template, based on name, apart from the user defined template "my-mymediaforalexa" and if I choose that there are no fields for /datadir or /medialibrary for me to edit Any idea what I am doing wrong, or should I be choosing a different template?

Would anyone be so kind as to provide an idiot guide for how to get this up and running? I've installed the docker via Docker Hub, but I don't speak linux and the instructions on the mymediaalexia site are a little opaque. I've had my unraid server set up for a couple of years now (after following idiot guides elsewhere) without much (if any) tinkering and have l largelyforgotten even the basics of setup, so even simple instructions like "Create a directory for storing My Media for Alexa data files, eg ~/.MyMediaForAlexa" fill me with anxiety and confusion. So, as I understand it, I still need to set up that directory, somewhere other than where my music is stored. I also need to "note the remapped datadir and medialibrary paths" and ensure I have created those on my system first. What else do I need to do?? Anything you can help me with or point me in the right direction to sort will be seriously appreciated. Assume I can string a sentence together, but all other knowledge is variable.

Thanks, but that isn't what happened. Whilst I was waiting for a response I did work out that I could manually set each shares back to R/W so I shouldn't have panicked, but the plugin had left the both the comment and set all the shares to read only. That persisted regardless of what I did with the plugin. I resolved it by setting the shares manually back to R/W and deleting the comments. I then uninstalled the plugin. There is no question that, in this respect, it wasn't behaving as it should do on my server. I have also found that if you set the plugin to recreate bait files/shares on restart then that seems to trigger false +ves - it is the plugin deleting the previous shares that seems to trigger the alerts. Again, I doubt this is what is supposed to happen so it may just be me who is seeing this. If I change the option to use existing shares/files then those false +ves stop. in addition to this issue with persistent 'read only' status it is also not hiding the bait shares or bait files despite both being selected. That's not a biggie but it does make the network tree look a mess in Windows with all the bait shares showing. How do others deal with that? I really want to love this plugin, and I totally appreciate the effort that went into creating it. I have just reinstalled it so we will see if it behaves better on my server this time.

What is mover? I guess as I'm asking that question the answer is no I think the issue is to do with incomplete deletion of previous bait files, if that's possible. I originally had the plugin set to place bait files in all folders but found that was causing me issues. So I deleted previous bait files and then set to place in root only. It looks like the deletion of existing bait files didn't complete before a server reboot, and then it looks like it picked up again on restart and that triggered the attack warnings. Does that sound possible? After ensuring all files had finished deleting it seems the false positive stopped. I do have another problem though. Suddenly many of my files have changed permissions and I am being denied the access to delete or modify them. This seems to have happened since I installed the plugin. Any idea how I get my permissions back for 'nobody'? EDIT - it looks like this Ransomware plugin is misbehaving. After posting above, I ran fix permissions (docker safe) and still couldn't modify the files. So, I checked my shares (which I should have done previously I guess) and Unraid reports that all my shares are in read only mode due to the Ransomware plugin: However when I go to the plugin settings it reports that the SMB is not in read only mode. So I'm stuck with files in read only due to this plugin but can't correct that because the plugin claims they aren't. Help! If I uninstall the plugin will my files return to RW? Is there anything else I can do?

I installed this plugin a few days ago and I'm having tons of what appear to be false positives. I can't quite understand why and hope someone can help. Last night for example I had more than a dozen attacks with the following or similar log: Jan 1 03:18:09 Tower root: ransomware protection:Jan 1 03:18:09 Tower root: ransomware protection:Service pid Machine Connected at Encryption SigningJan 1 03:18:09 Tower root: ransomware protection:---------------------------------------------------------------------------------------------Jan 1 03:18:09 Tower root: ransomware protection:Jan 1 03:18:09 Tower root: ransomware protection:No locked filesJan 1 03:18:09 Tower root: ransomware protection:Jan 1 03:18:09 Tower root: ransomware protection:Gathering Inventory Of Old Bait FilesJan 1 03:18:09 Tower root: ransomware protection:Found 40 previous bait files.Jan 1 03:18:09 Tower root: ransomware protection:Starting Background Monitoring Of Bait FilesJan 1 03:18:49 Tower root: ransomware protection:Deleted 29 bait sharesJan 1 03:18:49 Tower root: ransomware protection:Creating Folder StructureJan 1 03:18:49 Tower root: ransomware protection:Double attack detected. Possible misconfigured settings allowing a share (downloads?) to be deleted locallyJan 1 03:18:49 Tower root: ransomware protection:..Jan 1 03:18:49 Tower root: ransomware protection:Possible Ransomware attack detected on file /mnt/user/suppose-Squidbait/.SquidBait-DO_NOT_DELETE.docxJan 1 03:18:49 Tower root: ransomware protection:SMB Status:Jan 1 03:18:49 Tower root: ransomware protection:Jan 1 03:18:49 Tower root: ransomware protection:Samba version 4.5.10Jan 1 03:18:49 Tower root: ransomware protection:PID Username Group Machine Protocol Version Encryption Signing I'm confident there is no malware on my machine, or network, so I'm not sure how to identify what is the trigger here or what settings to change to avoid these false positives. Can anyone help

OK thanks, I'm guessing I can just uninstall the docker and see if that cures the problem though?

Thanks, I tried a clean reboot of the unRAID box already and that didn't help. It's not transcoding the files, the WDTV Live just plays the files straight off normally - they are most mp4 and mkv. After I posted this yesterday I tried to play using Plex and I had the same problem that I'd previously had without - e.g. it just stopped after about 20 seconds and booted me back to the library. So I'm wondering if there could be any relation to the update to the Plex Docker after all. Is there any way to roll back a Docker update so I can test if that makes any difference?

This is probably not an unRAID problem, but I don't know enough to be sure, I'm hoping someone can tell me and I will know then where to look for help. I've been using a WDTV Live streaming box to access media from my unRAID NAS. Until around a week ago it was working fine, I was able to fully access all my files on my NAS as a network share and stream them without issue. Suddenly my WDTV Live will not readily access the NAS. When it finds it - which it does most of the time - access is sluggish and unresponsive with scrolling through folders taking an age and freezing on the menu, before suddenly catching up and jumping on through multiple folders. When I try and play files that a week ago played fine the start up is very slow and then after a very brief period - usually 10 seconds to a minute the files stops playing and I get booted back out to the library. This happens with every file. So a couple of things seem to have happened around the time this fault appeared and this is why I'm wondering if it might be an unRAID issue after all: [*]I had a power cut and the NAS (and all my electrical kit) had a sudden power down. Subsequent parity checks on the NAS found no fault. [*]I updated the Plex docker on my unRAID box - I use Plex for other streaming devices in the house, but not normally for the WDTV Live Through a process of elimination I have been able to identify that the WDTV Live hardware is not at fault - it will serve the same files just fine using Plex from the NAS and from local attached drives, it just won't serve them using SMB. I've also done a factory reset of the WDTV Live box so I'm pretty sure it's not a WDTV Live software issue. I can access the unRAID box from elsewhere on the network fine using SMB and Plex and all files play fine on other devices. I'm fairly sure this isn't an unRAID issue but just in case, can anyone offer any suggestions? Running unRAID 6.1.6, and only the Plex Docker updated to the latest version.