Stubbs

For some reason I cannot access my NextCloud domain outside my home network, even though I followed the tutorial exactly. Everything is in order with the config files and port forwarding (click to expand the image): When I enter the domain on my home network, it appears fine with the correct https address. But if I try to do the same outside my local network, or when connected to a VPN, it times out. I ran the Let's Debug and got this: (the Let's Debug image is newer, hence the different IP from the DuckDNS part above) But as seen in the first image, I have port 80 forwarded properly. I can still access my Plex server from outside my local network. I used to be able to access NextCloud from other networks, but something appears to have gone wrong recently. None of the docker logs are showing any errors. [edit] NextCloud shows these errors: but I don't understand why X-Frame-Options is listed, because I am 100% sure I fixed that in the config. Log: _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [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] 50-config: executing... Variables set: PUID=99 PGID=100 TZ=Australia/Sydney URL=duckdns.org SUBDOMAINS=mydomain EXTRA_DOMAINS= ONLY_SUBDOMAINS=true DHLEVEL=2048 VALIDATION=http DNSPLUGIN= [email protected] STAGING= 2048 bit DH parameters present SUBDOMAINS entered, processing SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d mydomain.duckdns.org E-mail address entered: [email protected] http validation is selected Certificate exists; parameters unchanged; starting nginx [cont-init.d] 50-config: 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. nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html) Server ready

Oh right, thanks.

Can someone explain what is going on here? All my shares are set to high water, but since a few months ago, only disk 1 has been used. How do I make it so Unraid uses both disks?

I'm having a problem. I switched my ISP recently, which means different WAN IP, and for some reason, I can't connect to my NextCloud Server via reverse proxy. Everything looks to be in order, as it was before my ISP change: And the nginx log file doesn't show any errors: [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] 50-config: executing... Variables set: PUID=99 PGID=100 TZ=(my location) URL=duckdns.org SUBDOMAINS=my subdomain EXTRA_DOMAINS= ONLY_SUBDOMAINS=true DHLEVEL=2048 VALIDATION=http DNSPLUGIN= EMAIL=my email STAGING= 2048 bit DH parameters present SUBDOMAINS entered, processing SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d my subdomain E-mail address entered: my email http validation is selected Certificate exists; parameters unchanged; starting nginx [cont-init.d] 50-config: 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. nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html) Nor do any of the other containers.

Also this does not look right

This used to be working for me, but I recently had to wipe a cache drive, and now I can't set this up anymore, even though I followed the youtube tutorial exactly. For some reason, when I start it up, it loads up "Connection Manager" and has some 127.0.0.1 localhost thing there. In preferences, the download folder is set to something like "/usr/nobody/downloads" or just blank, even though it should say "data/downloads". If I try to change it to "data/Downloads", it doesn't work, torrents don't download, and the data wipes whenever I restart the docker container. Log: ErrorWarningSystemArrayLogin 2019-11-23 15:30:11,262 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2019-11-23 15:30:11,481 DEBG 'watchdog-script' stderr output: Unable to initialize gettext/locale! 'ngettext' Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/deluge/i18n/util.py", line 118, in setup_translation builtins.__dict__['_n'] = builtins.__dict__['ngettext'] KeyError: 'ngettext' 2019-11-23 15:30:12,271 DEBG 'watchdog-script' stdout output: [info] Privoxy process started [info] Waiting for Privoxy process to start listening on port 8118... 2019-11-23 15:30:12,274 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118 2019-11-23 15:31:02,331 WARN received SIGTERM indicating exit request 2019-11-23 15:31:02,331 DEBG killing watchdog-script (pid 162) with signal SIGTERM 2019-11-23 15:31:02,331 INFO waiting for start-script, watchdog-script to die 2019-11-23 15:31:03,333 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22522250854256 for <Subprocess at 22522250853584 with name watchdog-script in state STOPPING> (stdout)> 2019-11-23 15:31:03,333 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22522251007648 for <Subprocess at 22522250853584 with name watchdog-script in state STOPPING> (stderr)> 2019-11-23 15:31:03,333 INFO stopped: watchdog-script (terminated by SIGTERM) 2019-11-23 15:31:03,334 DEBG received SIGCHLD indicating a child quit 2019-11-23 15:31:03,334 DEBG killing start-script (pid 161) with signal SIGTERM 2019-11-23 15:31:04,336 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22522251236352 for <Subprocess at 22522251238992 with name start-script in state STOPPING> (stdout)> 2019-11-23 15:31:04,336 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22522250853488 for <Subprocess at 22522251238992 with name start-script in state STOPPING> (stderr)> 2019-11-23 15:31:04,336 INFO stopped: start-script (terminated by SIGTERM) 2019-11-23 15:31:04,336 DEBG received SIGCHLD indicating a child quit Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2019-11-23 15:31:18.484550 [info] System information Linux 45b7e6d0f1e9 4.19.56-Unraid #1 SMP Tue Jun 25 10:19:34 PDT 2019 x86_64 GNU/Linux 2019-11-23 15:31:18.519435 [info] PUID defined as '99' 2019-11-23 15:31:18.548815 [info] PGID defined as '100' 2019-11-23 15:31:18.788140 [info] UMASK defined as '000' 2019-11-23 15:31:18.813413 [info] Permissions already set for volume mappings 2019-11-23 15:31:18.842783 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info' 2019-11-23 15:31:18.867653 [info] DELUGE_WEB_LOG_LEVEL defined as 'info' 2019-11-23 15:31:18.894592 [info] VPN_ENABLED defined as 'yes' 2019-11-23 15:31:18.931016 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/my_expressvpn_australia_-_sydney_-_3_udp.ovpn 2019-11-23 15:31:18.988657 [info] VPN remote line defined as 'remote australia-sydney-3-ca-version-2.expressnetw.com 1195' 2019-11-23 15:31:19.017208 [info] VPN_REMOTE defined as 'australia-sydney-3-ca-version-2.expressnetw.com' 2019-11-23 15:31:19.043888 [info] VPN_PORT defined as '1195' 2019-11-23 15:31:19.079938 [warn] VPN_PROTOCOL not found in /config/openvpn/my_expressvpn_australia_-_sydney_-_3_udp.ovpn, assuming udp 2019-11-23 15:31:19.105762 [info] VPN_DEVICE_TYPE defined as 'tun0' 2019-11-23 15:31:19.132935 [info] VPN_PROV defined as 'custom' 2019-11-23 15:31:19.158887 [info] LAN_NETWORK defined as '192.168.1.0/24' 2019-11-23 15:31:19.182765 [info] NAME_SERVERS defined as '209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1' 2019-11-23 15:31:19.208818 [info] VPN_USER defined as '4r4v42acfgux7xb3mbq6tdku' 2019-11-23 15:31:19.235979 [info] VPN_PASS defined as '3hlfjpgbb6yb32uxhvc5pgpj' 2019-11-23 15:31:19.261872 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS) 2019-11-23 15:31:19.288964 [info] ENABLE_PRIVOXY defined as 'yes' 2019-11-23 15:31:19.314857 [info] Starting Supervisor... 2019-11-23 15:31:19,456 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing 2019-11-23 15:31:19,456 INFO Set uid to user 0 succeeded 2019-11-23 15:31:19,461 INFO supervisord started with pid 6 2019-11-23 15:31:20,463 INFO spawned: 'start-script' with pid 154 2019-11-23 15:31:20,465 INFO spawned: 'watchdog-script' with pid 155 2019-11-23 15:31:20,465 INFO reaped unknown pid 7 2019-11-23 15:31:20,471 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2019-11-23 15:31:20,471 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2019-11-23 15:31:20,471 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2019-11-23 15:31:20,532 DEBG 'start-script' stdout output: [info] Default route for container is 172.17.0.1 2019-11-23 15:31:20,535 DEBG 'start-script' stdout output: [info] Adding 209.222.18.222 to /etc/resolv.conf 2019-11-23 15:31:20,540 DEBG 'start-script' stdout output: [info] Adding 84.200.69.80 to /etc/resolv.conf 2019-11-23 15:31:20,543 DEBG 'start-script' stdout output: [info] Adding 37.235.1.174 to /etc/resolv.conf 2019-11-23 15:31:20,548 DEBG 'start-script' stdout output: [info] Adding 1.1.1.1 to /etc/resolv.conf 2019-11-23 15:31:20,552 DEBG 'start-script' stdout output: [info] Adding 209.222.18.218 to /etc/resolv.conf 2019-11-23 15:31:20,557 DEBG 'start-script' stdout output: [info] Adding 37.235.1.177 to /etc/resolv.conf 2019-11-23 15:31:20,562 DEBG 'start-script' stdout output: [info] Adding 84.200.70.40 to /etc/resolv.conf 2019-11-23 15:31:20,567 DEBG 'start-script' stdout output: [info] Adding 1.0.0.1 to /etc/resolv.conf 2019-11-23 15:31:20,867 DEBG 'start-script' stdout output: [info] Attempting to load iptable_mangle module... 2019-11-23 15:31:20,868 DEBG 'start-script' stderr output: modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.19.56-Unraid 2019-11-23 15:31:20,869 DEBG 'start-script' stdout output: [warn] Unable to load iptable_mangle module using modprobe, trying insmod... 2019-11-23 15:31:20,869 DEBG 'start-script' stderr output: insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory 2019-11-23 15:31:20,870 DEBG 'start-script' stdout output: [warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN [info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle' [info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko' 2019-11-23 15:31:20,885 DEBG 'start-script' stdout output: [info] Docker network defined as 172.17.0.0/16 2019-11-23 15:31:20,889 DEBG 'start-script' stdout output: [info] Adding 192.168.1.0/24 as route via docker eth0 2019-11-23 15:31:20,890 DEBG 'start-script' stdout output: [info] ip route defined as follows... 2019-11-23 15:31:20,891 DEBG 'start-script' stdout output: -------------------- 2019-11-23 15:31:20,892 DEBG 'start-script' stdout output: default via 172.17.0.1 dev eth0 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.3 192.168.1.0/24 via 172.17.0.1 dev eth0 2019-11-23 15:31:20,892 DEBG 'start-script' stdout output: -------------------- 2019-11-23 15:31:20,939 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2019-11-23 15:31:20,941 DEBG 'start-script' stdout output: -P INPUT DROP -P FORWARD DROP -P OUTPUT DROP -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 1195 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT -A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT -A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -i 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 1195 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT -A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT -A OUTPUT -o tun0 -j ACCEPT 2019-11-23 15:31:20,941 DEBG 'start-script' stdout output: -------------------- 2019-11-23 15:31:20,942 DEBG 'start-script' stdout output: [info] Starting OpenVPN... 2019-11-23 15:31:20,949 DEBG 'start-script' stdout output: Sat Nov 23 15:31:20 2019 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6 Sat Nov 23 15:31:20 2019 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6 Sat Nov 23 15:31:20 2019 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6 Sat Nov 23 15:31:20 2019 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6 2019-11-23 15:31:20,949 DEBG 'start-script' stdout output: Sat Nov 23 15:31:20 2019 WARNING: file 'credentials.conf' is group or others accessible Sat Nov 23 15:31:20 2019 OpenVPN 2.4.8 [git:makepkg/3976acda9bf10b5e+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Oct 30 2019 Sat Nov 23 15:31:20 2019 library versions: OpenSSL 1.1.1d 10 Sep 2019, LZO 2.10 2019-11-23 15:31:20,949 DEBG 'start-script' stdout output: [info] OpenVPN started Sat Nov 23 15:31:20 2019 WARNING: --ns-cert-type is DEPRECATED. Use --remote-cert-tls instead. 2019-11-23 15:31:20,949 DEBG 'start-script' stdout output: Sat Nov 23 15:31:20 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2019-11-23 15:31:20,951 DEBG 'start-script' stdout output: Sat Nov 23 15:31:20 2019 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Sat Nov 23 15:31:20 2019 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication 2019-11-23 15:31:20,951 DEBG 'start-script' stdout output: Sat Nov 23 15:31:20 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]185.198.242.96:1195 Sat Nov 23 15:31:20 2019 Socket Buffers: R=[212992->1048576] S=[212992->1048576] Sat Nov 23 15:31:20 2019 UDP link local: (not bound) Sat Nov 23 15:31:20 2019 UDP link remote: [AF_INET]185.198.242.96:1195 2019-11-23 15:31:20,972 DEBG 'start-script' stdout output: Sat Nov 23 15:31:20 2019 TLS: Initial packet from [AF_INET]185.198.242.96:1195, sid=54643ec7 4b2ceca4 2019-11-23 15:31:20,994 DEBG 'start-script' stdout output: Sat Nov 23 15:31:20 2019 VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, [email protected] 2019-11-23 15:31:20,995 DEBG 'start-script' stdout output: Sat Nov 23 15:31:20 2019 VERIFY OK: nsCertType=SERVER Sat Nov 23 15:31:20 2019 VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-4105-2a, [email protected] Sat Nov 23 15:31:20 2019 VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-4105-2a, [email protected] 2019-11-23 15:31:21,020 DEBG 'start-script' stdout output: Sat Nov 23 15:31:21 2019 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 2048 bit RSA Sat Nov 23 15:31:21 2019 [Server-4105-2a] Peer Connection Initiated with [AF_INET]185.198.242.96:1195 2019-11-23 15:31:22,085 DEBG 'start-script' stdout output: Sat Nov 23 15:31:22 2019 SENT CONTROL [Server-4105-2a]: 'PUSH_REQUEST' (status=1) 2019-11-23 15:31:22,105 DEBG 'start-script' stdout output: Sat Nov 23 15:31:22 2019 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 10.154.0.1,comp-lzo no,route 10.154.0.1,topology net30,ping 10,ping-restart 60,ifconfig 10.154.0.106 10.154.0.105,peer-id 25,cipher AES-256-GCM' 2019-11-23 15:31:22,105 DEBG 'start-script' stdout output: Sat Nov 23 15:31:22 2019 OPTIONS IMPORT: timers and/or timeouts modified Sat Nov 23 15:31:22 2019 OPTIONS IMPORT: compression parms modified Sat Nov 23 15:31:22 2019 OPTIONS IMPORT: --ifconfig/up options modified Sat Nov 23 15:31:22 2019 OPTIONS IMPORT: route options modified Sat Nov 23 15:31:22 2019 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified Sat Nov 23 15:31:22 2019 OPTIONS IMPORT: peer-id set Sat Nov 23 15:31:22 2019 OPTIONS IMPORT: adjusting link_mtu to 1629 Sat Nov 23 15:31:22 2019 OPTIONS IMPORT: data channel crypto options modified Sat Nov 23 15:31:22 2019 Data Channel: using negotiated cipher 'AES-256-GCM' Sat Nov 23 15:31:22 2019 NCP: overriding user-set keysize with default Sat Nov 23 15:31:22 2019 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key Sat Nov 23 15:31:22 2019 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key Sat Nov 23 15:31:22 2019 ROUTE_GATEWAY 172.17.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:11:00:03 2019-11-23 15:31:22,106 DEBG 'start-script' stdout output: Sat Nov 23 15:31:22 2019 TUN/TAP device tun0 opened Sat Nov 23 15:31:22 2019 TUN/TAP TX queue length set to 100 Sat Nov 23 15:31:22 2019 /usr/bin/ip link set dev tun0 up mtu 1500 2019-11-23 15:31:22,107 DEBG 'start-script' stdout output: Sat Nov 23 15:31:22 2019 /usr/bin/ip addr add dev tun0 local 10.154.0.106 peer 10.154.0.105 2019-11-23 15:31:22,109 DEBG 'start-script' stdout output: Sat Nov 23 15:31:22 2019 /root/openvpnup.sh tun0 1500 1557 10.154.0.106 10.154.0.105 init 2019-11-23 15:31:22,231 DEBG 'start-script' stdout output: [info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment 2019-11-23 15:31:22,231 DEBG 'start-script' stdout output: [info] Checking we can resolve name 'www.google.com' to address... 2019-11-23 15:31:22,236 DEBG 'start-script' stdout output: [debug] Having issues resolving name 'www.google.com', sleeping before retry... 2019-11-23 15:31:24,178 DEBG 'start-script' stdout output: Sat Nov 23 15:31:24 2019 /usr/bin/ip route add 185.198.242.96/32 via 172.17.0.1 2019-11-23 15:31:24,179 DEBG 'start-script' stdout output: Sat Nov 23 15:31:24 2019 /usr/bin/ip route add 0.0.0.0/1 via 10.154.0.105 2019-11-23 15:31:24,181 DEBG 'start-script' stdout output: Sat Nov 23 15:31:24 2019 /usr/bin/ip route add 128.0.0.0/1 via 10.154.0.105 2019-11-23 15:31:24,182 DEBG 'start-script' stdout output: Sat Nov 23 15:31:24 2019 /usr/bin/ip route add 10.154.0.1/32 via 10.154.0.105 2019-11-23 15:31:24,183 DEBG 'start-script' stdout output: Sat Nov 23 15:31:24 2019 Initialization Sequence Completed 2019-11-23 15:31:27,262 DEBG 'start-script' stdout output: [info] DNS operational, we can resolve name 'www.google.com' to address '172.217.25.132' 2019-11-23 15:31:27,264 DEBG 'start-script' stdout output: [info] Attempting to get external IP using Name Server 'ns1.google.com'... 2019-11-23 15:31:27,336 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address 185.198.242.93 2019-11-23 15:31:27,405 DEBG 'watchdog-script' stdout output: [info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.154.0.106 different, marking for reconfigure 2019-11-23 15:31:27,409 DEBG 'watchdog-script' stdout output: [info] Deluge not running 2019-11-23 15:31:27,412 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI not running 2019-11-23 15:31:27,417 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2019-11-23 15:31:27,417 DEBG 'watchdog-script' stdout output: [info] Attempting to start Deluge... [info] Removing deluge pid file (if it exists)... 2019-11-23 15:31:27,833 DEBG 'watchdog-script' stdout output: [info] Deluge key 'listen_interface' currently has a value of '10.197.0.26' [info] Deluge key 'listen_interface' will have a new value '10.154.0.106' [info] Writing changes to Deluge config file '/config/core.conf'... 2019-11-23 15:31:28,009 DEBG 'watchdog-script' stdout output: [info] Deluge key 'outgoing_interface' currently has a value of 'tun0' [info] Deluge key 'outgoing_interface' will have a new value 'tun0' [info] Writing changes to Deluge config file '/config/core.conf'... 2019-11-23 15:31:28,161 DEBG 'watchdog-script' stdout output: [info] Deluge key 'default_daemon' currently has an undefined value [info] Deluge key 'default_daemon' will have a new value '' [info] Writing changes to Deluge config file '/config/web.conf'... 2019-11-23 15:31:28,418 DEBG 'watchdog-script' stdout output: [info] Deluge process started [info] Waiting for Deluge process to start listening on port 58846... 2019-11-23 15:31:28,638 DEBG 'watchdog-script' stdout output: [info] Deluge process listening on port 58846 2019-11-23 15:31:28,865 DEBG 'watchdog-script' stderr output: Unable to initialize gettext/locale! 'ngettext' Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/deluge/i18n/util.py", line 118, in setup_translation builtins.__dict__['_n'] = builtins.__dict__['ngettext'] KeyError: 'ngettext' 2019-11-23 15:31:30,725 DEBG 'watchdog-script' stdout output: [info] No torrents with state 'Error' found 2019-11-23 15:31:30,726 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... [info] Deluge Web UI started 2019-11-23 15:31:30,732 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2019-11-23 15:31:30,947 DEBG 'watchdog-script' stderr output: Unable to initialize gettext/locale! 2019-11-23 15:31:30,947 DEBG 'watchdog-script' stderr output: 'ngettext' Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/deluge/i18n/util.py", line 118, in setup_translation builtins.__dict__['_n'] = builtins.__dict__['ngettext'] KeyError: 'ngettext' 2019-11-23 15:31:31,740 DEBG 'watchdog-script' stdout output: [info] Privoxy process started [info] Waiting for Privoxy process to start listening on port 8118... 2019-11-23 15:31:31,746 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118

I wanted to replace my cache drive because it was underperforming and overheating, but I accidentally added the new one to the "cache pool" without realizing. While waiting for the btrfs filesystem to build (which was taking forever), my old cache drive went to 75c overheating like crazy, and the read/writes froze. All I could do was restart my server, and now when I try to boot it back on, the Array doesn't start. It's just stuck on "Starting..." and no, I cannot provide a log file because the log won't load.

Having already followed the youtube tutorial setting up a Windows 10 VM, I thought I'd try to get an Ubuntu one set up. I managed to get it working (a bit laggy/choppy though), but for some reason, it won't play sound. The Windows 10 one played sound just fine, and I entered the ich9 XML line on both. I have connected both through VNC and an AnyDesk connection, but no luck. Sound Card is currently set to "none", same with the Windows 10 VM. Any time I try to use the AMD Raven/Family17h audio controller, I get the IOMMU error, and I'd rather not activate things like PCIe ACS override because last time I did that, it messed with my array. Everything else left default. Also, is there are more optimal way to connect remotely than using AnyDesk? For Windows I just use RDP. Splashtop doesn't seem to work for me even though I had everything set up right, and doesn't work for Linux anyway.

I was messing around my VM settings, turning on and off stuff like PCIe Override, and booting the VM at one point seems to have caused a problem in one of my array disks. It's just stuck on the message "Device is disabled, contents emulated". The log endlessly updates with the same error message: ErrorWarningSystemArrayLogin Nov 15 16:17:25 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha977788: link becomes ready Nov 15 16:17:26 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:26 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:26 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:26 Tower rc.docker: mariadb: started succesfully! Nov 15 16:17:26 Tower kernel: br-037f093ede18: port 2(vethfc42120) entered blocking state Nov 15 16:17:26 Tower kernel: br-037f093ede18: port 2(vethfc42120) entered disabled state Nov 15 16:17:26 Tower kernel: device vethfc42120 entered promiscuous mode Nov 15 16:17:26 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): vethfc42120: link is not ready Nov 15 16:17:26 Tower kernel: br-037f093ede18: port 2(vethfc42120) entered blocking state Nov 15 16:17:26 Tower kernel: br-037f093ede18: port 2(vethfc42120) entered forwarding state Nov 15 16:17:26 Tower kernel: br-037f093ede18: port 2(vethfc42120) entered disabled state Nov 15 16:17:26 Tower avahi-daemon[3466]: Joining mDNS multicast group on interface br-037f093ede18.IPv6 with address fe80::42:69ff:feba:b86d. Nov 15 16:17:26 Tower avahi-daemon[3466]: New relevant interface br-037f093ede18.IPv6 for mDNS. Nov 15 16:17:26 Tower avahi-daemon[3466]: Registering new address record for fe80::42:69ff:feba:b86d on br-037f093ede18.*. Nov 15 16:17:26 Tower avahi-daemon[3466]: Joining mDNS multicast group on interface veth79ca4a0.IPv6 with address fe80::1887:c2ff:feca:670f. Nov 15 16:17:26 Tower avahi-daemon[3466]: New relevant interface veth79ca4a0.IPv6 for mDNS. Nov 15 16:17:26 Tower avahi-daemon[3466]: Registering new address record for fe80::1887:c2ff:feca:670f on veth79ca4a0.*. Nov 15 16:17:27 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:27 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:27 Tower kernel: eth0: renamed from vethb7f89ce Nov 15 16:17:27 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethfc42120: link becomes ready Nov 15 16:17:27 Tower kernel: br-037f093ede18: port 2(vethfc42120) entered blocking state Nov 15 16:17:27 Tower kernel: br-037f093ede18: port 2(vethfc42120) entered forwarding state Nov 15 16:17:27 Tower rc.docker: nextcloud: started succesfully! Nov 15 16:17:27 Tower avahi-daemon[3466]: Joining mDNS multicast group on interface vetha977788.IPv6 with address fe80::50aa:27ff:feee:c7cc. Nov 15 16:17:27 Tower avahi-daemon[3466]: New relevant interface vetha977788.IPv6 for mDNS. Nov 15 16:17:27 Tower avahi-daemon[3466]: Registering new address record for fe80::50aa:27ff:feee:c7cc on vetha977788.*. Nov 15 16:17:28 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:28 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:28 Tower rc.docker: Plex: started succesfully! Nov 15 16:17:28 Tower kernel: docker0: port 5(veth6a4fcff) entered blocking state Nov 15 16:17:28 Tower kernel: docker0: port 5(veth6a4fcff) entered disabled state Nov 15 16:17:28 Tower kernel: device veth6a4fcff entered promiscuous mode Nov 15 16:17:28 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): veth6a4fcff: link is not ready Nov 15 16:17:28 Tower kernel: docker0: port 5(veth6a4fcff) entered blocking state Nov 15 16:17:28 Tower kernel: docker0: port 5(veth6a4fcff) entered forwarding state Nov 15 16:17:28 Tower kernel: docker0: port 5(veth6a4fcff) entered disabled state Nov 15 16:17:29 Tower avahi-daemon[3466]: Joining mDNS multicast group on interface vethfc42120.IPv6 with address fe80::605f:51ff:febd:15e0. Nov 15 16:17:29 Tower avahi-daemon[3466]: New relevant interface vethfc42120.IPv6 for mDNS. Nov 15 16:17:29 Tower avahi-daemon[3466]: Registering new address record for fe80::605f:51ff:febd:15e0 on vethfc42120.*. Nov 15 16:17:29 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:29 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:29 Tower kernel: eth0: renamed from veth5d415ef Nov 15 16:17:29 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth6a4fcff: link becomes ready Nov 15 16:17:29 Tower kernel: docker0: port 5(veth6a4fcff) entered blocking state Nov 15 16:17:29 Tower kernel: docker0: port 5(veth6a4fcff) entered forwarding state Nov 15 16:17:29 Tower rc.docker: tautulli: started succesfully! Nov 15 16:17:30 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:30 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:31 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:31 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:31 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:31 Tower avahi-daemon[3466]: Joining mDNS multicast group on interface veth6a4fcff.IPv6 with address fe80::408a:78ff:feba:ab27. Nov 15 16:17:31 Tower avahi-daemon[3466]: New relevant interface veth6a4fcff.IPv6 for mDNS. Nov 15 16:17:31 Tower avahi-daemon[3466]: Registering new address record for fe80::408a:78ff:feba:ab27 on veth6a4fcff.*. Nov 15 16:17:32 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:32 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:33 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:33 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:34 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:34 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:35 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:35 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:35 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:36 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:36 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:37 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:37 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:38 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:38 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:39 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:39 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:39 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:40 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:40 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:41 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:41 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:42 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:42 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:43 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:43 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:43 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:44 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:44 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:45 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:45 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:46 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:47 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:47 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:47 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:48 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:48 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:48 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:49 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:50 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:50 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:51 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:52 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:52 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:52 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:52 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:53 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:53 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:53 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:54 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:55 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:56 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:56 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:56 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:56 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:57 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:57 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:57 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:17:58 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:17:59 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:18:00 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:18:00 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:18:00 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:18:01 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:18:01 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:18:01 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:18:01 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:18:02 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:18:03 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:18:04 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:18:04 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:18:04 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:18:05 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:18:05 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:18:05 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:18:05 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:18:06 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:18:07 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:18:08 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:18:08 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:18:09 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:18:09 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:18:09 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Nov 15 16:18:09 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Nov 15 16:18:09 Tower root: error: /webGui/include/DeviceList.php: wrong csrf_token Is there a way to fix this? Did I permanently break one of my HDDs?

Why does it say I don't have permission to save anything inside the proxy-confs file in Windows SMB? I can read and write everything else in appdata except for this folder. Even if I set appdata to public, I still get this message.

I don't know if this is the right place to ask, sorry if it isn't. I was following that Spaceinvader One guide for this, and noticed he creates a Share for downloads + folders for both complete and incomplete. But Radarr automatically copies downloads to the media folder, which means I'm always ending up with two of the same movie for every download: one in "completed" the other in "movies". Is there a way to address this so I'll always just have one movie file? Sorry if it's a noob question.

I'm still fairly new to servers in general, and this will be my first server build, so I want to build up as much knowledge as possible before I start spending money. As of right now, I intend to use the server mainly for storage and as a Plex Media Server that can handle about 2-3 1080p transcodes. So far, I have only purchased the case, which has x3 hotswap 3.5" HDD bays and x5 internal 3.5" HDD bays. There are also 2 unsused 5.25" bays which leave the potential for expansion. As of right now, the plan is to have a 120GB SSD for cache, a 3TB HDD for Parity and 2-3 HDDs for storage. Budget: Not including any of the HDDs, I'd like to keep it under $500 AUD (about $350USD) CPU: I am currently deciding between the Ryzen 2400G and the Ryzen 2600. The former is $220 AUD ($154 USD), the latter is $245 AUD ($172 USD). I am still trying to gauge what kind of advantages the more expensive 6-core, 12-thread CPU entails, and whether or not it's worth the slight increase in price for me. Again, I'm initially building for storage and a media server capable of transcoding, but I may yet expand my horizons; I can definitely see myself using VMs at some point. Motherboard: I'm going to choose a B450 Motherboard to avoid potential compatibility issues with 2XXX-series Ryzen CPUs. I'm choosing between the MSI B450M-PRO-M2-V2 ($105 AUD, $73 USD), the ASUS Prime B450M-A ($125 AUD, $87 USD) and the Asus TUF B450-PLUS ($119 AUD, $83 USD). The first is the cheapest, most affordable option, the latter two both have 6 SATA ports whereas the MSI only had 4, and the B450M-A has ECC compatibility, which is something I'm still not sure if I want. I hear a lot of people expand their SATA ports with PCI-E Controller Cards like this. Would this work for HDDs in the Unraid storage array? Ram: G.Skill Ripjaws V 8GB (2x4GB) 2400MHz DDR4 - Nothing too fancy. Cheap DDR4 server solution. PSU: Corsair - VS 450 W 80+ Certified ATX Power Supply - I'm still unsure as to how big of a difference going gold would make to long-term cost. If it's significant, I could always bump up to this Taking all that into account, am I doing anything wrong? Could I be doing better? The builds in the FAQ seem to be pretty outdated so it's still a bit hard to gauge exactly what I should be doing. I'm also interested in knowing whether or not I should bother investing in HDD cooling. The 3 HDDs in the enclosure already have a small fan blowing into them; should I do the same for the ones in the internal bays? Some people have suggested used components to me in the past, but here in Australia, the market for them is drier than the Sahara, particularly the motherboards. I figure it's better to go new.