LittleMike

I have them all on a custom bridge behind a Traefik reverse proxy, so they should all be using the host DNS. So yeah, definitely a mystery as to why they still worked while resolv.conf was broken. I just updated to 6.11.5 and took a "clean" diagnostics file (everything is working, including the My Servers plugin, which immediately told me to update after the OS upgrade.) Now I'm curious to see if the issue still happens. If resolv.conf is breaking, that would point to dnsmasq being broken. Otherwise nothing would be overwriting resolv.conf. As far as mysteriously working again, I may have the answer to that - I rebooted the server because I was tired of the big red triangle staring at me. Stopped the array, performed a reboot, everything worked for like an hour, then the My Servers plugin complained again. I did not check resolv.conf, but it's quite possible it was also broken. If it happens again, I'll make a new post with a new diagnostics file in the general forum. Thanks again.

That would make sense. If local DNS is broken, then it can't resolve anything, not just *unraid.net. Why would container lookups succeed, though? That's the part I don't understand. Like trackers, indexers, etc that are all reaching out to DNS all the time. Another question - how could resolv.conf even break? Doesn't dnsmasq run on startup and that's it? Nothing should be writing to resolv.conf (or overwriting) for it to break in the first place. Strange, normally when there's a new version, I get a banner across the top of the web GUI (I always have a tab open in my browser to it). I have no issue doing the upgrade to 6.11.5, I was just completely unaware of it.

Resolve conf looks just fine to me. I am also not currently having the My Servers plugin issue, so it's kind of a chicken and egg thing right now. Is 6.11.5 stable? I've only run the stable editions. Strangely enough, I don't think I had these problems on 6.8. They only started with either 6.9 or 6.10. ~# cat /etc/resolv.conf # Generated by dhcpcd from br0.dhcp nameserver 192.168.1.1 I did see an "unavailable" message in the Docker tab next to all the dockers now that I've looked. I had no reason to check previously because I saw no other symptoms related to DNS. Like I said, all my external facing front ends work, all my docker container lookups worked (like the Arrs, etc). So as far as I'm aware, only unraid.net related things broke. Which still could point to an unraid issue, not a networking issue. Does community apps filter through *unraid.net?

Again, nothing on my network is having an issue. The server itself did not appear to be having any issues other than DNS lookups to unraid.net failing. I took a diagnostics snapshot, I just didn't upload it. You can find it here. I didn't do a deep dive, but like I said, everything else is working just fine as far as I can tell. All my containers and VMs are running, including outside facing frontends with external URLs blackpearl-diagnostics-20221128-1538.zip

Same issue as the other poster, like I mentioned. It resolved itself, but then just happened again today. I got this error: ERROR [getaddrinfo ENOTFOUND mothership.unraid.net] Do you want the whole diagnostics file? Because everything else is working just fine. It's just the My Servers plugin that fails and every single time it appears mothership.unraid.net becomes unavailable. Is it normally pingable? Because it's not as I type this. unraid-api.txt

Considering so many people are having this same issue, why would you think we are all having network issues? My network has been rock solid both on the LAN and WAN side and I'm getting this same error. Have been ever since the upgrade to 6.11.1.

Sorry if this is a dumb question, but the CA template shows the current version of Tdarr includes node. So do I still have to install the separate node container? Reason I ask is I'm currently trying to set this up for the first time and even though docker run finishes successfully, the logs are showing me: Please make sure the IP and Port are correct else it may be a firewall issue. �[91m[2022-04-09T12:54:42.350] [ERROR] Tdarr_Node - �[39mNode: 192.168.1.100:8267 - nodeID 'InternalNode1' could not be contacted by the server. Not sure what I'm doing wrong. I haven't installed the separate container yet, figuring I want to try to get this running as is first. Okay, so I have a clue but not how to fix it. The port assignment in the error log entry says it's trying to reach the InternalNode1 on port 8267 but nowhere is that configured in the template, nor does it show up in the docker run. So something internal is trying to map that port. EDIT 2: So poking around paid off. There's definitely something wrong with the template/image. The Tdarr_Node_Config.json file that gets automatically created on startup configured the following: "nodeID": "InternalNode1", "nodeIP": "192.168.1.100", "nodePort": "8267", I didn't set 8267 anywhere, so that's where it came from. Edited the json file, restarted the container, and all was well. So perhaps this is the issue a few posters above me had where they couldn't get the internal node working and had to set it to false and add the node container. Check the json file, edit it, ???, profit!

Okay, good. That's a starting point. Though I'm at a loss as to how that could be because nothing has changed on my end other than the container updated. *EDIT* That did it @JonathanM! All I did was go back to the container, put in my username and password (I noticed it was the older style one that PIA used) and then the UI came back up after a couple of minutes. Thank you. So next question is, what does the webui have to do with a wrong username/password for a VPN provider? Technically the container should still start, no?

I would if it gave any indication as to what it's failing auth on: 2021-11-17 20:49:21,991 DEBG 'start-script' stdout output: 2021-11-17 20:49:21 AUTH: Received control message: AUTH_FAILED

I don't even see a username or password in that log file. I do see some failed auth errors though. Think it's okay to still post it raw or should I dig deeper?

I noticed today that deluge had updated and now the web interface won't load. Any thoughts on how I can troubleshoot this? I can't make sense of the logs, but it looks fine to me.

Thanks! In my case, I only have 1 vault, 1 user, myself. So my setup is simple enough that this should be enough.

That's the thing - it's running and working just fine. The only thing I can't do is edit it in the unRAID GUI. The container itself is otherwise normal. What is the best procedure for backing up/importing passwords? I believe I had to do that once in the admin panel. Anything I should worry about?

So unfortunately, I don't think there's much here to go on: /--------------------------------------------------------------------\ | Starting Vaultwarden | | Version 1.22.2 | |--------------------------------------------------------------------| | This is an *unofficial* Bitwarden implementation, DO NOT use the | | official channels to report bugs/features, regardless of client. | | Send usage/configuration questions or feature requests to: | | https://vaultwarden.discourse.group/ | | Report suspected bugs/issues in the software itself at: | | https://github.com/dani-garcia/vaultwarden/issues/new | \--------------------------------------------------------------------/ [INFO] No .env file found. [WARNING] The following environment variables are being overriden by the config file, [WARNING] please use the admin panel to make changes to them: [WARNING] SIGNUPS_ALLOWED, INVITATIONS_ALLOWED, ADMIN_TOKEN [2021-10-28 22:13:43.893][parity_ws][INFO] Listening for new connections on 0.0.0.0:3012. [2021-10-28 22:13:43.895][start][INFO] Rocket has launched from http://0.0.0.0:80 [2021-10-28 22:13:50.440][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.31:60252.

I'm at work right now so unfortunately I won't be able to get to that till tonight. Do you want a screenshot of the left-click Show Logs or is there a particular log file you want me to upload? I can do either tonight.