Tweak3D

I've got 2 questions/issues. Firstly, While the UI is loading, it constantly prompts for credentials and complains about not being able to connect to rclone. I checked the UI log and its stating the following: 2022/09/27 09:02:58 INFO : Using --user admin --pass XXXX as authenticated user 2022/09/27 09:02:58 NOTICE: Serving remote control on http://0.0.0.0:5572/ 2022/09/27 09:02:58 NOTICE: Web GUI is not automatically opening browser. Navigate to http://admin:[email protected]:5572/?login_token=TOKENREMOVED to use. XXXX is not my password obviously, but my password is showing in the line below stating "Web GUI is not automatically opening browser." if I copy that URL it logs in and works just fine, but why is it not working directly from the Unraid UI? Secondly, I have a few shares with spaces in the name, for Example /mnt/user/appdata backup. But I am having issues getting the docker to see these as Media Shares. I've tried the following: /media/appdata backup /media/'appdata backup' '/media/'appdata backup'' '/media/appdata backup' /media/'appdata\ backup' /media/appdata\ backup All yield the same result, folder not found. How do I deal with handling a folder space in the path name for this docker? Thanks!

hmm, well that's somewhat unfortunate lol.

I've been seeing some similar but not identical issues on my box as well. Motherboard is an Asus z690-P D4. Errors are mostly: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20210730/dsfield-184) and there are tons of them. Additionally, I'm pretty sure unraid is trying to reboot, but it often stalls part way through leaving unraid inaccessible. When I turn on the monitor connected to unraid, all I see is a black screen. Performing a hard reboot is the only way to bring it back and then it reports all is good minus the errors mentioned above. Some research is showing this could be linux kernal/bios issue or an nviida driver issue. being that i'm on 12th gen intel and nvidia platform, both seem like they could be related in my situation

I've only ever seen it on forced shutdowns previously. My config is mostly unchanged for the last several revisions of unraid. I only stopped looking into it as others reported the same issue and most said it was likely a bug. I see now that it was also called out for those of us impacted that the logs were showing that the system wasn't waiting for the disks to shut down properly, and by toggling the field for disk timeout, this seemed to correct it (Post for reference: Parity check running when starting array every time - General Support - Unraid) and that seems to have corrected the issue for me as well. I changed the value to 100, saved, changed it back to 90 (what it was previously) and it looks like i'm good to go now. Hopefully this helps if others are having the same issue.

I've been having this issue since 6.9.1 where a reboot or a shutdown causes unraid to force a parity check when it comes back online. I saw that lots of others (but not everyone) were having this issue. Just reporting that this does not appear to be fixed in 6.9.2 :(. If there are any details I can provide to help get it fixed, i'd be more than happy to!

I got my instance up and running behind my proxy and it works great. Also confirming that by adding that variable to my template manually, it works perfectly! just be aware that the value of "false" is case sensitive, so keep it all lower case and name the variable with the name from the documentation and it works as expected.

I've been fighting the same issue for weeks, but didn't realize Chrome was to blame. Tried IE11 and sure enough works without issue. i can also connect via the mobile app without issue, so something is definitely up. also, interestingly enough, the Bitwarden addin for Chrome works fine, just not the web interface.

So just to follow up, Bitwarden is now loading and I can get to the login and create account screen, but hitting the submit button doesn't work when the form is filled out. I can cancel without issue and if I leave a required field blank it prompts me saying to fill in the corresponding empty fields. I've deleted and recreated the container, the docker image, and deleted my appdata/bitwarden directory. I don't see any errors in the docker container log at all anymore, but I don't know where else I can look for logging as I am unfamiliar with this docker. Any assistance would be much appreciated. Thanks!

ok, I deleted what I had, disabled direct i/o and it is installing now without issue, but now I cannot register an account, I get to the page, fill it out and click submit and nothing happens. Browser doesn't even indicate that anything is occuring. No errors or anything. So thats kinda odd. Any thoughts on that?

its ok, I apprecaite the help. I ended up copying the file db.sqllite3 from the bit warden directory on my UD to the appdata folder and overwrote what it had tried to made. I then remapped the docker to point back and my cache drives and now it works fine. I'll do some more testing, but super odd issue.

New directory on cache pool does not work. New directory on UD works fine as XFS and/or BRTFS I checked the perms on the Cache disk and that doesn't make a difference. I manually ran moved and moved off several hundred gigs of data to free up so blocks in a different part of the SSD, same issue. FS check in maintenance mode came up clean BTRFS scrube came up clean. both short and long SMART Tests passed without issue. No other errors in any other dockers, VMs, or unraid that I can see So it is something with my cache pool. but not exactly sure what. Any other suggestions I can try before I start updating firmware?

It could, but i'm not seeing any other issues with anything else. Nothing in the logs, smart tests, etc. I have dual Enterprise Intel p3600 1.6tb SSDs as my cache drive where this is running. I guess I can run a check on the FS on those 2 disks, but i'd think that an error of this nature would come up in various places and not with one very specific docker image. I'm fairly new to troubleshooting docker issues though, so it could very well be. I'll take a look.

I cannot get bitwarden to load at all. I've deleted and reinstalled multiple times and i'm only using default settings, so not sure what exactly is going on. Any assistance would be much apprecaited. The Docker never starts and this is all I see in the logs: First run: JWT keys don't exist, checking if OpenSSL is available...OpenSSL detected, creating keys...Keys created correctly.thread 'main' panicked at 'Can't run migrations: QueryError(DatabaseError(__Unknown, "disk I/O error"))', libcore/result.rs:945:5note: Run with `RUST_BACKTRACE=1` for a backtrace. Subsequent Runs: thread 'main' panicked at 'Failed to turn on WAL: DatabaseError(__Unknown, "disk I/O error")', libcore/result.rs:945:5note: Run with `RUST_BACKTRACE=1` for a backtrace.thread 'main' panicked at 'Failed to turn on WAL: DatabaseError(__Unknown, "disk I/O error")', libcore/result.rs:945:5note: Run with `RUST_BACKTRACE=1` for a backtrace.thread 'main' panicked at 'Failed to turn on WAL: DatabaseError(__Unknown, "disk I/O error")', libcore/result.rs:945:5note: Run with `RUST_BACKTRACE=1` for a backtrace.

gave this a try and got the same results. Just using PIA, so not sure why its not working here, seems to work fine on my desktop using their client: 2016-11-22 08:15:02,220 DEBG 'deluge-script' stderr output: [2016-11-22 08:15:02.220] Saved "/config/torrents/ubuntu-16.10-desktop-amd64.iso.0403fb4728bd788f.torrent" (variant.c:1266) [2016-11-22 08:15:02.220] ubuntu-16.10-desktop-amd64.iso Queued for verification (verify.c:269) [2016-11-22 08:15:02.220] ubuntu-16.10-desktop-amd64.iso Verifying torrent (verify.c:224) 2016-11-22 08:15:03,220 DEBG 'deluge-script' stderr output: [2016-11-22 08:15:03.220] ubuntu-16.10-desktop-amd64.iso Could not connect to tracker (announcer.c:996) [2016-11-22 08:15:03.220] ubuntu-16.10-desktop-amd64.iso Retrying announce in 20 seconds. (announcer.c:1005)

Having an issue and haven't see a solution. I added the docker, added my VPN info, all appears fine, but I constantly get warnings about "Cannot connect to tracker". Example below. Removed the name of the torrent and replaced with ****. [2016-11-21 12:33:01.295] **** Retrying announce in 1809 seconds. (announcer.c:1005) [2016-11-21 12:33:01.295] **** Connection failed (announcer.c:996) after several attempts, I then get this error: 2016-11-21 12:25:31,294 DEBG 'deluge-script' stderr output: [2016-11-21 12:25:31.294] **** Scrape error: Could not connect to tracker (announcer.c:1279) The log before it starts trying to download looks find to me, no warnings or errors, but I am horrible with routing, so perhaps something is off. usermod: no changes [info] Env var PUID defined as 99 [info] Env var PGID defined as 100 [info] Permissions already set for /config [info] Starting Supervisor... 2016-11-21 12:24:09,905 CRIT Set uid to user 0 2016-11-21 12:24:09,905 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing 2016-11-21 12:24:09,909 INFO supervisord started with pid 27 2016-11-21 12:24:10,912 INFO spawned: 'start-script' with pid 30 2016-11-21 12:24:10,913 INFO spawned: 'deluge-script' with pid 31 2016-11-21 12:24:10,915 INFO spawned: 'privoxy-script' with pid 32 2016-11-21 12:24:10,922 DEBG 'deluge-script' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2016-11-21 12:24:10,922 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2016-11-21 12:24:10,922 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2016-11-21 12:24:10,922 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2016-11-21 12:24:10,925 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2016-11-21 12:24:10,926 DEBG 'privoxy-script' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2016-11-21 12:24:10,935 DEBG 'start-script' stdout output: [info] VPN provider defined as pia [info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn 2016-11-21 12:24:10,937 DEBG 'start-script' stdout output: [info] Env vars defined via docker -e flags for remote host, port and protocol, writing values to ovpn file... 2016-11-21 12:24:10,954 DEBG 'start-script' stdout output: [info] VPN provider remote gateway defined as 104.200.154.4 [info] VPN provider remote port defined as 1198 [info] VPN provider remote protocol defined as udp 2016-11-21 12:24:10,961 DEBG 'start-script' stdout output: [info] VPN provider username defined as **** 2016-11-21 12:24:10,970 DEBG 'start-script' stdout output: [info] VPN provider password defined as **** 2016-11-21 12:24:10,987 DEBG 'start-script' stdout output: [info] Default route for container is 172.17.0.1 2016-11-21 12:24:10,996 DEBG 'start-script' stdout output: [info] Setting permissions recursively on /config/openvpn... 2016-11-21 12:24:10,998 DEBG 'start-script' stdout output: [info] Adding 192.168.1.0/24 as route via docker eth0 2016-11-21 12:24:10,999 DEBG 'start-script' stdout output: [info] ip route defined as follows... -------------------- 2016-11-21 12:24:11,000 DEBG 'start-script' stdout output: default via 172.17.0.1 dev eth0 2016-11-21 12:24:11,000 DEBG 'start-script' stdout output: 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2 192.168.1.0/24 via 172.17.0.1 dev eth0 2016-11-21 12:24:11,000 DEBG 'start-script' stdout output: -------------------- 2016-11-21 12:24:11,005 DEBG 'start-script' stdout output: [info] iptable_mangle support detected, adding fwmark for tables 2016-11-21 12:24:11,034 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2016-11-21 12:24:11,036 DEBG 'start-script' stdout output: -P INPUT DROP -P FORWARD ACCEPT -P OUTPUT DROP -A INPUT -i tun0 -j ACCEPT -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 9091 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 9091 -j ACCEPT -A INPUT -p udp -m udp --sport 53 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A OUTPUT -o tun0 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 9091 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 9091 -j ACCEPT -A OUTPUT -p udp -m udp --dport 53 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT 2016-11-21 12:24:11,036 DEBG 'start-script' stdout output: -------------------- [info] nameservers 2016-11-21 12:24:11,037 DEBG 'start-script' stdout output: nameserver 8.8.8.8 nameserver 8.8.4.4 2016-11-21 12:24:11,037 DEBG 'start-script' stdout output: -------------------- [info] Starting OpenVPN... 2016-11-21 12:24:11,044 DEBG 'start-script' stdout output: Mon Nov 21 12:24:11 2016 OpenVPN 2.3.9 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Dec 24 2015 Mon Nov 21 12:24:11 2016 library versions: OpenSSL 1.0.2f 28 Jan 2016, LZO 2.09 Mon Nov 21 12:24:11 2016 WARNING: file 'credentials.conf' is group or others accessible 2016-11-21 12:24:11,045 DEBG 'start-script' stdout output: Mon Nov 21 12:24:11 2016 UDPv4 link local: [undef] Mon Nov 21 12:24:11 2016 UDPv4 link remote: [AF_INET]104.200.154.4:1198 2016-11-21 12:24:11,058 DEBG 'start-script' stdout output: Mon Nov 21 12:24:11 2016 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this 2016-11-21 12:24:11,123 DEBG 'start-script' stdout output: Mon Nov 21 12:24:11 2016 [2136bcaeca1eddd771c929559cfff859] Peer Connection Initiated with [AF_INET]104.200.154.4:1198 2016-11-21 12:24:13,517 DEBG 'start-script' stdout output: Mon Nov 21 12:24:13 2016 TUN/TAP device tun0 opened Mon Nov 21 12:24:13 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0 Mon Nov 21 12:24:13 2016 /usr/bin/ip link set dev tun0 up mtu 1500 2016-11-21 12:24:13,518 DEBG 'start-script' stdout output: Mon Nov 21 12:24:13 2016 /usr/bin/ip addr add dev tun0 local 10.2.10.10 peer 10.2.10.9 2016-11-21 12:24:13,522 DEBG 'start-script' stdout output: Mon Nov 21 12:24:13 2016 Initialization Sequence Completed 2016-11-21 12:24:13,554 DEBG 'privoxy-script' stdout output: [info] Privoxy set to disabled 2016-11-21 12:24:13,554 DEBG fd 19 closed, stopped monitoring <POutputDispatcher at 47251779778752 for <Subprocess at 47251779714224 with name privoxy-script in state RUNNING> (stderr)> 2016-11-21 12:24:13,554 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 47251779711776 for <Subprocess at 47251779714224 with name privoxy-script in state RUNNING> (stdout)> 2016-11-21 12:24:13,554 INFO exited: privoxy-script (exit status 0; expected) 2016-11-21 12:24:13,554 DEBG received SIGCLD indicating a child quit 2016-11-21 12:24:13,558 DEBG 'deluge-script' stdout output: [info] First run detected, setting Transmission listening interface 10.2.10.10 2016-11-21 12:24:14,039 DEBG 'deluge-script' stdout output: [info] First run detected, setting transmission incoming port 2016-11-21 12:24:14,039 DEBG 'deluge-script' stdout output: [warn] PIA incoming port is not an integer, downloads will be slow, does PIA remote gateway supports port forwarding? [info] All checks complete, starting transmission... 2016-11-21 12:24:15,294 DEBG 'deluge-script' stderr output: [2016-11-21 12:24:15.293] Transmission 2.92 (14714) started (session.c:738) [2016-11-21 12:24:15.294] RPC Server Adding address to whitelist: 192.168.1.* (rpc-server.c:903) [2016-11-21 12:24:15.294] RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (rpc-server.c:1110) [2016-11-21 12:24:15.294] RPC Server Whitelist enabled (rpc-server.c:1114) [2016-11-21 12:24:15.294] Using settings from "/config" (daemon.c:528) [2016-11-21 12:24:15.294] Saved "/config/settings.json" (variant.c:1266) [2016-11-21 12:24:15.294] Loaded 4 torrents (session.c:2032) [2016-11-21 12:24:15.294] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:70) [2016-11-21 12:24:15.294] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:70) log.txt