BurntOC

Members
  • Content Count

    72
  • Joined

  • Last visited

Community Reputation

1 Neutral

About BurntOC

  • Rank
    Newbie

Recent Profile Visitors

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

  1. As I posted this on a long holiday weekend and hadn't seen responses in about a week, I thought I'd try bumping it once to see if anybody has any ideas. Sent from my GM1917 using Tapatalk
  2. So I've spent probably 2-3 hours searching, looking through posts, and double-checking my container paths. While I do have 21 containers currently, I keep hearing that's fairly normal and 15GB-20GB should work for most people. I got notifications it was filling up in the past so I'd upped the size to 30GB, but a couple of days ago while on a trip I got notice it was almost full again. I'm at 40GB but it sounds like this should be unnecessary. I'm hoping one of the experts here can spot something I'm obviously missing. I've attached a diagnostics.zip. Most things have been r
  3. Very much appreciated. Sent from my GM1915 using Tapatalk
  4. Thank you,@doron. This may be the path I take. Sent from my GM1915 using Tapatalk
  5. So I've had a great experience with Unraid as my core system running Windows as a VM for some of my gaming, but with some of these games blocking running on VM I'm considering running Windows 10 with ESXi and virtualizing Unraid. My system has an AMD Ryzen 5900x and a X570 motherboard, with a 3060 Ti GPU passed through to the VM and a 1660 being used - maybe unnecessarily - for things in Unraid like Plex transcoding. Most of the time my CPU load with the one VM and about 20 containers is in the 4-11% range (when not gaming). I use the X570 SATA connectors for all my array drives, parity
  6. Thank you very much, @IFireflyl. This is exactly what I needed to know.
  7. So I read the OP and several pages of this thread, including the latest posts but I don't see any posts speaking to an issue of concern for me. I don't have my server accessible except via VPN tunnel and that's how I like it. As with my Unifi gear, I don't want to enable remote access because I don't trust that a compromise on the vendor side won't facilitate access to my equipment. Am I correct in understanding that you don't have to enable remote access mode? If so, and if online flash backup is stil supported in that scenario, I take it there isn't any major security risk in what's on
  8. I tried following the steps posted elsewhere to rename the repository and use the fix plugin to fix the XML file. I can no longer access my container login page via https. If I try via http I get the error page someone posted about it only being accessible via https, even though I have a trusted cert available. It just isn't listening yet. If I go to the /admin URL then I get the same thing you're showing here, and I have no idea where to get that authentication key from. Any help would be appreciated. This was working just fine until I tried to "fix" it to the new repositor
  9. Code Thank you for the prompt reply, and please excuse my delayed follow up. I guess it doesn't auto-follow topics I create so I just saw your message. I'll dive into that to take a look. I didn't see the part in my diags with a macvlan msg, but I must've missed it.
  10. Running the latest version of Unraid on a pretty new 5900x x570 build. Per the title, the system becomes unstable after a while. This has been going on for some time. I usually realize it when I'm trying to access one of my containerized apps from another computer and it doesn't respond. When I go to Unraid it the dashboard will usually eventually come up after a much longer than usual period of time, but none of my containers show on the Dashboard and the Docker tab is missing. I can SSH in, but attempting to restart or shutdown via the console, dashboard, or SSH commands never gets it do
  11. I've read through the Video Guide post on this, but I know that the method changed a bit in 6.9 vs S1's video and I'm going to be using the rebuild-dndc container as well (though that's immaterial to my core question here, but it might help someone in the thread piggyback in the future), so I thought I'd create a new post. I've tryinging to route some -arrr and sabnzbd containers through a VPN container and I think I only have one question left. FWIW, while I'm a huge fan of binhex I'm testing with hotio's qbittorrent-vpn container because it doesn't require privileged mode for wir
  12. Is this not a security concern? Nothing to be concerned about?
  13. NOTE: I posted this in the binhex-qbittorrent thread as well. This one gets more traffic but if I get to an answer in either I'll post the update in both for others who may run across the issue in the future. I finally had the chance to set this and the binhex-qbittorent containers for evaluation as they're the last major containers I wanted I'd not gotten around to yet. Most everything looks good, but whenever I launch either container I get this in the logs: Warning: `/config/wireguard/wg0.conf' is world accessible I've seen some people include that in the
  14. I finally had the chance to set this and the binhex-delugevpn containers for evaluation as they're the last major containers I wanted I'd not gotten around to yet. Most everything looks good, but whenever I launch either container I get this in the logs: Warning: `/config/wireguard/wg0.conf' is world accessible I've seen some people include that in their log captures here, but I've not found the resolution. I thought that deleting perms.txt and restarting the containers would address, but the behavior is the same. Whether I delete perms.txt or leave it as be, it changes
  15. I couldn't leave well enough alone and I tried to install VM Backup from CA over the version I'd installed per my posts a few days ago. It failed, as the poster above indicated, with various issues from the one he/she described to a md5 check on a file it pulled. AND, I started seeing the problem you're desribing above. Unfortunately, if I delete the plugin out of /config/plugins it still won't let me go back to my previous version either. I'm going to try to delete the vmbackup folder out of plugins and just leave it be until @JTok has some time to put that new version out. Too many hicc