• Content Count

  • Joined

  • Last visited

Community Reputation

15 Good

About carnivorebrah

  • Rank

Recent Profile Visitors

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

  1. The file should be named "default" and located in \appdata\nextcloud\nginx\site-confs
  2. Thank you! All of these steps worked for me to get the "All checks passed" after upgrading to 21.0.1. The only additional thing I had to do was clear my browser cache in order for it to get rid of this error: Your web server is not properly set up to resolve "/.well-known/webfinger".
  3. UPDATE: Still going without issues. Thanks for the help!
  4. Diagnostics attached. I really hope it's not a bad card. I've only had it for 2 months. It worked fine up until last weekend, but I guess it could happen. I'm 99.99% sure I updated both the BIOS and BMC/IPMI firmware when I built the server. I will have to check the BIOS on the next reboot though, if it locks up again. I have a feeling (mainly hope) pulling the GT710, and running the Unraid video out through the P2200 fixed it though. I'm running a Supermicro X9DRL-iF, which only has an open-ended 8x PCI-
  5. Oh, wow. That just goes to show how much of a newb I am. lol I had no idea I could run the video for Unraid on the same GPU as my transcoding GPU. GT710 has been removed. Unraid video out and Plex transcoding confirmed working on just the P2200. Will report back in a few days if it hasn't happened by then.
  6. Has anyone here experienced this error happening? I am on 6.9.1 and using the latest nvidia driver (v460.67). I am running a Quadro P2200 for Plex transcoding and a GT710 for Unraid video out. I've had this error appear 4 times since Sunday, and it completely locks up the server, requiring a hard reset and parity check. The line in particular that makes me think it's related to the driver is this one, right after the end trace (maybe I'm wrong... idk): RIP: 0010:_nv036095rm+0x4/0x70 [nvidia] I also want to say that it seems like it started after I updated
  7. Well, that didn't last long. Any idea why the latest update no longer works with Swag? I can get to the web UI using the local IP/port, but my proxy-conf file, which was working before the update, is no longer working. It's only this one. All other domains/subdomains proxy-confs are still working. The container is running on "custom: br0" w/ ip address and listening on port 80. EDIT: Figured it out. I had to switch it to my custom "proxynet", add a port mapping (8084 host to 80 container) and then update the proxy-conf to the below (my unraid serv
  8. Should I be able to change the tab/favorite icon by putting an icon file named favicon.ico in the directory /config/img/icons/ ? I was able to get the logo to change by placing a logo.svg file in /config/img/, restarting the docker and clearing my browser cache. I just can't seem to get the tab/favorite icon to show up. I also tried just placing the favicon.ico file in the /config/img/ directory with the logo.svg file, but still got the same results. EDIT: I got it working. I missed the browserconfig.xml file. I created it and the PNG file that t
  9. Has anyone been able to get 2 separate domain names (i.e. & working through Cloudflare and SWAG? I was able to get my first domain all setup and working. I can access all the subdomains just fine. I then added a new site to Cloudflare, and verified the DNS setup is working and pointing to my public IP like my first domain. I can see communication is occurring through Cloudflare. I then added this domain to the "Extra Domains" parameter in the SWAG docker container. Restarted, and everything generated fine. It recognized t
  10. Is anyone else having issues getting Overseer to connect with Sonarr recently? I don't get as much use out of Overseerr as I would like. So, I haven't noticed it until today, as I was having issues with the recent update to DelugeVPN, and I decided to go through and check to make sure all is well with the rest of my dockers. When I try to connect to Sonarr in Overserr, it just says it can't connect. However, I can connect to Radarr (same IP/port 7878) just fine. I thought it may have been because I enabled the login page, but I disabled it, restarted and it didn't work.
  11. Okay, looks like adding my network "10.100.1.*" to "Ignored Addresses" in both Sonarr and Radarr fixed the connections issues between them, Jackett and DelugeVPN. It looks like just checking the box "Bypass Proxy for Local Addresses" will not work on its own. Thank you so much. This is also true for any physical devices I use, aka laptop, desktop, mobile device: You have to specify the IP addresses or entire subnet that you want to bypass the proxy for. Checking the box alone doesn't work. All issues resolved! Thank you!!!
  12. I think I am using privoxy running in delugevpn, because I'm not routing the containers using '--net=container:<name of vpn container>'. I think? I honestly don't know if I'm answering your question correctly though. Anytime I want to "point" or "route" something through DelugeVPN, I enter the IP and port 8118 on that physical device's or the docker container web UI's proxy settings. At least, that is how I've always done it.
  13. Well, I didn't add '--net=container:<name of vpn container>' to my containers. I missed that, but I see a reply stating that is not needed if you set the "localhost" IP in the web GUI of the container instead. So, I'm not sure what's going on. The part that is really killing me, is the physical device pointed through the proxy IP/port part. If I do that, I cannot access the Unraid web GUI, nor any of my dockers running in bridge or custom IP on that device. I can only access dockers running on my "proxynet" VLAN using the fully qualified public domain name, which is going out
  14. I posted screenshots of my setup a few posts up. Please let me know if you need more screenshots 1. Yes, I am routing Radarr, Sonarr and Jackett through DelugeVPN using the web GUI settings for each docker to point to the deluge container IP/port ( I tried using "localhost" too, but it wouldn't connect. 2. Yes, my unraid server IP is, and my LAN_NETWORK is defined as 3. Yes, I have a couple containers set with static IPs (pihole and guacamole) that I can no longer access when I point a physical device to the deluge proxy. C