Jump to content

Caldorian

Members
  • Content Count

    31
  • Joined

  • Last visited

Community Reputation

6 Neutral

About Caldorian

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. Changing the in Namecheap had no affect, no updates were issued. If I deleted the cache file in docker, and let it continue to run, then I'd see in the console (within 5 minutes) that the IP address was updated, and my DNS gets updated properly. Seems like it does check against the cache file, and if it matches, doesn't do anything. Which is kind of good, as I don't want to issue erroneous updates if there's nothing to change. But it would be nice if it would say that I did check and no changes were required. Seems like it's a known "feature" of ddclient, and various people have come up with all sorts of work arounds to deal with dynamic dns providers that require updates every X days: https://www.linuxquestions.org/questions/debian-26/ddclient-will-not-update-316726/#post1611217
  2. I've had it running for the last 5 hours now, and I haven't new log entries since the last time the dockers were restarted.
  3. Thanks @saarg. While it didn't directly resolve my issue, it was enough to get me started. Been trying to get this to work for a while now, and been using a few different templates for it. First there was mace's, and then tried adding lsio's direct from docker hub. I'm guessing I was getting some package corruption between various elements. I had tried removing each of the dockers, including the option to remove the image, but I guess it was still leaving remnants. In particular, I noticed today after removing the image, if I used the "Add Container" option, I could still pick from all the old templates I had tried. So a quick Google search on how to get rid of those (CA --> Previous Apps --> "X"), and installed the docker fresh (yet again). Updated the config file, and success. Even have it working with 2 copies of the container going (2 domains, one still on Namecheap, the other with Cloudflare). For those curious, here's the final Cloudflare config I ended up with: use=web, web=dynamicdns.park-your-domain.com/getip protocol=cloudflare, \ zone=mydomain.com, \ ttl=1, \ login=user@email.com, \ password=ThisIsWhereYourGlobalAPIKeyGoes \ subdomain1.mydomain.com,subdomain2.mydomain.com One question: I'm sure when I had mace's docker going against Namecheap, it would ping in the console log every 5 minutes, stating that the IP was updated. Has this version been updated such that it'll only post to the console if/when the IP changes and it sends a command out to update the DNS entry? If so, is there some change I can make so that it at least logs that the current IP was checked?
  4. Thank you for this. But do you have a configuration file that works with Cloudflare? I must have tried a couple dozen different configs, and I can't get it to work. I keep getting one of two errors: WARNING: file /var/cache/ddclient/ddclient.cache, line 3: Invalid Value for keyword 'ip' = '' WARNING: found neither ipv4 nor ipv6 address Here's the Cloudflare section of my current config: protocol=cloudflare, \ server=www.cloudflare.com, \ login=XXXXXXXX@XXXXXX.com \ password=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX \ zone=XXXXXX.com, \ YYYYYYYY.XXXXXX.com Edit: I'll add in that if I add a line to detect my IP from a web page (ie. use=web, web=dynamicdns.park-your-domain.com/getip), I get the following series of errors: WARNING: file /var/cache/ddclient/ddclient.cache, line 3: Invalid Value for keyword 'ip' = '' WARNING: skipping update of YYYYYYYY.XXXXXX.com from <nothing> to WWW.XXX.YYY.ZZZ. WARNING: last updated <never> but last attempt on Thu Jun 13 12:26:25 2019 failed. WARNING: Wait at least 5 minutes between update attempts. With the WWW.XXX.YYY.ZZZ being my actual IP address. That would imply that ddclient it actually getting my IP address. But for whatever reason, it's just not parsing it correctly to send it to Cloudflare.
  5. Think I found the issue. Silly me, I had the first DNS server listed on my unraid network settings set to my pihole docker that I run on it's own IP. Of course, unraid can't talk to it due to macvlan network isolation. Updated my dns setting so that unraid only has the external DNS entries (8.8.8.8, 1.1.1.1, etc.) and update resolution seems to be back to normal.
  6. Upgraded to 6.7.0 last week, and have started running into an issue updating my docker containers. When I click the Check for Updates button, all my dockers just sit on "checking..." forever. Left it for 20 minutes now, and it hasn't returned. If I refresh the Docker page, then I can see that I the check process has completed (or at least progressed), and several of my dockers do have updates available. I've attached the diagnostics for review. diagnostics-20190531-2039.zip
  7. Just installed it on a 6.6.7 install, and it's looking good. However, I'm getting an alert in it about my cache drive, saying that the btrfs allocation is 97.3%. However, if I look at my unraid dashboard, it's only around 60% allocated (157GB out of 256GB). Any clue why this alert is being raised, and how I may clear it?
  8. Has anyone been able to get the Pieces plugin (https://dev.deluge-torrent.org/wiki/Plugins/Pieces) to work successfully with this? The best I've ever gotten is for the tab to show up, but nothing to be shown in the tab. Most of the time for me, it ends up where the Web UI can't connect to the running instance.
  9. Tried the apctest stuff. First attempted to run the batter calibration, and it wouldn't run. Next up, I checked the battery date, and it was properly reporting that it was replaced on 2/2/2018. Then tried to run a self test, which failed. So then I decided to go for it, and I pulled the plug from the wall, and let it run off the battery for 10 minutes. No issues there. Plugged it back in, and re-ran a self-test manually from the UPS (holding the power button for 6 seconds). Self test passed and the alarm has cleared. Still, would have been nice if you guys could have addressed my original question at some point an say if there was a way or not to silence the notification in unraid.
  10. No way on the UPS to tell it that the battery was replaced. Only thing you can do is run the self test. After a couple of self tests on the new battery, the alerts on the UPS went away. Been running without issues for about 10.5 months now. It's only recently started alerting me about the battery again. Planning on replacing the UPS as a whole in the future, as there's better options out there now for cheaper. But getting back to my original question: Is there a way I can get Unraid to stop alerting me about this? I don't need the reminder every 9 hours.
  11. I replaced the battery pack less then a year ago. It's failing the self test, but the estimated run-times are still plenty high. If this was a production system, I'd do something more, but given it's just my home server, I'm more concerned about the line conditioning and dealing with brown-outs, which it's handling fine.
  12. I have an APC Back-UPS Pro 1500 connected to and configured on my Unraid server. The UPS is now reporting that the battery has "failed", even though it looks like it's working fine. As a result, my Unraid server is pinging me every 9 hours about the failed battery. Is there any way that I can disable this notification from happening, while keeping the other notifications intact?
  13. Since I cut over from a windows 10 system to unraid, using the linuxserver.io Plex image, some of my users have complained that sometimes when they try and stream to a chromecast, they have to kick it off 2 or 3 times for it to go successfully. Any thoughts on what might be the issue, and or where I can look to find out?
  14. Tried playing with the docker this weekend, looking to see if I could use it to replace my delugevpn docker (one thing deluge is missing that I'd like to see is information about what blocks/pieces are downloading and/or missing). Ran into 2 major issues: 1) Ports being listed as not open. I figured out how to modify the rtorrent.rc file to set custom ports, but still didn't work. Admittedly, this could be an issue with my VPN provider, but haven't seen anything from deluge indicating that this is an issue. 2) And this is the bigger issue for me: I couldn't get magnet links to work. With Deluge, I just needed to copy the link, paste it as a URL, and the torrent kicks off without issue. Trying a similar process with rtorrent, it just hangs there with the torrent labelled as the magnet hash value. It wasn't until I did a full download of the torrent and importing of it that things would start to work. The other thing that was getting at me was that my testing torrents were listed as having errors, but I couldn't find anything that would tell me what the actual errors were. The logs tab would only show me general data about the whole rtorrent environment, and nothing else I poked at seemed to show things.
  15. Running 6.5.2 on my system. Use SSL is set to auto, but when I access my server it's not redirected to an HTTPS connection. I guess as a result(?), the "Open Web UI" link in UnBALANCE is left as a regular http:// link.