DarkHorse

Members
  • Content Count

    59
  • Joined

  • Last visited

Community Reputation

5 Neutral

About DarkHorse

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Hmm... downloaded a new OpenVPN config definition from my VPN provider and all is now good. Not sure why that would affect me connecting to the docker instance locally.
  2. Anyone else seeing TLS handshake failures? I see the following in my log every minute or so, and can no longer connect to the WebGUI. I recently updated my docker containers, and I believe it was working fine before the last update. Could it be related to the ciphers warnings? 2021-01-21 09:22:33,410 DEBG 'start-script' stdout output: 2021-01-21 09:22:33 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) 2021-01-21 09:22:33 TLS Error: TLS handshake failed 2021-01-21 09:22:33,410 DEBG 'start-script' stdout output: 2021-01-21 09:22
  3. I looked up my installation notes... not sure if this is helpful, but these are the steps I used to get netbox up and running: First install Postgres11 docker container, enter POSTGRES_PASSWORD, keep other default values Console in to postgres container su postgres psql CREATE DATABASE netbox; \l to verify it was created GRANT ALL PRIVILEGES ON DATABASE netbox TO postgres; \l to verify permissions \q and exit console. Next install Redis container, keep default values. Next i
  4. For me, I found that my netbox configuration.py file was not being properly updated with the variables passed. To take a look, console in to your netbox container, and view /app/netbox/netbox/netbox/configuration.py. I simply edited that file directly, saved, and then restarted the docker container.
  5. Thinking this docker container might work with UnRAID? https://hub.docker.com/r/bubuntux/nordvpn/
  6. Found this guide link... gonna start with this....
  7. I just subscribed to NordVPN because of their support for Wireguard... I too would like to know a bit more... thanks!
  8. A short follow up: so, after making sure I had things backed up, I stopped the arrary. Previously, this would just hang trying to unshare folders. This time, however, the array stopped. I then reassigned my drive back into the array, and it rebuilt the drive from parity. Everything appears to be fine now.
  9. So, the drive has been unassigned, is being emulated, and a parity-check is currently in progress, 3 hrs to go. I'm still able to access my shares and data. To the best of my memory, here is exactly what I did: 1. stopped the array 2. unassigned the drive 3. started the array. The system immediately began doing a parity check upon starting the array 4. I used the GUI button to "Cancel" the parity check. Without canceling, the "Stop" array button was not active. 5. After canceling the parity check, I was then able to click the "Stop" button to st
  10. This technique discussed here is no longer valid in UnRAID 6.7? Stop the array Set the disk to be not installed Start the array Stop the array Set the disk to be the appropriate disk Start the array
  11. So, I've had a red x on a drive before, while running with dual parity drives. Usually just a cabling issue... wiggle the SATA cables and back in business. I would simply stop the array, unassign the drive, start the array, stop again, and reassign, and then start. However, is doing this with 6.7 different now? I stopped the array, unassigned the drive, and started the array again. Now it is rebuilding the parity which will take serveral days. So I now need to wait to add back in the drive? I don't recall older versions of UnRAID doing this. Before, I w
  12. sorry, no... haven't looked into it any further.
  13. Well, after reading this thread... I knew I had a Marvell controller on my board, but couldn't recall if any of my drives were using it. So I did ls -al /sys/block/sd* lrwxrwxrwx 1 root root 0 May 21 12:17 /sys/block/sda -> ../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/host0/target0:0:0/0:0:0:0/block/sda/ lrwxrwxrwx 1 root root 0 May 21 12:17 /sys/block/sdb -> ../devices/pci0000:00/0000:00:1f.2/ata1/host1/target1:0:0/1:0:0:0/block/sdb/ lrwxrwxrwx 1 root root 0 May 21 12:17 /sys/block/sdc -> ../devices/pci0000:00/0000:00:1f.2/ata2/host2/target2:0:0/2:0:0:0
  14. bastl's solution described above solved my audio issue... thanks.
  15. What's the best way to have a common VM disk image that I can use to sometimes have GPU passthrough, and then sometimes have it run without GPU? Is the best / only way to edit the VM XML definition every time? Or can I setup two XML definitions (with GPU / without GPU) that share a common vm disk image? Curious how / if others are doing this. thanks!