VelcroBP

Can someone ELI5 an annoyance I have accessing my shares via SMB and File Explorer from a Win11 PC on my network? Basically, why does it sometimes access the "TOWER" right away, but other times I get "ACCESS DENIED"? I have an uNRaid user that matches my Windows user. In File Explorer on Windows, the shares show up in the navigation pane's "Network" group as "TOWERNAME". IF that's displayed, I can just double click and get right into the shares as expected. Sometimes, however, I have to expand the "Network" group. If that's the case and I try to click on "TOWERNAME", I get Access Denied. Also, the 2nd scenario seems to always be the case when accessing vie a "Browse..." menu for saving files. In either case, I am always able to access if I type the IP address into File Explorer's address bar regardless of how TOWERNAME displays in the navigation pane. I'm a networking idiot so I don't know if this is due to my bad configuration or just quirk in how windows does SMB?

I'm not finding any info in either documentation regarding an existing configuration option for permissions or how to add them to the template. I'm probably overlooking it.

Is there an environment variable available to set UMASK for the SLSKD container? Right now all files/folders are set as -rw-r--r--

I am using the default. Oddly enough, I upgraded unRaid last night from v6.11.5 to v6.12.4, and now it is working as expected. Loving the container!

I just installed SLSKD and it works great! However, if I launch the WebUI via unRaid, browser URL field is blank and nothing loads. However entering the IP:PORT in the browser works. I am routing the container through another for VPN. In the VPN container I have added both the HTTP & HTTPS ports indicated in the SLSKD template. I'm sure I'm overlooking something basic in my config.

I've been putting off upgrading but think I'd like to take the plunge so as to not fall any farther behind. I've been reading up on the history of the MACVLAN vs. IPVLAN issues and am hoping I won't have trouble. But I'd like to know if there are steps I can take to help make sure it will go as smoothly as possible. For instance: I've not used any manual/static IPs for my containers. Would it benefit me to switch them all/some over prior to the upgrade? Should I try switching to IPVLAN before the upgrade? Server mobo has 2 NICs + IPMI. I currently have the NICs as bond0 for redundancy, but only 1 is currently connected to the switch. I am using a custom Docker network for all of my containers (except iPerf3 as Host & Macinabox as Bridge). Will this help or hurt my chances for issues? I am using a domain with Cloudflare tunnel + NGINX reverse proxy. I only 1 router port forwarded to the server for PLEX. Will anything need adjusted on my router? Home network is simple: Modem > Router > Switch (unmanaged) > Clients (unRaid Server, PCs, VOIP, & AP [for phones, tablets, & TV]) The server is assigned a static IP in the router. I don't have any other Container-specific configurations, VLANS, or special firewall rules for unRaid What tests/diagnostics/errors should I look our for after the upgrade? Anything else I'm overlooking? Here is a link to my Network & Docker configs. Please let me know if any other settings or console outputs would be useful.

I followed THIS GUIDE for setup

I've used "GRANT ALL" & "SET OWNER" for the user on this database Sent from my Pixel 5 using Tapatalk

I've tried to follow the install instructions for Invidious but I am unable to access the WebUI. I am getting the following error in the logs (seems to repeat for all tables): Unhandled exception in spawn: permission denied for table users (PQ::PQError) from lib/pg/src/pq/connection.cr:202:22 in 'handle_error' from lib/pg/src/pq/connection.cr:220:65 in 'handle_async_frames' from lib/pg/src/pq/connection.cr:162:7 in 'read' from lib/pg/src/pq/connection.cr:414:31 in 'perform_query' from lib/db/src/db/statement.cr:80:7 in 'query:args' from lib/db/src/db/pool_statement.cr:29:30 in 'query:args' from lib/db/src/db/query_methods.cr:61:12 in 'begin' from src/invidious/jobs.cr:37:15 in '->' from /usr/share/crystal/src/fiber.cr:146:11 in 'run' from ??? Please let me know what info/files I can attach for more info.

Is this not possible? Should I just delete the VM and start over?

Every time I spin up the VM I get an error about memory module configuration. Here are screenshots of the error as well as the info from macOS.

Woke up to this error notification this morning. The system seems to be ok now so I'm not sure of the severity, other than this should never happen if everything is configured correctly, right? I set up a macOS VM yesterday using the Macinabox container. This is the first VM I've used (aside from quick testing way back when), so I'm guessing I might have configured that wrong somehow? can someone please take a peek at my diagnostics to see what the culprit is so I can read up on a solution? mootower-diagnostics-20230813-0739.zip

I used SpaceInvaderOne's tutorial and Macinabox to spin up a Big Sur VM. I want to shrink the vDisk but am not sure how. Right now the vDisk is designated 100GB and 29GB shows as allocated. I'm not familiar with macOS or how the Disk Utility manages the volumes, so I don't know what work needs done there before editing the VM image in unRaid.

Ok after backing up AppData and documenting all my current container and client settings I decided to try the :libtorrentv1 tag direct from v4.3.9. Now here's where I feel real dumb. I remembered that I was using a custom webUI and thought, "hey I bet that's not compatible or something". Sure enough, I revert to the default webUI, restart the container, then update it, and voila! Now it nuked my settings but they were easy enough to revert. It also nuked any empty categories, but I just recreated them with all their paths. Now I just hope it keeps running stable while I look for a new dark theme.

Bumping , please advise on upgrade path. i.e.: What versions between 4.3.9 and latest have major changes that need applied it configured before advancing versions. I want to get this container current before upgrading unRAID. Sent from my Pixel 5 using Tapatalk *Edited because I had the wrong version listed. I'm on 4.3.9 and looking for a safe upgrade path. I'm the meantime I'm reading up on qt6 and libtorrent 1.2 to see if either caused the issues I had trying to upgrade directly.

Is there a step-stone approach I need to take to safely upgrade to :latest from v3.3.9? What is the proper way to get current from this old release? I tried to go directly but it blew up my Category/Folder config. Sent from my Pixel 5 using Tapatalk

I'm bumping this looking for info on best practice upgrade path to :latest from v3.3.9

I'm still looking for info on this. Can a script maybe run on the SLSK download folder to change ownership of all subfolders & files at once?

I found this in the support thread and it fixed it for me.

Same here. I'm trying to isolate anything unique about Komga. I don't know when it started for me since I was away from home for 3.5 weeks and just tried Komga today.

Downloading Wireguard on router and unRAID container using other VPN causing issues? I set up Wireguard on my router to access my server while traveling and so far it is working as expected. however nothing seems to be downloading with qbt-VPN. the container is set up using AirVPN config. it is running and the AirVPN ip is showing with ifconfig. It has Internet access when testing with speedtest-cli. However all downloads added since I setup the Wireguard and left are immediately stalling with no connections. A test of the port forward on AirVPN shows "Connection Refused: 111". Is there something I'm missing that would prevent traffic to or from the container because of the router's Wireguard? Sent from my Pixel 5 using Tapatalk

I just installed a Slsk (Nicotine+) container from a Dockerhub pull. It's working great, but it's defaulting all newly created folders & files to 755 so I can't delete or move them when browsing the SMB from my Win11 PC. Can I force the container to apply 775 or 777 instead? Or will I have to manually CHGRP or CHMOD all downloads?

Ok my density continues. It was my Diagnostic-Utilities container hung up trying to "rebuild". I had set it to run through the Nicotine container for testing and forgot to update it when I shortened the container name. Derp.

As the titles says. This just started this afternoon after I installed a new container (Nicotine+), and configured it to route through a Binhex-qbt-VPN container. I did have to go through serval botched attempts because I was being dense and overlooking the VPN_INPUT_PORTS field so I couldn't get the new webUI up. No they seem to be running as expected but my Docker tab won't stop refreshing and is quite laggy. I've tried rebooting the server with no luck, as well as stopping those individual containers. Here is the issue docker tab.mp4

[SOLVED] I found the resolution in another thread pointing to the github instructions, question #24, instruction to add the webUI port to VPN container's VPN_INPUT_PORTS variable. I have another container (Nicotine+} routed through binhexQBT. The logs indicate it is successfully connecting to the web and logging in fine. However I'm unable to access the webui using SERVERIP:PORT. I have the port added to the BinhexVPN container and removed from the Nicotine template. Sent from my Pixel 5 using Tapatalk