JimmyOdcu

My unifi controller recently began to fail to load. Attempts to reinstall / restore using AppData backup/restore plugin have resulted in no change. Attached is the container log. Anyone have any suggestions before I completely reset & rebuild my network First line of failure appears to be: Exception in thread "launcher" java.lang.IllegalStateException: Tomcat failed to start up unraid-network-application_log.txt

How do you check / change the tag you're using without uninstalling / reinstalling from CA? Or is that the recommended method?

Having trouble with SWAP + DuckDNS config based on SpaceInvader's tutorials using mysubdoman.duckdns.org (I may add my own domain later, but leaving it as is for now) (DuckDNS subdomain changed for privacy/security) abc123.duckdns.org resolves to my WAN IP correctly swag & vaultwarden containers are on 'proxynet' network swag 172.18.0.3:443/TCP <-> 192.168.111.61:1443 & 172.18.0.3:80/TCP <-> 192.168.111.61:180 vaultwarden 172.18.0.2:80/TCP <-> 192.168.111.61:4743 vaultwarden.subdomain.conf file (I've made changes here): #BITWARDEN # make sure that your domain has dns has a cname or a record set for the subdomain bitwarden # This config file will work as is when using a custom docker network the same as letesencrypt (proxynet). # However the container name is expected to be "bitwardenrs" as it is by default the template as this name is used to resolve. # If you are not using the custom docker network for this container then change the line "server bitwardenrs:80;" to "server [YOUR_SERVER_IP]:8086;" Also remove line 7 #resolver 127.0.0.11 valid=30s; upstream vaultwarden { server vaultwarden:80; } server { listen 443 ssl; server_name abc123.*; include /config/nginx/ssl.conf; client_max_body_size 128M; location / { proxy_pass http://vaultwarden; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location /notifications/hub { proxy_pass http://vaultwarden; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } location /notifications/hub/negotiate { proxy_pass http://vaultwarden; } }

I've had my binhex-delugevpn container running for about a year or so now.. suddenly in the past few days I get 192.168.111.61 refused to connect (access via local LAN). I'm a bit of a docker newb, so please let me know what info you might need to assist. TIA Here's my Log File: Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2021-08-31 01:44:31.524777 [info] System information Linux 53c7e0c8be09 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux 2021-08-31 01:44:31.580052 [info] OS_ARCH defined as 'x86-64' 2021-08-31 01:44:31.634676 [info] PUID defined as '99' 2021-08-31 01:44:31.752444 [info] PGID defined as '100' 2021-08-31 01:44:31.916102 [info] UMASK defined as '000' 2021-08-31 01:44:31.968548 [info] Permissions already set for volume mappings 2021-08-31 01:44:32.030580 [info] Deleting files in /tmp (non recursive)... 2021-08-31 01:44:32.091722 [info] VPN_ENABLED defined as 'yes' 2021-08-31 01:44:32.146326 [info] VPN_CLIENT defined as 'openvpn' 2021-08-31 01:44:32.198384 [info] VPN_PROV defined as 'custom' 2021-08-31 01:44:32.261029 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn 2021-08-31 01:44:32.361116 [info] VPN remote server(s) defined as '94-1-ca.cg-dialup.net,' 2021-08-31 01:44:32.406572 [info] VPN remote port(s) defined as '443,' 2021-08-31 01:44:32.452242 [info] VPN remote protcol(s) defined as 'udp,' 2021-08-31 01:44:32.504500 [info] VPN_DEVICE_TYPE defined as 'tun0' 2021-08-31 01:44:32.556325 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS) 2021-08-31 01:44:32.608175 [info] LAN_NETWORK defined as '192.168.111.0/24' 2021-08-31 01:44:32.660165 [info] NAME_SERVERS defined as '208.67.222.222,208.67.220.220,209.222.18.222,84.200.69.80,37.235.1.174,209.222.18.218,37.235.1.177,84.200.70.40' 2021-08-31 01:44:32.712107 [info] VPN_USER defined as '****' 2021-08-31 01:44:32.764029 [info] VPN_PASS defined as '****' 2021-08-31 01:44:32.816342 [info] ENABLE_PRIVOXY defined as 'yes' 2021-08-31 01:44:32.869161 [info] ADDITIONAL_PORTS not defined (via -e ADDITIONAL_PORTS), skipping allow for custom incoming ports 2021-08-31 01:44:32.921484 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info' 2021-08-31 01:44:32.973998 [info] DELUGE_WEB_LOG_LEVEL defined as 'info' 2021-08-31 01:44:33.036572 [info] Starting Supervisor... 2021-08-31 01:44:33,436 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing 2021-08-31 01:44:33,436 INFO Set uid to user 0 succeeded 2021-08-31 01:44:33,440 INFO supervisord started with pid 6 2021-08-31 01:44:34,443 INFO spawned: 'start-script' with pid 172 2021-08-31 01:44:34,446 INFO spawned: 'watchdog-script' with pid 173 2021-08-31 01:44:34,446 INFO reaped unknown pid 7 (exit status 0) 2021-08-31 01:44:34,456 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2021-08-31 01:44:34,456 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2021-08-31 01:44:34,456 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2021-08-31 01:44:34,565 DEBG 'start-script' stdout output: [info] Adding 208.67.222.222 to /etc/resolv.conf 2021-08-31 01:44:34,572 DEBG 'start-script' stdout output: [info] Adding 208.67.220.220 to /etc/resolv.conf 2021-08-31 01:44:34,578 DEBG 'start-script' stdout output: [info] Adding 209.222.18.222 to /etc/resolv.conf 2021-08-31 01:44:34,584 DEBG 'start-script' stdout output: [info] Adding 84.200.69.80 to /etc/resolv.conf 2021-08-31 01:44:34,590 DEBG 'start-script' stdout output: [info] Adding 37.235.1.174 to /etc/resolv.conf 2021-08-31 01:44:34,596 DEBG 'start-script' stdout output: [info] Adding 209.222.18.218 to /etc/resolv.conf 2021-08-31 01:44:34,603 DEBG 'start-script' stdout output: [info] Adding 37.235.1.177 to /etc/resolv.conf 2021-08-31 01:44:34,609 DEBG 'start-script' stdout output: [info] Adding 84.200.70.40 to /etc/resolv.conf 2021-08-31 01:46:24,989 DEBG 'start-script' stdout output: [crit] '94-1-ca.cg-dialup.net' cannot be resolved, possible DNS issues, exiting... 2021-08-31 01:46:24,989 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23233414805920 for <Subprocess at 23233414807168 with name start-script in state RUNNING> (stdout)> 2021-08-31 01:46:24,989 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23233411213344 for <Subprocess at 23233414807168 with name start-script in state RUNNING> (stderr)> 2021-08-31 01:46:24,989 INFO exited: start-script (exit status 1; not expected) 2021-08-31 01:46:24,990 DEBG received SIGCHLD indicating a child quit