Transition Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About humancaviar

  • Rank

Recent Profile Visitors

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

  1. @elmuziko No worries, gotta start somewhere! Obviously, all actions are done at your own risk, but this should work unless you stuff something up. What I'd recommend for you is to save the raw script within a text file on one of your shared folders as something like #SSH into your server #Change directory to where you saved that script: cd /volume1/SharedFolder/ #Confirm you're where the script is: ls -la *.sh #Should spit out a line with #Make it executable and fix any potential permissions issues
  2. So... Funny thing happened. Reverted my original attempts to load updated crt/pem's and then ran @haydibe's script: Think I missed something in my original attempt. Restarted Sabnzbd and was able to connect to my news provider without issue. Just checked package center, and wouldn't you believe it, there was an updated VPN Server application who's changelog listed chain of trust fixes. Only thing remaining, for me at least, is package center can't connect to SynoCommunity... Not the end of the world, but a bit of a bummer that I wont get updates. Forgot to m
  3. I'm thinking that installing Entware and attempting an openssl update to 1.1.1? Anyone have experience trying this?
  4. Havnt had the time to mess with this further. It seems as though the CA/Chain needs to be updated somewhere I'm not aware of at the moment, or I've missed something? Needs stating, I'm no expert only an enthusiast, hoping someone with more experience will come along and finish the job
  5. Thanks @haydibe, lot of good information. In my case, chain appears broken for: Sabnzbd (native app, not docker) connecting to letsencrypt signed servers. Synology VPN server app (I use LetsEncrypt for signing that and DSM, et. al). I'm wondering if those apps are using sandboxed openssl libraries. Going to keep digging with some of the new stuff I gleaned from your posts. Not in a good position to upgrade DSM, running a 24 drive bare metal rig which usually has issues updating.
  6. That tutorial was to update the certificate signing module to support some new methodologies implemented by LetsEncrypt, that wont help us in this case. Only useful for fixing the "request new certificate from LetsEncrypt"... I may try this separately as I'm having to request with, but wont help our issue in this thread. I've tried a bunch of things, adding the new X3 certificate and ISRG root to /usr/share/ca-certificates/mozilla/ Added those same certificates in pem format to /etc/ssl/certs and hashed them Modified /etc/ca-certificates.conf to include the newly
  7. I ended up saying F-it, zeroing the disks and going to restore backup. After doing some research, it seems that old RAID data on previously used disks can cause issues like this. Fully zeroing should prevent it from happening in the future.
  8. Hello, was wondering if anyone had any experience recovering a volume crash after healthy disks are randomly dropped from SHR volume. After system partition issues and a reboot, two healthy disks were dropped from my volume rendering it useless. I have confirmed that all of the raid partitions for the volume are still on those disks. They appear as initialized disks in the storage manager. I have backups but there was interim data that I would love to recover. Manually adding the disks back into the raid with mdadm is not an option because... mdadm --examine /dev/sdg mdadm: No md sup
  9. Hi guys, I have been messing around with an old Lenovo x220 laptop with the intent of making a stable, low power, XPEnology NAS and seemed to have cracked it. I wanted to share my experience as it may help others looking to create a similar setup. This guide assumes that you've signed up for a free copy of ESXi. Note1: The general format and some processes taken from LeeBear's [GUIDE] Nanoboot ESXi 5.5.0 Perfect Install because it's so damn good. Note2: Following the instructions below constitutes an acceptance of the risk of data loss; I cannot be held responsible for any data o