Jump to content

jserio

Members
  • Content Count

    26
  • Joined

  • Last visited

Community Reputation

2 Neutral

About jserio

  • Rank
    Member
  • Birthday 12/04/1972

Converted

  • Gender
    Male

Recent Profile Visitors

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

  1. To answer my own question, it looks like it has something to do with "Use rich workplaces." Disabling this removes the icon.
  2. I've been on v16 for some time and finally went through the multiple upgrade process to get to 18. Everything went well but my homepage shows what appears to be a spinning icon (as if it's scanning for something). The icon never goes away. Restarting the container doesn't help. This is on Firefox. Only add-on is UBlock Origin which is disabled for my Nextcloud host. Any ideas?
  3. Hey guys. The latest Deemix docker seems to be broken. I noticed the port in the config still says 9666 but the documentation mentions 6595. Regardless of what I put in the configuration, I am unable to connect. Removing and adding the container doesn't seem to fix it.
  4. Works great now. Thanks for the quick response.
  5. Same here. AirVPN. Tried several new config files and get the "unable to resolve Google DNS error." Rolled back to 4.2.5-1-01 and all is good.
  6. Hey guys. I'm having some trouble with file permissions after a transcode. Media directories are nobody:users 666 (rwrwrw). UID and PGID are 99 and 100 in the container settings for Tdarr. However, after a transcode, when Tdarr copies the new file to the original location, the file permissions are root:root 644. This causes problems when I need to write to those directories later. I have tried adding "-e UMASK_SET=0000" to the Extra Parameters section in the container and this has had no effect. I've also tried UMASK. I've also added these as variables in the container settins with no such lock. For kicks, I've tried other UMASK values and no change. Any ideas or suggestions?
  7. Hey guys. Ever since I switched to this container (a few months now) it seems that almost daily it needs to be updated. Is this happening for anyone else or maybe something is wrong on my end with the CA Update plugin.
  8. 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.
  9. 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?
  10. 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?
  11. 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.
  12. 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?
  13. @binhex, any chance you can update this container? The latest release is 4.1.1. Thanks!
  14. 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.
  15. 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?