starwak3

Thanks for your response. If that is the case, it does not make sense to me that other plugins that utilize yt-dl do not produce this error. Also, the error occurs on many other sites besides youtube, so I struggle to understand your response. Will you please clarify further?

I just uninstalled the deprecated plugin and copied the paths over to KluthR's plugin. I get the below message in red and it is not clear to me what I can do to configure the plugin any differently to resolve this. "Note: You should specify a backup share (and subfolders) dedicated to that particular backup. It is entirely possible for backups to erase any other files contained within the destinations." iss-diagnostics-20230421-1019.zip

Looking for some help with an error returning upon attempting to download videos in youtube-dl-material Here is the error text: Error while retrieving info on video with URL https://www.youtube.com/watch?v=E8RS6SZRk_4 with the following message: Error: Command failed with exit code 1: node_modules/youtube-dl/bin/youtube-dl -o video/%(title)s.mp4 --write-info-json --print-json -f bestvideo+bestaudio --merge-output-format mp4 --write-thumbnail --dump-json http://www.youtube.com/watch?v=E8RS6SZRk_4 ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type youtube-dl -U to update. Be sure to call youtube-dl with the --verbose flag and include its complete output. Error persists after the following troubleshooting: Restarted the docker Confirmed up to date (v4.3) Forced update used another ytdl docker (youtube-dl-server) and video downloads without error Removed and reinstalled from orphan image Removed with ophan and reinstalled anew iss-diagnostics-20230308-1423.zip

Odd how errors can creep up like this even when we don't change anything. Let's honor the fix suggested by the author's error. Give that password change a try. See if the log contents change and if the problem persists reply with the new log in a .txt file

Stats Plugin Not Showing The "Stats" plugin is listed as an included plugin on https://dev.deluge-torrent.org/wiki/Plugins however is not showing in 'Preferences > Plug-ins' as pictured in my screenshot. On that page, the plugin is listed as "no" under WebUI, however so is the Toggle plugin and that shows up. Troubleshooting so far: restarted container found a '.egg' in python 2.7 (this did show up in the list but understandably did not function) Any and all education/ideas in the pursuit of getting some tasty visualizations of data welcome. Thank you.

Got this error last week - the posted solution worked. Got this error this evening, the posted solution does not work now. Any ideas? Log for: mariadb [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] 40-initialise-db: executing... [cont-init.d] 40-initialise-db: exited 0. [cont-init.d] 90-custom-folders: executing... [cont-init.d] 90-custom-folders: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Warning: World-writable config file '/etc/my.cnf.d/custom.cnf' is ignored Warning: World-writable config file '/etc/my.cnf.d/custom.cnf' is ignored 210909 22:01:41 mysqld_safe Logging to '/config/databases/aae9e9e9ff69.err'. 210909 22:01:41 mysqld_safe Starting mariadbd daemon with databases from /config/databases Log for: nextcloud [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 40-config: executing... [cont-init.d] 40-config: exited 0. [cont-init.d] 50-install: executing... [cont-init.d] 50-install: exited 0. [cont-init.d] 60-memcache: executing... [cont-init.d] 60-memcache: exited 0. [cont-init.d] 70-aliases: executing... [cont-init.d] 70-aliases: exited 0. [cont-init.d] 90-custom-folders: executing... [cont-init.d] 90-custom-folders: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done.

Woah! I posted that quick as I was heading off to a huge plate of sushi - my bad. Regardless, I'm reassured that you checked in. Thank you. (weird bug huh?)

we meet again - here you go

now I understand what you were getting at. I thought you were asking it as a prep-question inferring that I missed a step. As of now, I have let the m.2 disk fully clear and removed it physically from the motherboard. Parity check / data-rebuild is underway. Once completed, my plan is to give it another go using the other m.2 slot. Hoping that, or just the chance of a second try will do the trick. I will also submit the bug report. Here goes nothin' - thank you both again!

I did not make a new config and rebuild parity without the new cache disk. I followed spaceinvaderone's tutorial and that wasn't mentioned. "New Config" is foreign to me - could you please elaborate? If by "rebuild parity" you mean performing a parity check then I understand that part. EDIT: I looked in Tools and of course New Config is there (duh - my bad). Do you suggest doing this and a parity check? whacky - alright then. I'll do that, unless you think that trurl's question opens up a different angle of attack here. Also, I'm curious if you have any comments regarding this part of my original post (quoted below). Thanks so much for your help, JorgeB

haha - I'm new to UNRAID but got the feeling this was actually a strange one. thanks for the quick reply. it did happen again. diags attached. iss-diagnostics-20210127-1213-BEFORE.zip iss-diagnostics-20210127-1222-AFTER(safe).zip

howdy - got a fun one! Issue: Upon restart, I noticed that a Clear operation had started automatically on my Cache disk which was also moved into my array in the last position (Disk 22). I reassigned the SSD to the Cache drive in "Pools" and formatted it as it was unmountable. The same thing happened again this morning upon boot. Weird things I noted that I'm not sure matter but may help ¯\_(ツ)_/¯: While initially setting up the cache drive, I noticed there was no "cache devices" section. I chose to click "Add Pool" and noticed that the default name was "cache," and took that as my cue. I was having difficulty with Macinabox (script confirming VM was ready but not appearing in VM menu). I initiated an install 3 times using Macinabox, then restarted. This issue first happened on the boot of this restart. Repeated this issue the morning after. I had only the plex docker installed and the server had been off overnight. The SSD is an m.2 in the motherboard slot that shares bandwidth with the 1st sata port (I *believe* this is the port that my parity drive is using) iss-diagnostics-20210127-0843.zip iss-diagnostics-reconfigured.zip

SWEET! that did the trick. initially got "Not Found" but it was clearly a response from the ip, not a timeout. added "/youtube-dl" and the webui loaded. why would changing the deluge lan_network variable from 192.168.1.0/24 to 192.168.0.0/24 make the difference? *edit: I see why now - just had to see it from this side of the learning journey - thank you again!*

I tried taking your suggestion changing deluge's LAN_NETWORK and using that address with the port added at the end to access webui. no luck. In spaceinvaderone's video, his local server IP and LAN_NETWORK within deluge differ similarly to the way that mine do. his server IP: 10.10.20.199 (mine: 192.168.0.22) deluge LAN_NETWORK: 10.10.20.0/24 (mine: 192.168.1.0/24) he enters 10.10.20.199:port and webui loads properly please let me know if I've missed something here. I'd love to be wrong

big thx for pointing me there - I'll take a look at FAQs more next time! youtube-dl-server run command: " root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='youtube-dl-server' -e TZ="America/Chicago" -e HOST_OS="Unraid" -v '/mnt/user/Duluth/':'/youtube-dl':'rw' --net=container:binhex-delugevpn 'kmb32123/youtube-dl-server' " binhex-delugevpn run command (vpn_user/vpn_pass and names_servers redacted): " root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-delugevpn' --net='bridge' --privileged=true -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='[...]' -e 'VPN_PASS'='[...]' -e 'VPN_PROV'='pia' -e 'VPN_CLIENT'='openvpn' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='192.168.1.0/24' -e 'NAME_SERVERS'='[...]' -e 'DELUGE_DAEMON_LOG_LEVEL'='info' -e 'DELUGE_WEB_LOG_LEVEL'='info' -e 'ADDITIONAL_PORTS'='' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -p '8118:8118/tcp' -p '8080:8080/tcp' -v '/mnt/user/downloads/':'/data':'rw' -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-delugevpn' "

that's correct. I posted a screenshot of the added port in deluge as well, but the post strangely only shows it if you open the 1st screenshot and navigate to the right ">" regardless I'll put it here as well

I have not resolved this yet, but I really appreciate you checking in. I triple-checked the settings and posted screenshots. After doing some research, I found that others were having this problem specifically when routing through deluge. Attempting to connect through "192.168.0.22:8080"

thanks for the reply, jonathanm. yes I did complete that mapping. I'm new, but still perplexed that this docker (and other yt downloaders) returns an error when running "curl ifconfig.io"

greetings I seem to have hit a snag that's not been posted. after entering "curl ifconfig.io" in the console of the docker I wish to route through the vpn it returns "sh: curl: not found" I tried forging forward with the rest of the docker settings to completion but the docker ends up inaccessible by IP. Any ideas on how to proceed are welcome!