• Posts

  • Joined

  • Last visited

Everything posted by 2twisty

  1. Back from the dead. Does this docker (or the script mentioned) work on 6.8.3? With the docker, I am getting the 1kb file with a zero-byte sql dump file inside. With the script, it fails to run,giving me "mysqldump: errno 11 on write" when it executes the docker command
  2. I just looked in that directory, and yes, all my templates are gone. I guess the next question is can they be recreated easily? I wonder what deleted them since I didn't make any changes to the flash aside from the upgrade to 6.8..?
  3. Reboots do not fix it, and I did nothing to the flash drive -- I just pressed the "update" button to go from 6.7 to 6.8, and now my dockers have no templates. Fix Common Problems offers to apply a fix, but just gives me a "no template" error. Here's diagnostics as of a few moments ago. rrl-nas-diagnostics-20191226-2202.zip
  4. After upgrading to 6.8, most of my dockers are still working (some aren't), but all the templates are gone. I can't update them. I just get a message asking if this docker was created with this plugin. They all were and worked fine in 6.7.x. I don't want to have to recreate all my dockers just to fix this. Is there a way to sideload the templates back in so that everything is working properly again?
  5. That might work, but it would completely destroy the ability to hotplug/easily remove the device. If I am stuck with that arrangement, I might as well shuck the drive and install it into the server. It's a backup drive, so I'd like the ability to remove it from the system. I use rSync to copy the files, so I am considering taking the drive off-site (eventually) and use remote rSync. I guess I'll take another stab at passing the entire USB controller through to the VM. I'd imagine that would be more stable -- only when I tried it, it caused my unraid server not to boot. I am 95% sure that the flash was NOT connected to that controller at the time, but have since moved it to the external USB3 ports on the motherboard (rather than using the internal USB3 header on the motherboard) so I am now 100% certain that the flash isn't on the USB3 add-in card. So I will try again and see if I can make that work.
  6. HMMMM. I read a post about USB hard disks not being detected, and the solution the OP found was that his USB cable was somehow bad. I tried that. It didn't show up in the VM. So then, I powered it off and restarted. It appeared! So, I tried a reboot of the VM. It's still there as of now. So...bad cable? I was a cheap Chinese enclosure, so who knows. Hopefully this problem is resolved, but if it recurs, I'll come back here and update with any other things I try/find.
  7. Here's some more info that I just noticed. It seems that the VM "sees" the external USB drive enclosure, but then does nothing with it. webadmin@panel:~$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub webadmin@panel:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sr0 11:0 1 667M 0 rom vda 253:0 0 60G 0 disk ├─vda1 253:1 0 512M 0 part /boot/efi ├─vda2 253:2 0 55.5G 0 part / └─vda3 253:3 0 4G 0 part [SWAP] vdb 253:16 0 200G 0 disk └─vdb1 253:17 0 200G 0 part /var/customers So maybe this isn't a KVM/unraid issue, but an Ubuntu 16.04 issue. I'll keep digging, but any ideas are appreciated.
  8. I've got a Linux VM that I want to pass a USB hard disk through. The box is checked in the VM config to pass it through, and most of the time it doesn't appear in the lsblk output of the VM. At one point yesterday, it magically showed up and I have no idea what I did to make that happen. Subsequent reboots of the VM failed to attach the drive. I tried passing my whole USB controller (separate PCIe device) through, making sure that my flash drive was on a different controller, using the vfio-pci.ids= command in the boot config. After that, UNRaid would not boot. I had to manually edit the files on my flash to remove the vfio directive and then unraid came right back up. I've searched the forum for this particular issue and haven't found an answer that seems to apply or works. What information can I provide to allow you to help me resolve this? I don't really need/want to pass the entire controller through, since the VM is a server, and I don't need to pass any other USB devices to it (I use SSH or the RealVNC if I need to). Please advise.
  9. IIIIIIInteresstingggg.. I noticed in the log that it complained that the VPN endpoint I had chosen did not support port forwarding. It still connected but just issued a warning about download speeds. So, I tried changing it to one of the ones listed in the log that DO support it, and POOF. Container starts with VPN and WebGUI comes up. So, I guess using an endpoint that supports port forwarding needs to be listed as a requirement rather than just a warning? NOTE: Previously I had tried other end points with the same failure result, but none of them were on the list of port forwarding endpoints either.
  10. Well, turning the VPN off sure simplified that log! Basicially, it says "OK listening on port 8080 now." supervisord.log
  11. ok. Here's supervisord.log. I looked through it and it looks like this may be something to do with it, since goes through all 12 retries several times in the log and never has success. I'll try grabbing a log with the VPN turned off to see if there is an obvious change in the logs, but I admit that log chasing isn't my strongest suit. 2019-09-15 12:50:47,822 DEBG 'start-script' stdout output: [warn] Response code 000 from curl != 2xx [warn] Exit code 7 from curl != 0 [info] 12 retries left [info] Retrying in 10 secs... supervisord.log
  12. Anybody have any suggestions for me on this? I REALLY need to get the VPN going since I am on Spectrum and don't want to get any nastygrams.
  13. There are some great tutorials on YouTube by SpaceInvader1, that will help you understand in general hoiw to set up docker and UnRAID. You definitely dont want your data going in the /config folder. Check his stuff out. It helped me a lot when I was new to UnRAID.
  14. Additional note: tried rebooting server, as well to clean out RAM and any stuck ports, etc. No dice. Same behavior.
  15. SYNOPSIS: Web GUI won't load when VPN enabled I've read through this entire thread, and some have had a similar problem, but not exactly. I have installed this container with all the defaults and put the certs and ovpn file in the openvpn folder. I know my PIA account is working since I can log into the web site and also connect via the Windows client. There are no other containers using any of the ports that qbittorrentvpn is using. When I have the VPN enabled in the container, the container will start, but the web GUI refuses to connect. If I disable the VPN, Web GUI works fine. Uninstalled and reinstalled and even removed the folder from appdata to be sure there were no leftovers. When I uninstalled, I deleted the image. NOTE: I still have binhex-deluge installed, but it doesn't share any ports. I am transitioning to a VPN downloader which is why i chose the qbittorrent one so that I could use my non-VPN deluge client concurrently until its downloads complete. What information can I provide to help troubleshoot this?
  16. OK, apparently, Radarr can still add items to Deluge, but the "connection test" fails. Honestly, at that point, it doesn't matter now that I have a Deluge 2.0 client (I run Linux Mint so I don't have the "windows" problem that others do. I'll go back to the other threads and edit them.
  17. After a recent update to Deluge v2 (my binhex-deluge container auto updated), neither binhex-radarr nor binhex-sonarr can connect to it. When I test the connection, I get "authentication error" and I have changed no passwords. What additional information can I provide to allow you to help me with this? Right now, I can't add any new torrents to Deluge. Unraid 6.6.7. (crossposted in binhex-radarr and binhex-deluge support threads)
  18. EDIT: Found help with the Radarr/Sonarr issues here: Binhex-Sonarr support thread After a recent update to Deluge v2 (my binhex-deluge container auto updated), neither binhex-radarr nor binhex-sonarr can connect to it. When I test the connection, I get "authentication error" and I have changed no passwords. What additional information can I provide to allow you to help me with this? Right now, I can't add any new torrents to Deluge. Unraid 6.6.7.
  19. EDIT: Found help with the Radarr/Sonarr issues listed below here: Binhex-Sonarr Support Thread Looks like Deluge did get upgraded to v2. After upgrading the thin client, I can now connect, but I still can't get Radarr and Sonarr to talk to it. I am using the binhex versions of both radarr and sonarr. They don't report that any updates are available. Any idea where to go with this next? I'll check the support threads for those containers, as well.
  20. Just today, my remote Deluge client started to refuse to connect to my docker. The Auth file still has the proper passwords in it. I checked Radarr and Sonarr and they too can no longer connect. When I test the connection in Radarr/Sonarr, I get "authentication failed." I am able to see my active torrents via the web interface from UnRAID, so I know that the daemon is still running and operating, and that the password is still recognized. Thinking that some config got corrupted, I stopped the container, renamed the config directory and removed the container, deleting the image. I downloaded a fresh copy. I changed no settings in the docker setup except the location of the /data directory, and made no config changes in either the web interface or via the terminal. So, this container is totally default. I still have the same problem. Neither my Deluge client nor Radarr/Sonarr can connect using the default "deluge" password. Same "authentication error." Have there been any recent changes to the container that might explain this? My torrents are crippled right now until I can get this working. What additional information do you need to allow you to help me figure this out? Still on UnRAID 6.6.7
  21. TOPIC: Running this docker on a static IP and changing the listen address to port 80. I would like to be able to use DNS to resolve my dockers on separate IPs. So instead of http://rrl-nas.contoso.com:7878/ for radarr, I'd like a clean URL of http://radarr.contoso.com/ I thought I had this figured out when playing with OwnCloud, but I don't have the whole picture. Nothing I try seems to move the listen port from 7878 to 80. I tried settings in the UnRAID Docker UI as well as googling and trying to directly modify the config.v2.json file to change the exported port from 7878 to 80. Nothing works. What am I doing wrong?
  22. OK. I decided to experiment and changed it to PORT:80, and it fixed the problem. Since I've had similar problems with containers in the past, I guess this is a common problem. I've been trying to get separate IPs working for a long time, but only just now noticed the mapping issue. Thanks for the info, and hopefully this post will help someone else.
  23. That doesn't really answer my question. If I change the WebUI entry, will that fix the UI problem I described? If so, why doesn't it update that automatically when I change the port settings in Basic View?
  24. It says: http://[IP]:[PORT:8000]/ So, I assume that I should change this to say: http://[IP]:[PORT:80]/ Still curious that it didn't update it on its own.