twistedlabel

Members
  • Posts

    9
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

twistedlabel's Achievements

Noob

Noob (1/14)

2

Reputation

1

Community Answers

  1. 🤦‍♂️ Sorry, let me try that again haha supervisord.log
  2. Sorry for adding another "cant get to the web ui" post but after a lot of digging I cant find an answer. Im running Unraid 6.12.3 Im using Windscribe VPN (ive use this with DelugeVPN in the past for years without issue) I haven't used DelugeVPN for quite a while. Ive been using rTorrentVPN but it stopped working and I recently learned that is no more. What I've tried: Updating my ovpn file... and tried lots of different places Reinstalling the container and setting it back up. Setting VPN_ENABLED to "no" Drinking... here is my log: 2023-08-06 17:46:19,423 DEBG 'start-script' stdout output: 2023-08-06 17:46:19 Note: Treating option '--ncp-ciphers' as '--data-ciphers' (renamed in OpenVPN 2.5). 2023-08-06 17:46:19,425 DEBG 'start-script' stdout output: 2023-08-06 17:46:19 WARNING: file 'credentials.conf' is group or others accessible 2023-08-06 17:46:19,426 DEBG 'start-script' stdout output: 2023-08-06 17:46:19 OpenVPN 2.6.5 [git:makepkg/cbc9e0ce412e7b42+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Jun 13 2023 2023-08-06 17:46:19 library versions: OpenSSL 3.1.1 30 May 2023, LZO 2.10 2023-08-06 17:46:19 DCO version: N/A 2023-08-06 17:46:19,426 DEBG 'start-script' stdout output: 2023-08-06 17:46:19 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2023-08-06 17:46:19,427 DEBG 'start-script' stdout output: 2023-08-06 17:46:19 TCP/UDP: Preserving recently used remote address: [AF_INET]37.120.213.163:443 2023-08-06 17:46:19,428 DEBG 'start-script' stdout output: 2023-08-06 17:46:19 Attempting to establish TCP connection with [AF_INET]37.120.213.163:443 2023-08-06 17:46:19,594 DEBG 'start-script' stdout output: 2023-08-06 17:46:19 TCP connection established with [AF_INET]37.120.213.163:443 2023-08-06 17:46:19 TCPv4_CLIENT link local: (not bound) 2023-08-06 17:46:19 TCPv4_CLIENT link remote: [AF_INET]37.120.213.163:443 2023-08-06 17:46:20,125 DEBG 'start-script' stdout output: 2023-08-06 17:46:20 VERIFY OK: depth=2, C=CA, ST=ON, L=Toronto, O=Windscribe Limited, OU=Systems, CN=Windscribe Node CA X1 2023-08-06 17:46:20,125 DEBG 'start-script' stdout output: 2023-08-06 17:46:20 VERIFY OK: depth=1, C=CA, ST=ON, L=Toronto, O=Windscribe Limited, OU=Systems, CN=Windscribe Node CA X2 2023-08-06 17:46:20,126 DEBG 'start-script' stdout output: 2023-08-06 17:46:20 VERIFY KU OK 2023-08-06 17:46:20 Validating certificate extended key usage 2023-08-06 17:46:20 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication 2023-08-06 17:46:20 VERIFY EKU OK 2023-08-06 17:46:20 VERIFY X509NAME OK: C=CA, ST=ON, L=Toronto, O=Windscribe Limited, OU=Systems, CN=zrh-112.windscribe.com 2023-08-06 17:46:20 VERIFY OK: depth=0, C=CA, ST=ON, L=Toronto, O=Windscribe Limited, OU=Systems, CN=zrh-112.windscribe.com 2023-08-06 17:46:20,631 DEBG 'start-script' stdout output: 2023-08-06 17:46:20 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bit RSA, signature: RSA-SHA256 2023-08-06 17:46:20 [zrh-112.windscribe.com] Peer Connection Initiated with [AF_INET]37.120.213.163:443 2023-08-06 17:46:20,971 DEBG 'start-script' stdout output: 2023-08-06 17:46:20 TUN/TAP device tun0 opened 2023-08-06 17:46:20 net_iface_mtu_set: mtu 1500 for tun0 2023-08-06 17:46:20,971 DEBG 'start-script' stdout output: 2023-08-06 17:46:20 net_iface_up: set tun0 up 2023-08-06 17:46:20 net_addr_v4_add: 10.121.60.40/23 dev tun0 2023-08-06 17:46:20 /root/openvpnup.sh tun0 1500 0 10.121.60.40 255.255.254.0 init 2023-08-06 17:46:20,976 DEBG 'start-script' stdout output: 2023-08-06 17:46:20 Initialization Sequence Completed 2023-08-06 17:46:20 Data Channel: cipher 'AES-256-GCM', peer-id: 0 2023-08-06 17:46:20 Timers: ping 5, ping-restart 60 2023-08-06 17:46:20,977 DEBG 'start-script' stdout output: [debug] Waiting for valid VPN gateway IP addresses from tunnel... 2023-08-06 17:46:20,978 DEBG 'start-script' stdout output: [debug] Waiting for valid VPN adapter IP addresses from tunnel... 2023-08-06 17:46:22,005 DEBG 'start-script' stdout output: [debug] Valid local IP address from tunnel acquired '10.121.60.40' 2023-08-06 17:46:22,006 DEBG 'start-script' stdout output: [debug] Valid gateway IP address from tunnel acquired '' 2023-08-06 17:46:22,006 DEBG 'start-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2023-08-06 17:46:22,098 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2023-08-06 17:46:37,209 DEBG 'start-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.203.100' 2023-08-06 17:46:37,210 DEBG 'start-script' stdout output: [info] Attempting to get external IP using 'http://checkip.amazonaws.com'... 2023-08-06 17:46:37,384 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.203.100' 2023-08-06 17:46:38,526 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address 37.120.213.169 2023-08-06 17:46:38,528 DEBG 'start-script' stdout output: [info] VPN provider 'custom' not supported for automatic port forwarding, skipping incoming port assignment 2023-08-06 17:46:38,599 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2023-08-06 17:46:38,608 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2023-08-06 17:46:38,609 DEBG 'watchdog-script' stdout output: [info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.121.60.40 different, marking for reconfigure 2023-08-06 17:46:38,613 DEBG 'watchdog-script' stdout output: [info] Deluge not running 2023-08-06 17:46:38,618 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI not running 2023-08-06 17:46:38,622 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2023-08-06 17:46:38,622 DEBG 'watchdog-script' stdout output: [info] Attempting to start Deluge... [info] Removing deluge pid file (if it exists)... 2023-08-06 17:46:38,871 DEBG 'watchdog-script' stdout output: [info] Deluge key 'listen_interface' currently has a value of '10.111.128.41' [info] Deluge key 'listen_interface' will have a new value '10.121.60.40' [info] Writing changes to Deluge config file '/config/core.conf'... 2023-08-06 17:46:39,067 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'... 2023-08-06 17:46:39,260 DEBG 'watchdog-script' stdout output: [info] Deluge key 'default_daemon' currently has a value of '92a4905269544d599638ddef384308dd' [info] Deluge key 'default_daemon' will have a new value '92a4905269544d599638ddef384308dd' [info] Writing changes to Deluge config file '/config/web.conf'... 2023-08-06 17:46:39,509 DEBG 'watchdog-script' stdout output: [info] Deluge process started 2023-08-06 17:46:39,509 DEBG 'watchdog-script' stdout output: [info] Waiting for Deluge process to start listening on port 58846... If I open my log fast enough I also get this "insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory" further up in them. I really hope this isn't a softball answer but Im at a loss. Thanks!
  3. @trurl Thank you so much for pointing me in the right direction. I dont know in what fever dream state i decided to add those port forwarding options in my router but they have been nuked. I dont need remote access to my server other than through the My Server plugin and that is now set up properly. I reset my DHCP by deleting config/network.cfg on my flash drive I then reset my port numbers by editing the config/ident.cfg file on my flash drive. Reading though the list of security best practices, I thankfully have done/follow most of them (with the obvious exception of my huge port forwarding mistake) I now have access to my web GUI and have a lot more knowledge in my tool belt. Thanks again!!!
  4. I did not. Look into that. And its offline now. Thank you. Aside from needing to change that port is there anything else i can do/should worry about those bots? Ill get the ports resent and get it bak to the default DHCP. The IP address it has is on my system but ill redo things the correct way moving forward. Ill also get some diagnostics going on my RAM. Thanks again!
  5. This was a solution to several other users who had lost access to their GUI as a result of a conflict with docker port numbers. Their description of the issue sounded most similar to my situation compared to the other fixes i came across. And since all of my dockers are running except Home Assistant I thought it was worth a try incase I mucked something up in that setup. I dont have an attached monitor and keyboard, but I can make that happen. Yes. I can ssh into it also. Thats how I was able to generate a diagnostic report as well as tell my server to boot into safe mode though safari using my server.local name, using the ip address, and using the link to my server though the My Server section of this forum. All of which is how I normally accessed the GUI In trying to up my networking knowledge I have very recently been made aware that this is the best practice. And, of course, since everything has been running smoothly I hadn't made time to implement this change in my system. Ive only been following unraid tutorials up to this point so ive got a lot more to learn.
  6. So, like many others I am no longer able to access my Unraid GUI after booting back up from a clean shutdown. I still have access to all of the docker images that I can remember the port numbers of. The only one that doesn't seem to be working is my Home Assistant, which was the most recently installed docker. I have tried every fix for this that i can find to no avail. I wouldn't call my self an Unraid NOOB but I am also far from an expert so theres a reasonable chance I didn't implement one of the fixes correctly. Some of the fixes I've tried: Shutting down docker and restarting nginx changing the Unraid port number to several different unused ones booting in safe mode removing nvida plugin (this was a fix for me one of the other times i couldn't access the GUI, but that was after swapping almost all of my hardware out. I have restarted with no issue several times with my new hardware) Two oddities I've noticed: The recently installed Home Assistant docker doesn't seem to be working (I cant remember restarting my server after setting up the Home Assistant docker) my router doesn't show a DNS lease to my unraid server but it shows up on a scan of my network with the self assigned ip address (not sure if this even matters as I don't know if it has ever shown up in my router, its just an odd thing I noticed. Im definitely a network noob I did manage to get a diagnostic file which I've attached. Thank you for any help you can provide. timp-diagnostics-20230129-1242.zip
  7. I ran into the same problem when setting up the My Servers plugin and I was pulling my hair out trying to figure out how to change my router settings. Turns out using cloudflair's 1.1.1.1 dns was my issue, not the router. I changed over to googles, waited for a bit and was able to generate the SSL certificate.