Jump to content

Zervun

Members
 View Profile  See their activity

  • Posts

    15

  • Joined

  • Last visited

 Content Type 

Posts posted by Zervun

    [Support] binhex - DelugeVPN

    in Docker Containers

    Posted

    3 hours ago, gzibell said:

    Well this is about the strangest thing I have came across.  Not sure if there is actually a question in here but figured I would throw it out there just in case someone has seen something like it.  Been trying to track down something funky that has been happening. 

     

    Grab 6 linux distros and add them to deluge.  Runs for 5-10 mins and I completely lose connectivity(my whole house).  Odd, ssh into my USG, can't ping google 8.8.8.8 nothing.  K, lets disconnect the WAN cable and reconnect.  Boom, internet back up house wide....ok lets start the download again.  Same thing over and over and over again.  WTF?  

     

    So then the smart guy in me says ok download utorrent to your desktop and do the same thing.  A short while later I have 6 shiny new distros in my downloads folder.  ok...

     

    Another idea. Lets set VPN_ENABLED to no.  Fire it back up, 6 shiny new distros on my server with no issues.  

     

    This seems like a stretch but could traffic from deluge be breaking my USG somehow or could my ISP be doing something funky?

     

     

     

    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?

    [Support] binhex - DelugeVPN

    in Docker Containers

    Posted · Edited by Zervun

    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.

     

     

     

     

    [Support] binhex - Plex Pass

    in Docker Containers

    Posted

    13 hours ago, BomB191 said:

    @Zervun @regorian

     

    So I seem to have resolved the issue. My pinning was screwed up. 

    I also forced all the database optimisations to run and extended my daily maintenance window

     

     

    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.

    [Support] binhex - Plex Pass

    in Docker Containers

    Posted

    On 3/31/2021 at 6:48 AM, regorian said:

     

    I am having a fairly similar issue, where the webui becomes unresponsive and playback is interrupted. Restarting the container resolves this, however I did not notice any events within the container log that may point to an error. I will be on the lookout the next time it occurs.

     

    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

    [Support] binhex - DelugeVPN

    in Docker Containers

    Posted · Edited by Zervun

    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

    [Support] binhex - DelugeVPN

    in Docker Containers

    Posted

    6 minutes ago, binhex said:

    thanks for the log, ive spotted the issue, its this:- 

    
2020-09-21 11:50:01,367 DEBG 'start-script' stderr output:
iptables v1.8.5 (legacy): unknown protocol "tcp-client" specified
Try `iptables -h' or 'iptables --help' for more information.

2020-09-21 11:50:01,394 DEBG 'start-script' stderr output:
iptables v1.8.5 (legacy): unknown protocol "tcp-client" specified
Try `iptables -h' or 'iptables --help' for more information.

    so annoyingly openvpn uses 'tcp-client' and iptables uses 'tcp' so there has to be some modification of the value to account for this, i did previously have this in place but things have changed so i need to rework the check, on a fix now, should have something within the hour...

    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!

    [Support] binhex - DelugeVPN

    in Docker Containers

    Posted · Edited by Zervun

    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"

    (Still NOT Solved) current pending sector is 1on new SSD Cache

    in General Support

    Posted · Edited by Zervun

    7 minutes ago, trurl said:

    How are you using those 4 SSDs in Unraid? SSDs are great for the cache pool, but SSDs are not recommended in the parity array.

    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)

    SOLVED: Notifications not saving

    in General Support

    Posted · Edited by Zervun
    solved

    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.

×
×
  • Create New...