Jump to content

raiditup

Members
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

3 Neutral

About raiditup

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. For those of you using PIA for VPN and have been waiting for the ltConfig plugin to be available for Deluge 2.0, the maintainer has released a forked beta version. You'll need to compile the plugin yourself in Python 3.7 for it to work however. ltConfig Beta Version -> https://github.com/JoshDi/deluge-ltconfig To ensure the plugin was compatible, I actually compiled it directly within the latest binhex-delugevpn container and then copied the resulting .egg to the binhex-delugevpn plugin directory on my unRAID host. After restarting delugevpn, I was then able to enable the plugin and disable/uncheck the following settings. Make sure to also check "Apply settings on startup". enable_incoming_utp enable_outgoing_utp Once these two settings are disabled, my torrent speeds skyrocketed back to where they should be. If anyone needs help with this process or would like me to just post the pre-compiled plugin, let me know.
  2. Yeah webUI worked for me too, but not able to connect directly to the daemon.
  3. Log into the Unraid WebGUI and click on the Docker tab Click on the binhex-delugevpn app and click Edit Change the Repository to binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04 and click Apply. You should then be automatically reverted back to the last version before it switched over to 2.0.3
  4. Has anyone been able to connect to the deluge daemon running on 2.0.3? I've tried with the 1.3 gui & console and the 2.0.3 console and I see libtorrent errors. As soon as I revert back to 1.3, it works again.
  5. I found a workaround for now. If I edit the VM's config in the GUI and switch to XML View, I can change the settings of an existing network interface to point to the bridge I created. <source bridge='br0'/> Change to <source bridge='prv0'/> Still holding out hope that unRAID will make all interfaces visible to the VM's.
  6. Hi, A year ago or so, I created 2 private bridges in libvirt for VM testing purposes. These bridges are persistent and active, but they no longer show up as an option when creating or editing my VM's. I'm wondering what may have changed in the many updates unRAID has gone through since I first created these bridges and how I can make these bridges usable again. I've already run virsh net-list to confirm the default bridge and my 2 private bridges show up as Active and Persistent, but these bridges do not show up in the GUI network or VM settings. Anyone got any ideas?
  7. Yeah I created a .img from the USB. The only difference is I used an Ubuntu machine to create the img with qemu-img instead of plugging in the drive directly to the Unraid server. I then scp'd the img file over to the Unraid server. I followed both the Creating Install Media and the How to High Sierra on Unraid videos by Gridrunner but still ran into the issue of it not seeing the disk.
  8. I'm having the same problem as you. I've tried the latest version of Clover (r4380) and the one suggested in the description of the Creating Install Media guide (r4220) and both times Clover sees no disk.
  9. I found this article on a blog site that explained why this isn't working in the latest version of unRAID http://kicherer.org/joomla/index.php/en/blog/48-automatic-hotplugging-of-usb-devices-for-libvirt-managed-vms It appears that when you run a command fired from a UDEV rule, the rule waits for the command to finish before completing the event such as mounting or attaching a USB device. This is why my attach command kept failing as my USB device wasn't attached when it ran. The clever blogger was able to workaround this issue by using systemd to run his command. Unfortunately, unRAID is based on Slackware which still uses init so I instead wrote 2 scripts for each USB device. One to attach/detach the device and another to call that script. My UDEV rule now fires the 2nd script which calls the real script. The call script looks something like this #!/bin/bash /boot/config/attach-keyboard.sh & disown The key is the call script includes "& disown" which will run the script in the background and disassociate it from the shell. Theoretically I should've just needed the "&" but it still didn't appear to work without the disown. This allows the UDEV rule to not wait for the script to finish running before attaching the USB device. I'm sure there's probably a cleaner way to do all of this, but this is what has been working for me. I'm going to try and write an article on my blog and will post a link when I'm done. In the interim, if anyone needs more info on how to automate USB Hotplugging for VM's, I'll be more than happy to help.
  10. Sorry originally posted this in the general forum thread. Before I updated to the latest build (6.3.2), I had a custom udev rule copied to /etc/udev/rules.d on boot. It allowed me to use a mouse and keyboard hooked up via KVM like USB switch to be shared between my main PC and a VM in unRAID. On the latest build however this doesn't seem to work anymore. I can attach the mouse and keyboard manually when switching between my PC and VM but this is a major hassle. I'm not sure if its an issue with the latest version of libvirt or udev that's causing the problem. If anyone has a custom udev rule working in the latest build and can provide assistance with this it would be much appreciated.
  11. Sorry this was posted in the wrong Forum. Can this be deleted?
  12. Before I updated to the latest build (6.3.2), I had a custom udev rule copied to /etc/udev/rules.d on boot. It allowed me to use a mouse and keyboard hooked up via KVM like USB switch to be shared between my main PC and a VM in unRAID. On the latest build however this doesn't seem to work anymore. I can attach the mouse and keyboard manually when switching between my PC and VM but this is a major hassle. I'm not sure if its an issue with the latest version of libvirt or udev that's causing the problem. If anyone has a custom udev rule working in the latest build and can provide assistance with this it would be much appreciated.
  13. Thanks for the quick turnaround. Sickrage is back to functioning as normal.
  14. I was wondering if the current release is off the latest Sickrage build. I'm getting a timezone error in Sickrage and the Sickrage creator says on his Github page that its fixed in the latest build.