Zervun

Members
  • Posts

    15
  • Joined

  • Last visited

Zervun's Achievements

Noob

Noob (1/14)

2

Reputation

  1. Sounds like an issue with your VPN provider. I would wager a guess that there are disconnection issues, retries or something of the sort. Have you checked logs? The first stop every single time is to look at your appdata logs of the container. Is your VPN provider getting blocked by IPS/IDS and/or DNS lists?
  2. I tried searching the thread and have read the github FAQ. I don't think I've come across this question. I've had wireguard successfully running for a long time. Today, it looks like mullvad changed one of their endpoints I was using and/or they are having issues with the endpoint. Absolutely nothing to do with the container/functionality. Obviously I couldn't access the gui, searched the logs and it was issues with mullvad connecting. So I grabbed a new set off endpoints from them, deleted the old wg.conf file, uploaded a new endpoint, chowned it properly and blam it worked again like magic as I expected it would. My question is - when we get these VPN endpoints from the providers, they are usually bundled up into a dozen or so endpoints in a zip file per whatever location you select. I obviously used one of those. Is there some best practice to be able to change the endpoint? I gather I could just open wg.conf file and edit that but I was wondering what happens for example if I just throw all the endpoint conf files in the wireguard directory? Will it just use the first one? Or will it bug out? Can I just leave the others there for quick reference? This is obviously an extremely small annoyance and has nothing to do with the container itself but how wireguard operates. Since I have files all over the place I'm just wondering if I could drop them in the wireguard folder, so I could just ssh in and have the files there for copy and pasting. I'm assuming with how wireguard operates I couldn't create a script that if the first one failed it would use the next etc. As always thank you so much binhex for maintaining these containers they are awesome.
  3. Ya, I'm not sure of what my issue was. Unfortunately I was without power for a week and internet for about a month during the Oregon storms. When I started it back up it was the Plex permissions changes and Nvidia changes. Not sure if either of those caused an issue, or I got some corruption somewhere. I did update things but it was crashing quite a bit. I did try and do some database restores, but they didn't work on this last pass. I did install binhex plex and it is working fine, so I migrated over to that. This was before I knew that you could copy all your meta data and so forth over but oh well. I might reinstall and migrate back to binhex plexpass in the future.
  4. Same - this has been happening to me once or twice a day. Restarting fixes this until today, where about a few minutes ago I can't access the webgui at all. Tryed updating the container etc. All other binhex dockers (sonar, radar, sabvpn, delug, etc work fine) I check logs, nothing seems unusual. Looks like it starts but no webgui
  5. Just a note, after the latest forced update everything is working well again.
  6. Having trouble connecting to Mullvad this morning and the webui. Looks like it is getting a soft connection reset. Force updated to the latest image (was working yesterday). Edit: I can connect to mullvad on other computers. Couldn't find any errors in the sup log file. Sup file attached supervisord.log
  7. Ah makes sense - annoying. I see it now and missed it when looking through the log. Thanks for looking at this! I really appreciate it!
  8. Done and attached - could it be something to do with the fact that I have remote as IP addresses and not names? I read that it does an nslookup on all remote supervisord.log
  9. I haven't been able to connect since after the updated it just hangs on trying to make a connection to mullvad vpn. Was working yesterday. Tried restarting multiple times and waited for it to connect for 15+ minutes. Connection works from other computers fine. I can telnet to the IP over port 443 from the unraid server Any help would be appreciated 2020-09-21 10:42:55,790 DEBG 'start-script' stdout output: Mon Sep 21 10:42:55 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]104.200.129.150:443 Mon Sep 21 10:42:55 2020 Socket Buffers: R=[87380->1048576] S=[65536->1048576] Mon Sep 21 10:42:55 2020 Attempting to establish TCP connection with [AF_INET]104.200.129.150:443 [nonblock] 2020-09-21 10:43:27,794 DEBG 'start-script' stdout output: Mon Sep 21 10:43:27 2020 TCP: connect to [AF_INET]104.200.129.150:443 failed: Connection timed out Mon Sep 21 10:43:27 2020 SIGHUP[connection failed(soft),init_instance] received, process restarting 2020-09-21 10:43:27,795 DEBG 'start-script' stdout output: Mon Sep 21 10:43:27 2020 WARNING: file 'credentials.conf' is group or others accessible Mon Sep 21 10:43:27 2020 OpenVPN 2.4.9 [git:makepkg/9b0dafca6c50b8bb+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 20 2020 Mon Sep 21 10:43:27 2020 library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.10 2020-09-21 10:43:27,796 DEBG 'start-script' stdout output: Mon Sep 21 10:43:27 2020 Restart pause, 5 second(s) Here is my openvpn script remote 104.200.129.150 443 client dev tun proto tcp-client remote-random cipher AES-256-CBC resolv-retry infinite nobind persist-key verb 3 remote-cert-tls server ping 10 ping-restart 60 sndbuf 524288 rcvbuf 524288 auth-user-pass credentials.conf ca mullvad_ca.crt tls-cipher TLS-DHE-RSA-WITH-AES-256-GCM-SHA384:TLS-DHE-RSA-WITH-AES-256-CBC-SHA pull-filter ignore "route-ipv6" pull-filter ignore "ifconfig-ipv6"
  10. 4 SSD's in raid 10 for cache pool. I have 8x 10tb shucked WD whites for spinners/array with 2 parity drives of those. I haven't noticed the error on my esxi cluster, might not have the smart notifications setup right on that, or it is because it is on a dell h710 controller doing hardware raid in a dell r720xd and that error may not be noticed on the h710 The other 4 mx500's I have are on a ESXI cluster. (I have way too many servers about ~200 TB total, ESXI, Unraid, Freenas, Synology)
  11. Yep, going to do that, just not ideal as I'd like to monitor it
  12. Chock this up for another person with the issue. Will open a ticket with crucial as well as this is annoying. I have 8 of 1tb mx500's, all bought at different times over the past few years. The 4 I have in unraid all periodically report "current pending sector is 1" and then clear. Immediately after reporting field 197 of smart shows 0, so it must resolve very quickly.
  13. Solved, bitdefender was detecting update.php as an exploit in online threat protection when trying to set some unraid settings
  14. Hello, I'm having an issue with notifications. I tried searching but most of the threads I found were fairly old and it seems that some of the notification problems were fixed in newer versions. I am on version 6.6.7 Pro, with a fresh install. The only things I have done is install, parity and format disks. My next step was to setup notifications I enabled notifications for both browser and agents, and when enabling the notifications it does look like it is enabling them - below is a tail of syslog when I hit "apply" under the notifications settings. Apr 1 14:16:42 Tower ool www[1397]: /usr/local/emhttp/plugins/dynamix/scripts/notify 'cron-init' The notifications are working through the browser (I get notifications of array status etc), but I cannot get them to work with the agents (I've tried pushbullet and pushover). When I go into either pushbullet and pushover, enable, put in the required keys, and hit "apply", it seems to do nothing. There is nothing in the syslog when I do this. The plugin stays disabled as nothing has happened. I read before that this was broken and people were having to manually adjust the scripts in scripts at /boot/config/plugins/dynamix/notifications, but the only thing I have in there is the archive and unread directory. This was supposed to be fixed in 6.6.5 I've also tried on three different browsers (IE, chrome, firefox) and they all respond the same way - I figured I would check that out even though I have disabled any ad-blocking no-script and the like. Am I missing a step where the agent plugins need to be installed or something? Any help would be appreciated.