manderso

Random question, and I don't think it's been asked yet. I'm monitoring qBittorrent/data/logs/qbittorrent.log from a splunk universal forwarder container. The log is getting saved as 600, so the splunk user from the other container cannot read it. How would I go about changing the permissions for that file (without having to do it manually) to be readable to others? Thank you

Yep. Thought I had copied over the new file, guess I didn't. Sorry to bother you. Thanks for the help.

I'm still getting "the remote line is referencing PIA legacy network which is now shutdown" error, even though I've downloaded the newest openvpn.zip file from PIA, and am using the latest (and tried the test) branch of binhex-delugevpn. I've also tried another ovpn file (usually using CA\ Montreal.ovpn, tried CA\ Toronto.ovpn), and get the same error. What am I doing wrong? 2020-12-17 11:34:30.164925 [info] PUID defined as '99' 2020-12-17 11:34:30.189888 [info] PGID defined as '100' 2020-12-17 11:34:30.871321 [info] UMASK defined as '000' 2020-12-17 11:34:30.894360 [info] Permissions already set for volume mappings 2020-12-17 11:34:30.918113 [info] Deleting files in /tmp (non recursive)... 2020-12-17 11:34:30.945285 [info] VPN_ENABLED defined as 'yes' 2020-12-17 11:34:30.969321 [warn] VPN_CLIENT not defined (via -e VPN_CLIENT), defaulting to 'openvpn' 2020-12-17 11:34:30.992415 [info] VPN_PROV defined as 'pia' 2020-12-17 11:34:31.608775 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/CA Toronto.ovpn 2020-12-17 11:34:31.646677 [crit] VPN configuration file '/config/openvpn/CA Toronto.ovpn' 'remote' line is referencing PIA legacy network which is now shutdown, see Q19. from the following link on how to switch to PIA 'next-gen':- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md exiting script... client dev tun proto udp remote ca-montreal.privateinternetaccess.com 1198 resolv-retry infinite nobind persist-key persist-tun cipher aes-128-cbc auth sha1 tls-client remote-cert-tls server auth-user-pass compress verb 1 reneg-sec 0 <crl-verify> -----BEGIN X509 CRL----- ... -----END X509 CRL----- </crl-verify> <ca> -----BEGIN CERTIFICATE----- ... -----END CERTIFICATE----- </ca> manderso@Tower:/mnt/user/appdata/binhex-delugevpn$ ls -al openvpn/ total 16 drwxrwxr-x 1 nobody users 124 Dec 17 11:34 ./ drwxrwxr-x 1 nobody users 486 Nov 8 14:40 ../ -rwxrwxr-x 1 nobody users 3180 Dec 17 11:34 CA\ Toronto.ovpn* -rwxrwxr-x 1 nobody users 2025 Dec 17 11:03 ca.rsa.2048.crt* -rwxrwxr-x 1 nobody users 20 Nov 11 08:26 credentials.conf* -rwxrwxr-x 1 nobody users 869 Dec 17 11:03 crl.rsa.2048.pem* Thanks for your help.

And I moved cables around and we're healthy again. Thanks for the reply.

Drive isn't seen in the bios because it's hooked directly to the sata card, not the mobo. Its a newer ssd, I have no idea if there's a pin that needs to be blocked.

Purchased a SATA card (SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 11)) and ssd, plugged cable into card and hd, and power in to drive. The SATA card is seen in the GUI as well as lspci, however neither mount nor fdisk -l will see the new drive. Can someone please help me resolve this? tower-diagnostics-20200531-1434.zip

Are you saying you were able to get your fusionio drive working in unraid using the steps above? Are you using it as a cache drive, and is it working as expected? Thanks

And I'm silly. I've got the Splunk docker image running on the unraid server. I opened up the /mnt/user/appdata directory as a mount in the container, and find the logs of each container's local data in the mount.

Have you found something for this? I'm in the process of installing the splunk universal forwarder on the unraid box, but not having an init.d or systemctl process is pretty limiting. I get the docker startup/error logs already, but I'd like the logs from the containers as well.

Finally figured this out by looking in the letsencrypt.log file in /config. Was seeing this: and i'm not sure how I solved it, but that the account in the mentioned directory was not there. I originally had 2 sub domains set to get a cert, and stopped using one of them and deleted it in the settings, then hit apply, which brought the image down again and for some reason, added a new account to the directory. Letsencrypt saw it and allowed the cert to renew.

Thanks for the help. I'll be on the lookout.

Can you recommend an inexpensive 4 port card, or point to someone who can? I can't tell how up to date this is: https://wiki.unraid.net/Hardware_Compatibility#PCI_IDE_Controllers

I'm seeing these events in my log at least once per minute: I think it's about my sli raid card, which has been fine for some time, but no longer. I'm attaching my diagnostics log. Is there something I can do here? Looks like there's going to be a problem w/ my drive connected to the raid card in the future, so any help here would be great. Thanks tower-diagnostics-20200131-1222.zip I was getting the above error, though it was talking about my sata raid card. I attempted to clear it up by disabling iommu in syslinux.cfg, but the drives didn't show after a reboot. Same thing happened when I disabled the virtual settings in my bios. So, I disconnected the storage disks from the sata raid card, and connected them to the onboard sata connections. I also connected my cache drive to the sata raid card (as I'm out of sata ports on the mobo). I'm now getting Unmountable: Unsupported partition layout as the file system status on the cache drive, so that's not great. I don't mind wiping the cache drive if need be. Can anyone help w/ all this mess? Thanks

Looking at page information, on the security tab in firefox, for my nextcloud page, I see Verified by: Let's Encrypt, Expires on: December 28, 2019.

That came from nextcloud that said my cert had expired. And I haven't changed any settings, including networking. I had followed spaceinvaders guide for setting up nextcloud behind a letsencrypt cert, and that's using a proxynet network I setup for this purpose.