ThermodynamicEntropy

Thank you, I did check that earlier, but I now I realize my issue was trying to connect via VNC while the container was routed through Gluetun. I am able to connect normally while on a bridge network, but nothing (connection refused) when I run it through Gluetun. Would you have any insight on getting these working together? (Nicotine_ through Gluetun accessed on a VNC client)

Thank you, this has actually pushed me to Nicotine after some though on whether I really want my music collection to be automated. That being said, is there a way to connect to the tigerVNC server using my own VNCViewer client? I tried RealVNC, TightVNC and TigerVNC and they all say the connection is being actively refused by the computer.

Aloha, thank you for your response earlier, I started to look up that exact method and thats how I have it setup currently with SLSKD. I wanted to know if there's a way to get Nicotine+ to work with/produce a SLSKD apikey. I ended up going primarily to SLSKD so I can use it with soularr, but I prefer Nicotine+ in every way.

Greetings all. I'm trying to get Nicotine running through unraid's wieguard VPN using the "vpn tunneled access for docker". I am not able to get port forwarding working. I added the port I wanted to forward to the docker template as I am otherwise connected through the VPN just fine. I was misreading my error logs. I kept seeing " UPnP: Failed to forward external port 2234: No UPnP devices found" and assumed my port forwarding wasn't working, completely ignoring the UPnP issue like a dummy.

Aloha all, I'm hoping for some input that could help resolved my issue here I've been using this jacketvpn container for over a year now and now can't access the webgui. The logs show the server is up and there's no issue. Here's a quick list of the things I've tried/checked I can ping IPs and DNS entries from within the container Reboot the container didn't help Restarting the docker service did not help Rebooting the entire server did not help Installing a fresh jackettvpn with a new config directory did not help Changing the docker network from ipvlan to macvlan back to ipvlan did not help (I usually access my server through a wireguard vpn, so many efforts were focused on that I created a windows vm to see if I could connect to the docker within my home network, this did not work. I changed the docker tags to both dev and buster, but this did not help I've tried a few different PIA openvpn files, to no avail After everything so far, I'm inclined to believe there's something wrong with the docker itself and not my configuration, hence this post, to sanity check against anyone else using this docker and possibly get some help! I'm running Unraid 6.11.5. Logs below (The vpn is off for testing, but no webgui when its enabled:)

Confirming, this worked for me as well. Thanks @joelrfernandes!

Try these steps instead (this applies to JellyFin):

Hi all, I haven't touched this docker yet, but seeing the issues with permissions, I've got an arm-chair solution here. You can use something like inotify-command to watch output directory and run a chmod script every time theres a change. I'll try it out myself as well later. EDIT: It's the next day and I've done this now. It was pretty simple and seems to be working. Here's my script for inotify-command, just be sure to change the "WATCH_DIR:" to whatever the directory mapped in YOUR inotify-command container is (I believe it's dir1 by default). WATCH_DIR=/tubesync SETTLE_DURATION=5 MAX_WAIT_TIME=05:00 MIN_PERIOD=00:01 COMMAND="chmod 777 -R $WATCH_DIR" USER_ID=0 GROUP_ID=0 UMASK=0000 IGNORE_EVENTS_WHILE_COMMAND_IS_RUNNING=1 USE_POLLING=no DEBUG=0

Hi, Just tossing in my2¢. My ISP (verizon) recently blocked Nyaa for it's users. I can still grab stuff off of Nyaa myself, by I came here looking for something similar, to route jackett through PIA to avoid my isp messing about (I think this would probably clear up some other sites that I previously may have thought were 'dead').

Not quite, I meant nothing I was adding to mover file in /usr/local/sbin was being executed, but I now see that there's another mover file in usr/local/emhttp/plugins/ca.mover.tuning and my scripts ran when I added them there, I was a bit of an idiot and didn't look around enough. I didn't know about /usr being volatile, thank you for telling me, I'll add a line to my "go" file to over-write the mover on boot. EDIT: So I've been a bigger idiot than I originally anticipated, I've been adding things to /sbin this whole time, I accidentally copied the whole directory to root at some point today and have been in there this whole time.

Hi, I want to add my own script to run before and after mover runs (to pause some processes I know don't like mover), how would I go about doing this? I tried adding a command to run my script before the following line within /usr/local/sbin/mover. /usr/local/emhttp/plugins/ca.mover.tuning/mover.php $P_COMMAND $1 but this file doesn't appear to be called anymore.

I've added this to my own mover script, but a good feature for some would be to have certain docker containers shut down before mover runs and restarted after. For example, Radarr and Sonarr both like to get currupt databases if you run mover and they weren't set to use the cache drive as their appdata directory specifically. I don't have any appdata on my cache drive, as it's only used for speeding up my downloads and file transfers.

From what I can gather off of forum posts, a few people have been having issues with their rotating logs either filling up the docker.img. Also, good to see you're back in the community, I loved your work (I'm still using your Filebot plugin, I just had to swap out the .jar and .sh files with updated ones, this was also a shameless contrived reason to say hello).

Fixing a Malformed/Corrupted PLEX Database. Hi, all. I'm just here to update you on the "Starting Plex Media Server" issue. For me it was caused by a very malformed database file. I followed this guide which has worked perfectly. I've had a few more corruptions (brought about by failing hardware that I've replaced) but I've been able to bring my library back each time. I wrote this script to automate much of the process, and do some of the most basic backup management (creating backups if your database isn't corrupt/malformed and you agree to a prompt). PLEASE MAKE SURE YOUR TO SET THE TOP 2 VARIABLES! They're fairly self-explanatory, but here is what you set them to: appdata_directory > Your appdata directory plex_container_name > The name of your plex container (the defaults for those are "/mnt/user/appdata" and "plex" respectively) This script requires SQLite3 if you do not have it installed: 1. Go to Community Applications 2. Install the Dev Pack 3. Go to "Settings" in UNRAID 4. Open Dev Pack 5. Enable (install) SQLite3 6. Retry pmsDB.sh Also, please keep in mind that I wrote this script with this linuxserver.io image of plex in mind, it should(?) still work with other plex dockers if you edit the paths in the script, but I'm making no guarantees. Download Script: pmsDB.sh ***EDIT - 5/24/19*** I just updated the script to fix one of my checks (for sqlite3) and improved the error reporting (slightly).

48GB ECC DDR3