Jump to content

jserio

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

2 Neutral

About jserio

  • Rank
    Member
  • Birthday 12/04/1972

Converted

  • Gender
    Male
  1. Same issue. Pi-Hole is using a custom IP on br0. I can access any other device on my network except the Pi-Hole IP.
  2. Hey guys. I have an issue accessing the Pi-Hole docker from outside my network over Wireguard. I believe this is a known issue but I can't seem to find a definitive answer. My Unraid server is 192.168.1.110 Pi-Hole is using custom br0 192.168.1.111 No other dockers use a custom br0. When outside my network using Wireguard, I can access Unraid and all other dockers, in addition to all other devices on my LAN (router, Windows clients, etc). However, I am unable to access Pi-Hole. Can someone confirm if this is a known issue and if it will be fixed in a future release?
  3. Interestingly, I went to the airvpn page to choose a few different servers and noticed this on the page (never saw it before): I suspect when the issue arises, that deluge is caching the original IP and not resolving to a new one? Any way to force a flush of the dns cache?
  4. Thanks @binhex for the reply. The ovpn files does indeed use the hostname (remote us.vpn.airdns.org 443). When the issue reoccurs I'll post the logs here.
  5. Hey guys. I've used AirVPN for years now but it seems that every few weeks DelugeVPN will go into a disconnect/reconnect loop every 2-3 minutes. I believe it's due to the particular server going down or having issues. Usually, when this happens I just download a new config file from AirVPN and copy it to the Deluge openvpn directory, restart the docker and all is well for a few weeks. Is it possible to copy several openvpn config files to this directory and have Deluge rotate through them if it disconnects from a server?
  6. @binhex, any chance you can update this container? The latest release is 4.1.1. Thanks!
  7. Thanks for the quick reply. I tried searching prior to posting but didn't see that particular thread. Good to know I'm not the only one with the problem. For now, I've disabled attribute 197.
  8. Using Unraid 6.7.2. Hey guys, I picked up two new Crucial MX500 (2TB) ssd drives on Amazon Prime Day. one to replace my cache and the other to replace my unassigned Download drive. After installing them (prior to formatting) I saw the following "Warnings" in my dash - one for each drive: Current pending sector count 1 (sdm) I ran an extended SMART test which resulted in no errors. However, the SMART error log shows the following (for both drives): Warning: ATA error count 0 inconsistent with error log pointer 4 ATA Error Count: 0 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error -3 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 00 ec 00 00 00 00 00 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ec 00 00 00 00 00 00 00 00:00:00.000 IDENTIFY DEVICE ec 00 00 00 00 00 00 00 00:00:00.000 IDENTIFY DEVICE ec 00 00 00 00 00 00 00 00:00:00.000 IDENTIFY DEVICE ec 00 00 00 00 00 00 00 00:00:00.000 IDENTIFY DEVICE c8 00 00 00 00 00 00 00 00:00:00.000 READ DMA I've acknowledged the warning, but it seems to return every few days. I suspect it's just Unraid referring to the last error log (which happens to be the one above, and seems to have occurred at first power up). I don't believe both drives are bad... I suspect perhaps this is a general error upon a new drive install? Is there any way to clear the most recent SMART error log? Or perhaps any way to deal with this so it does not keep popping up in the dashboard?
  9. I removed then re-added CA and all works fine now. Thanks again for checking, and thanks for the great plugins!
  10. It's on the main Apps page. I opened up Chrome's dev tools and see this in the console (hope this helps). The error comes after I type in "beet" (no pressing Enter).
  11. Forgive my ignorance but I haven't used the beet command this way. I open the beet console and then within the container I run beet import.... Is this not the correct way? If I run the command outside of the container, then the permissions will be correct? I do know that the user inside the container appears to be 'abc'.
  12. Hey guys. I've used both this docker and thetarkus version and they both exhibit this problem. When importing new files, when beets moves/copies them to the destination, the file ownership is root.root - even though the docker settings for UID/GID is 99/100. This requires me to chown/chmod after each import in able to edit the files later on. Short of writing a cron job, is there a way to fix this? Or does beets support a post-processing script (I couldn't find anything in their docs) that can call external commands? Any help would be appreciated.
  13. Hey guys. A quick search didn't yield anything. Has anyone noticed in the last few versions of CA, that the auto-complete in the search box no longer works? I've disabled all ad-blockers and browser plugins. Tried in both Chrome and Firefox and nothing. The changelog makes note of a few autocomplete changed but nothing about it being removed. Is this a widespread issue or just me?
  14. Has anyone gotten the Last.fm integration working? I created an API key and set the variables (https://koel.phanan.net/docs/#/3rd-party) however the Koel profile page still says: Last.fm Integration This installation of Koel has no Last.fm integration. Visit Koel’s Wiki for a quick how-to. Any ideas?
  15. Running Unraid 6.6.3. I have my VM (Windows 10) set up with GPU and USB card passthrough. Also, the OS is running on a SATA controller which is also passed through. Everything works beautiful. Except when I enable File Integrity Control (in Settings). I get terrible mouse lag/stutter every few seconds. I tried with both SHA2 and Blake2 and the problem persists. Anyone else have this problem? Any ideas?