ehawman

Aha it was a combination of incorrect http port and expired login. I thought it was outdated certs so I followed this page (which I've definitely already done) and `use_ssl no` told me the correct default URL! I've now signed in and all is well. Thanks!

I haven't used this computer in around a year now. I want to tinker with it so I boot it up. Unraid Connect shows it as offline. I have a custom HTTPS port but trying to access that via my local network goes to an nginx 404 page. I'm pretty sure I have the correct HTTP port, but it gets ERR_CONNECTION_REFUSED and I seem to recall that being disabled. I am able to SSH in from another machine on my network and I have root creds so there's a foothold. I can also ping public IPs from it so it definitely has internet access. I see suggestions on this forum to boot into safe mode, but the only instructions on how to do that use the WebUI. I would like to just update my current config rather than restart from scratch. How can I get into the WebUI from here? Thanks!

Unraid 6.12.3 So I followed this guide and got dnsmasq set up on my server. Except I couldn't install or launch dnsmasq because... it was already running. Running `ps -feww | grep dnsmasq` yielded this: UID PID PPID C STIME TTY TIME CMD nobody 10470 1 0 22:34 ? 00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp script=/usr/libexec/libvirt_leaseshelper root 10471 10470 0 22:34 ? 00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper Ok so I'm guessing that in the intervening 14 years Unraid has added a dnsmasq instance. Printing the contents of the default.conf reveals that libvirt is generating these files automatically. So all this to say: Can I use my Unraid tower as a DHCP/DNS server with dnsmasq or would attempting to do so break libvirt? If I can, what is the most correct way to go about that?

Oh derp. I saw "sha256 hash", saw the hashes below, and immediately skipped the rest of the post thinking it was irrelevant. My bad.

Apologies if this is already asked, but the default Docker system always shows the containers as having an available update. This causes Fix Common Problems to have a hissy fit. I can ignore those warnings if I have to, but is there any way for the Compose Up//Update Stack processes to tell Unraid's Docker implementation that they've done an update? If not, is there a way (in your opinion) that the problem could be addressed from the Unraid side? Thanks!

I have a few requests for your consideration. First, I would really like to have the latest fish shell version included. I'm using the version from Masterwishx because they're a hero, but it would be even better if this was integrated. Secondly, a couple of packages that I like which aren't on the Modern Unix list: croc: croc is a tool that allows any two computers to simply and securely transfer files and folders. micro: micro is a terminal-based text editor that aims to be easy to use and intuitive, while also taking advantage of the capabilities of modern terminals. It comes as a single, batteries-included, static binary with no dependencies; you can download and use it right now! neovim: "Agressively refactored vim" Finally, let me link the contents of the (IMO) excellent Modern Unix list, with my personal thoughts in (parens). Items that are already in NerdTools are omitted. Of these, I would call bat, fd, ripgrep, sd, and zoxide my "essential" packages. bat: A cat clone with syntax highlighting and Git integration. exa: A modern replacement for ls. lsd: The next gen file listing command. Backwards compatible with ls. (Personally I prefer lsd to exa but they both are stepping in to the same role) delta: A viewer for git and diff output. dust: A more intuitive version of du written in rust. duf: A better df alternative. broot: A new way to see and navigate directory trees fd: A simple, fast and user-friendly alternative to find. (This one beats the pants off of find in many cases) ripgrep: An extremely fast alternative to grep that respects your gitignore. ag: A code searching tool similar to ack, but faster. mcfly: Fly through your shell history. Great Scott! choose: A human-friendly and fast alternative to cut and (sometimes) awk. jq: sed for JSON data. sd: An intuitive find & replace CLI (sed alternative). (Holy smackerel this thing slaps) cheat: Create and view interactive cheatsheets on the command-line. tldr: A community effort to simplify man pages with practical examples. (There are actually a number of implementations of this, tldr++ and tealdeer being some of the best imo) bottom: Yet another cross-platform graphical process/system monitor. glances: Glances an Eye on your system. A top/htop alternative for GNU/Linux, BSD, Mac OS and Windows operating systems. gtop: System monitoring dashboard for terminal. hyperfine: A command-line benchmarking tool. gping: ping, but with a graph. procs: A modern replacement for ps written in Rust. httpie: A modern, user-friendly command-line HTTP client for the API era. curlie: The power of curl, the ease of use of httpie. xh: A friendly and fast tool for sending HTTP requests. It reimplements as much as possible of HTTPie's excellent design, with a focus on improved performance. zoxide: A smarter cd command inspired by z. (I LOVE THIS ONE. Seriously any z jump implementation would be incredible, esp since we can define the database location to be on a persistent share. Makes your life so much easier.) dog: A user-friendly command-line DNS client. dig on steroids

The goal: Run a Firefox container which uses the qbittorrentvpn container as its network. My stack: https://pastebin.com/E6Naetvt Result: qbittorrentvpn works perfectly, the Firefox container successfully hooks in to its network and has an internet connection (confirmed via CLI), but attempting to connect to port 3000 times out (accessing from a different machine on the same network). Change: Manually edited iptables in the qbittorrent container via CLI iptables -I INPUT 11 -i eth0 -p tcp -m tcp --dport 3000 -j ACCEPT iptables -I INPUT 12 -i eth0 -p udp -m udp --dport 3000 -j ACCEPT iptables -I OUTPUT 11 -o eth0 -p tcp -m tcp --sport 3000 -j ACCEPT iptables -I OUTPUT 12 -o eth0 -p udp -m udp --sport 3000 -j ACCEPT Tested and this works just as I expected. So my two questions are: 1. Is what I did "safe"? Both from a network security and a stability perspective? What entity set the other rules (like the ones regarding ports 8080)? 2. What is the "correct" way to change these iptables so I don't have to manually touch this in the future? I can't find a way to do this through the compose file. Thanks for all the amazing work you do!

@JorgeB @trurl THANK YOU! Y'all saved my bacon So glad to be off the external drive and in compliance at last. Y'all rock.

@JorgeB To clarify, rebuilding is doing a New Config with "Parity is already valid" checked, right?

@trurl @JorgeB Here they are tower-diagnostics-20221005-2252.zip

@trurl Thanks for the advice. I'll try to take a look at it soon but A) It's my birthday and B) I'm heading out of town tomorrow so my time is extremely squeezed. Apologies for stringing y'all along like this. I really appreciate you taking the time.

@JorgeB Will do. Unfortunately I can't seem to use "Local access" via My Servers (I'm at work at the moment). It's showing ERR_CONNECTION_TIMED_OUT. However My Servers says it's online and correctly identifies the array as stopped? Weird.

@trurl Here you go! tower-diagnostics-20221005-0038.zip

@JorgeB @trurl Parity complete. What's the next step?

@JorgeB@trurl Running parity now. Estimated 1d10h