shawnngtq

Hi 🙋‍♂️ Machine Check Events detected on your server - Your server has detected hardware errors. The output of mcelog has been loggeg. Post your diagnostics and ask for assistance on the Unraid forums More Information Can someone guide me on this. I see some errors in logs, related to rsyslog, but don't think it's the cause for reboot/crash? Perhaps because of this? But I don't change my hardware. Feb 24 09:41:25 Thanos root: Fix Common Problems: Error: Machine Check Events detected on your server Feb 24 09:41:25 Thanos root: mcelog: ERROR: AMD Processor family 25: mcelog does not support this processor. Please use the edac_mce_amd module instead.thanos-diagnostics-20260224-0943.zip

which NUT details tell us how long our battery can last? I do not see `battery.runtime` / `battery.runtime.low` information nut-ups.dev

I am running fail2ban with host network. However this container's iptables is different from UnRaid's iptables. How can we make sure they are the same?

I configured WireGuard server-to-server tunnel, that causes this issue.

The problem is with my ISP provider. Changing from ONT to ONR caused this. Solution is to get new ISP provider that uses ONT.

This issue happen only on the UnRaid terminal and docker containers. I can curl from my VM. I suspect it means issue is specific to UnRaid + docker network interface

Attached diagnostic

root@myUnraidAccount:~# nslookup app.myhostname.com Server: 192.168.1.123 Address: 192.168.1.123#53 Non-authoritative answer: app.myhostname.com canonical name = myhostname2.com. Name: myhostname2.com Address: 167.123.12.123 root@myUnraidAccount:~# curl -v https://app.myhostname.com -4 * Trying 167.123.12.123:443... * connect to 167.123.12.123 port 443 failed: Connection refused * Failed to connect to app.myhostname.com port 443 after 2040 ms: Couldn't connect to server * Closing connection curl: (7) Failed to connect to app.myhostname.com port 443 after 2040 ms: Couldn't connect to server root@myUnraidAccount:~# curl -v https://app.myhostname.com -6 * Could not resolve host: app.myhostname.com * Closing connection curl: (6) Could not resolve host: app.myhostname.com root@myUnraidAccount:~# traceroute https://app.myhostname.com https://app.myhostname.com: Name or service not known Cannot handle "host" cmdline arg `https://app.myhostname.com' on position 1 (argc 1) root@myUnraidAccount:~# traceroute app.myhostname.com traceroute to app.myhostname.com (167.123.12.123), 30 hops max, 60 byte packets 1 167.123.12.123 (167.123.12.123) 37.629 ms 37.624 ms 37.620 ms My `/etc/resolv.conf` root@myUnraidAccount:~# cat /etc/resolv.conf # Generated by dhcpcd from br0.dhcp nameserver 192.168.1.124 nameserver 192.168.1.123 # Generated by rc.inet1 My `/etc/hosts` root@myUnraidAccount:~# cat /etc/hosts # Generated 127.0.0.1 myUnraidAccount localhost 54.149.176.35 keys.lime-technology.com When I tried to `curl` in my UnRaid terminal `app.myhostname.com`, it's failed, but `nslookup` work. Any idea what's wrong with my `resolv.conf` or `hosts`? Both of them are default generated, I don't touch them.

My solution: 1. Stop VM manager and Docker service 2. Change `IPv4 DNS server assignment` to `Static` -> to regenerate `/etc/resolv.conf` 3. Change `IPv4 DNS server assignment` to `Automatic` -> originally value, and preferred it to be automatic This is definitely on UnRaid, I don't touch that `resolv.conf` file. And it only gets regenerated by toggling `IPv4 DNS server assignment` value

UnRaid version: 6.12.8 I think my UnRaid has some network issue, specifically DNS. root@yourhostname:~# nslookup google.com ;; connection timed out; no servers could be reached root@yourhostname:~# cat /etc/resolv.conf # Generated by rc.inet1 root@yourhostname:~# cat /etc/resolv.conf.head root@yourhostname:~# cat /etc/resolv.conf.tail # Generated by rc.inet1 Is UnRaid `resolv.conf` supposed to be empty? If not? How should I fix it?

If say you have thousand of pages. Will Google page index a page every (few) minute(s)? If yes, when the containers reboot everyday, it will cause the Google index to fail at that minute? Or will Google ignore that single failure and continue indexing the rest? I'm curious if others face similar issue with their UnRaid container webapp?

I am running a few web applications via docker on my unraid. Every day, appdata backup plugin will backup appdata, during this time, the containers will have short downtime. My concern is that downtime affects my Google page indexing Many of the pages has the status: Crawled - currently not indexed Anyone else encounter the same issue? Or did some experiment?

Wireshark only show the local traffic, not external traffic. When I go to these domains with different internet, instead of `Your connection is not private / Warning: Potential Security Risk Ahead`, the browser shows `The connection has timed out` Perhaps the server's firewall block external traffic?

Used Wireshark to track traffic. So it seems that AWS route 53 did pass the traffic to my server. The problem is in my server, not route 53 then. Protocol: TLSv1.2 Length: 61 Info: Alert (Level: Fatal, Description: Certificate Unknown) 20240302 - Copy.txt

Use NPM to test server reachability. *.domainname.com: There is a server found at this domain but it returned an unexpected status code Invalid domain or IP. Is it the NPM server? Please make sure your domain points to the IP where your NPM instance is running. domainname.com: There is a server found at this domain but it returned an unexpected status code Invalid domain or IP. Is it the NPM server? Please make sure your domain points to the IP where your NPM instance is running.