Jump to content

cgrd

Members
  • Posts

    7
  • Joined

  • Last visited

Posts posted by cgrd

  1. Thanks for the update, I appreciate your time.

     

    I updated the container June 15, and no further updates show. The configuration files are set to 650 (nobody:users).

     

    I have my config files reference a file, rather than having the cert info inline. Ex:

    crl-verify crl.rsa.2048.pem
    ca ca.rsa.2048.crt

     

    So if the parsing of the .ovpn file is looking for the data inline, that may be my root cause.

     

    I can expand the file permissions and force a container update, and see if that works.

     

    Thanks again!

  2. On 6/5/2024 at 8:24 AM, Arcaeus said:

    Hey everyone. Just updated to the new version of DelugeVPN and now I can't open the webGUI. I use PIA as my VPN client. I personally haven't changed any of the settings, just clicked "Update Container" or whatever through the Docker tab. Now when I click on webUI, I just get a "Connection Refused" error.

     

    I had the same error. Digging around the issue logged:
     

    2024-06-05 09:19:38 OpenSSL: error:068000E9:asn1 encoding routines::utctime is too short:
    2024-06-05 09:19:38 OpenSSL: error:0688010A:asn1 encoding routines::nested asn1 error:Field=revocationDate, Type=X509_REVOKED
    2024-06-05 09:19:38 OpenSSL: error:0688010A:asn1 encoding routines::nested asn1 error:Field=revoked, Type=X509_CRL_INFO
    2024-06-05 09:19:38 OpenSSL: error:0688010A:asn1 encoding routines::nested asn1 error:Field=crl, Type=X509_CRL

     

    OpenSSL v3.3.x will reject invalid dates in the CRL file, and PIA supplies a CRL with invalid dates; I've attached a screenshot showing the CRL parse, and the likely source.

     

    The obvious long term solution would be to request PIA update their CRL with the expected valid dates.

     

    I removed the "crl-verify" directive/command from my ovpn configuration file, and resolved the error. Everything is up and running.

     

    However, I'm unsure if this is a wise course of action, I'll let others such as @binhex weigh in!

    pia_bad_utc.jpg

  3. 27 minutes ago, ich777 said:

    One recommendation would be to add a line where you it only keeps the last 10 backups and if a new one is found that the oldest one is deleted. :)

    There are many ways with ls -alt or find... :)

    I'm not sure how long my gaming group is going to be on the Valheim kick, and at 16mb/day, I'm not overly concerned with storage. BUT you're right; it's good practice. I've edited the script to include a clean up action. Thanks!

    • Like 1
  4. On 2/9/2021 at 2:21 PM, luckyy said:

    Just thought I'd share my experience setting up a Valheim server with this docker app from @ich777(thank you!)

     

     

    And thanks for the instructions. I've been running this docker with Valheim since Feb 4th, and it's been very stable. Here is my user script to backup World files; I have mine set to run at 03:30 daily. Note that your destination paths will be different, so make sure you update it to match your setup.

    #!/bin/bash
    
    # Create a compressed file archive as a backup for the Valheim server
    
    today=$(date '+%m_%d_%Y__%H_%M_%S')
    backup_path=/mnt/user/CA-backups/valheim_backup
    source_path=/mnt/user/appdata/valheim/.config/.
    backup_file=$backup_path/valheim_$today.7z
    
    7z a -t7z -m0=lzma -mx=9 -mfb=64 -md=32m -ms=off $backup_file $source_path
    # Keep only the 10 newest backups
    ls -t $backup_path/*.7z | awk 'NR>10' | xargs --no-run-if-empty rm -f

     

×
×
  • Create New...