Jump to content

cgrd

Members
  • Posts

    7
  • Joined

  • Last visited

About cgrd

  • Birthday August 1

Converted

  • Gender
    Male

Recent Profile Visitors

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

cgrd's Achievements

Noob

Noob (1/14)

2

Reputation

  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. 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!
  3. 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!
  4. 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
  5. 1. This is working perfectly for me 2. Thank you so much for the work you've put into this container and the support you provide.
  6. Hi. Some linux users have indicated the issue may lie with how Steam handles IPv6 on the linux platform. Disabling IPv6 has resulted in faster download speeds. You can read about it here: https://old.reddit.com/r/linux_gaming/comments/b0jh6g/steam_download_speed_slow/ All the best!
  7. The incredible ease of use, while still being an very complex and in depth tool. Manual XML edits retained when re-editing via the GUI. Thank you, and best of luck everyone.
×
×
  • Create New...