puma1824

Members
  • Posts

    10
  • Joined

  • Last visited

Posts posted by puma1824

  1. 6 minutes ago, DZMM said:

    I've followed the video guide https://www.youtube.com/watch?v=I58LTMKyeYw and I can connect to my server 172.30.12.2 from my VPN server 172.30.12.2:943.

     

    The problem I'm having is I've moved my dockers to other IPs e.g. 172.30.12.80 doe nzbget and I can't connect to them via the VPN?  Do I need to assign an IP for the VPN server e.g. 172.30.12.81 as well?  Would this mean though that I won't be able to connect to my unraid server on 172.30.12.2?

     

    Or, is there another solution?

     

    Thanks

     

    can you ping .80 when you're logged into VPN?

     
  2. On 10/19/2017 at 10:49 AM, thomast_88 said:

     

    I'm myself converting down to a single cache drive. Multiple drives is just too unstable for me (and for many other it seems). Even when balancing each day (!!).

     

    Is it possible to run raid1 cache with XFS on unraid? Or does it even make any sense?

     

    On 10/27/2017 at 8:57 AM, wirenut said:

    i received unraid notification email of an update to the container from overnight. container auto update enabled in unraid. now i cannot connect from phone app or work computer.

    log just keeps repeating TLS Error: cannot locate HMAC in incoming packet from [AF_INET]XX.XXX.XXX.XXX:1194

    I tried restarting container, did not change.

    Is there something I need to change on my end as a result of the container update?

    7

     

    On 10/28/2017 at 10:12 AM, wgstarks said:

     

     

     

    Ok. New reply from OpenVPN-AS support-

    
    It looks like the upgrade procedure you followed broke the database.
    
    Try the following to reset the TLS settings:
    
    Go to Advanced VPN in the Admin UI.
    Disable the "Enable TLS authentication" option.
    Save settings.
    Update running servers.
    Enable the "Enable TLS authentication" option.
    Save settings.
    Update running servers.
    
    Now try again.

    This fixed the problem for me. @linuxserver.io Looks like updating the docker caused an incompatibility of the local database???

     

    deusxanime try this ^

    • Like 3
    • Upvote 2
  3. 4 hours ago, puncho said:

    I followed space invader's tutorial, tested it and it works if I use the user 'admin'. I tried to set up another user but was unable to log on, says login failed? I created the user/password by telneting into the docker as shown in the video.

     

    Also, since I only have the DDNS (xxxxxx.duckdns.org), does that mean I can't make use of the SSL certificate? Is it less secure then/what other downsides are there? Thanks

    1

     

    Yeah, I followed his directions prior the upgrade and all WAS good.  After the upgrade couldn't get the 2nd user setup like you when I tried to re-setup.  

     

    Ad for using duckdns, maybe you can use the other authentication methods by temporarily setting up a ftp / web site to register for a cert.  

  4. 17 minutes ago, thomast_88 said:

     

    I'm myself converting down to a single cache drive. Multiple drives is just too unstable for me (and for many other it seems). Even when balancing each day (!!).

     

    Is it possible to run raid1 cache with XFS on unraid? Or does it even make any sense?

     

    What's your backup plan for your Cache drive? I'm trying to figure out the best way to proceed with a single drive.  Thanks.