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.

I flushed my iptables (iptables -F). Same issue

https://www.ssllabs.com/ssltest/ Ran this SSL test, the output is: Assessment failed: Unable to connect to the server

I deleted AWS route 53 A record, then recreate them (domainname.com, www.domainname.com). I am sure it's they are ready via nslookup domainname.com nslookup www.domainname.com Same issue, even thought NPM is off

I think Nginx Proxy Manager (NPM) is not the issue. Stopping NPM container still yield same error ... Meaning the issue occur before NPM.

Hi Guys, UnRaid 6.12.1. Everything is fine yesterday night. Until I remove wireguard server-to-server tunnel. I deleted the external EC2 wireguard that routes all the traffic to my UnRaid, to save AWS VPS cost. The problem now is that all my internet facing apps exposed by Nginx Proxy Manager can't be reached. Firefox: SEC_ERROR_UNKNOWN_ISSUER Google Chrome: NET::ERR_CERT_AUTHORITY_INVALID Here is what I tried, from upstream to downstream 0. Restart Unraid -> no imppact 1. AWS route 53 -> I confirmed that the domain A record is pointed to my UnRaid public ipv4 address. Issue not here 2. UnRaid firewall -> maybe the issue is here? 3. Nginx Proxy Manager (NPM) -> I deleted all the certs and re-provisioned, no impact. I tried another NPM fresh installation, still same. I don't see any logs generated when I go to the site. Does this imply that the request never hit here? 4. Fail2Ban container -> stop this container, no impact 5. ddns-route53 container -> stop this container, no impact 6. VPN manager -> disable this, no impact

I am using unraid 6.12.1, elasticsearch:8.8.1; Followed @lucahammer, @buyenne suggestions, added `TAKE_FILE_OWNERSHIP` and `xpack.security.enabled`; But it don't work for me ... { "@timestamp": "2023-08-22T08:52:24.691Z", "log.level": "ERROR", "message": "fatal exception while booting Elasticsearch", "ecs.version": "1.2.0", "service.name": "ES_ECS", "event.dataset": "elasticsearch.server", "process.thread.name": "main", "log.logger": "org.elasticsearch.bootstrap.Elasticsearch", "elasticsearch.node.name": "0c2a2d6fb5b6", "elasticsearch.cluster.name": "docker-cluster", "error.type": "java.lang.IllegalStateException", "error.message": "failed to obtain node locks, tried [/usr/share/elasticsearch/data]; maybe these locations are not writable or multiple nodes were started on the same data path?", "error.stack_trace": "java.lang.IllegalStateException: failed to obtain node locks, tried [/usr/share/elasticsearch/data]; maybe these locations are not writable or multiple nodes were started on the same data path?\n\tat [email protected]/org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:291)\n\tat [email protected]/org.elasticsearch.node.Node.<init>(Node.java:483)\n\tat [email protected]/org.elasticsearch.node.Node.<init>(Node.java:327)\n\tat [email protected]/org.elasticsearch.bootstrap.Elasticsearch$2.<init>(Elasticsearch.java:216)\n\tat [email protected]/org.elasticsearch.bootstrap.Elasticsearch.initPhase3(Elasticsearch.java:216)\n\tat [email protected]/org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:67)\nCaused by: java.io.IOException: failed to obtain lock on /usr/share/elasticsearch/data\n\tat [email protected]/org.elasticsearch.env.NodeEnvironment$NodeLock.<init>(NodeEnvironment.java:236)\n\tat [email protected]/org.elasticsearch.env.NodeEnvironment$NodeLock.<init>(NodeEnvironment.java:204)\n\tat [email protected]/org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:283)\n\t... 5 more\nCaused by: java.nio.file.NoSuchFileException: /usr/share/elasticsearch/data/node.lock\n\tat java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)\n\tat java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)\n\tat java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)\n\tat java.base/sun.nio.fs.UnixPath.toRealPath(UnixPath.java:833)\n\tat [email protected]/org.apache.lucene.store.NativeFSLockFactory.obtainFSLock(NativeFSLockFactory.java:94)\n\tat [email protected]/org.apache.lucene.store.FSLockFactory.obtainLock(FSLockFactory.java:43)\n\tat [email protected]/org.apache.lucene.store.BaseDirectory.obtainLock(BaseDirectory.java:44)\n\tat [email protected]/org.elasticsearch.env.NodeEnvironment$NodeLock.<init>(NodeEnvironment.java:229)\n\t... 7 more\n\tSuppressed: java.nio.file.AccessDeniedException: /usr/share/elasticsearch/data/node.lock\n\t\tat java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:90)\n\t\tat java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)\n\t\tat java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)\n\t\tat java.base/sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:261)\n\t\tat java.base/java.nio.file.Files.newByteChannel(Files.java:379)\n\t\tat java.base/java.nio.file.Files.createFile(Files.java:657)\n\t\tat [email protected]/org.apache.lucene.store.NativeFSLockFactory.obtainFSLock(NativeFSLockFactory.java:84)\n\t\t... 10 more\n" } Error seems to suggest file permission issue. It worked after I change the ownership and permission for the data mount chown -R nobody:users elasticsearch/ chmod 777 -R elasticsearch/

Regarding the prometheus docker. How do we add `--web.enable-lifecycle` flag? If I do it using ADVANCED VIEW > Extra Parameters -> crash container ADVANCED VIEW > Post Arguments -> run, but it will say can't find prometheus.yml

Anyone config this to use minio as storage backend? Online guide shows that we need to update `config.yml`, but we can't do that if we use unraid docker GUI. https://github.com/distribution/distribution/issues/3493

Hi, I recently updated from v23.0.0 to v25.0.1, and my webGUI showed internal server error. Does anyone has solution to this? I already raised an official issue but no response yet, for complete details: https://github.com/linuxserver/docker-nextcloud/issues/277 I think it's due to nginx, but not sure how to resolve 2022/11/26 23:53:56 [error] 263#263: *5 FastCGI sent in stderr: "PHP message: {"reqId":"mD6fa0vltJXldEalQPUy","level":3,"time":"2022-11-26T15:53:56+00:00","remoteAddr":"xxx.xx.xx.xxx","user":"admin","app":"PHP","method":"GET","url":"/apps/dashboard/","message":"file_put_contents(/data/appdata_oczrczf8fi1o/js/core/merged-template-prepend.js): Failed to open stream: Permission denied at /config/www/nextcloud/lib/private/Files/Storage/Local.php#311","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:107.0) Gecko/20100101 Firefox/107.0","version":"25.0.1.1","exception":{"Exception":"Error","Message":"file_put_contents(/data/appdata_oczrczf8fi1o/js/core/merged-template-prepend.js): Failed to open stream: Permission denied at /config/www/nextcloud/lib/private/Files/Storage/Local.php#311","Code":0,"Trace":[{"function":"onError","class":"OC\\Log\\ErrorHandler","type":"::"},{"file":"/config/www/nextcloud/lib/private/Files/Storage/Local.php","line":311,"function":"file_put_contents"},{"file":"/config/www/nextcloud/lib/private/Files/View.php","line":1179,"function"...PHP message: {"reqId":"mD6fa0vltJXldEalQPUy","level":3,"time":"2022-11-26T15:53:56+00:00","remoteAddr":"xxx.xx.xx.xxx","user":"admin","app":"index","method":"GET","url":"/apps/dashboard/","message":"file_put_contents failed","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:107.0) Gecko/20100101 Firefox/107.0","version":"25.0.1.1","exception":{"Exception":"OCP\\Files\\GenericFileException","Message":"file_put_contents failed","Code":0,"Trace":[{"file":"/config/www/nextcloud/lib/private/Files/SimpleFS/SimpleFile.php","line":92,"function":"putContent","class":"OC\\Files\\Node\\File","type":"->"},{"file":"/config/www/nextcloud/lib/private/Template/JSCombiner.php","line":194,"function":"putContent","class":"OC\\Files\\SimpleFS\\SimpleFile","type":"->"},{"file":"/config/www/nextcloud/lib/private/Template/JSCombiner.php","line":97,"function":"cache","class":"OC\\Template\\JSCombiner","type":"->"},{"file":"/config/www/nextcloud/lib/private/Template/JSR 2022/11/26 23:53:56 [error] 263#263: *5 FastCGI sent in stderr: "0vltJXldEalQPUy","level":3,"time":"2022-11-26T15:53:56+00:00","remoteAddr":"xxx.xx.xx.xxx","user":"admin","app":"core","method":"GET","url":"/apps/dashboard/","message":"file_put_contents failed","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:107.0) Gecko/20100101 Firefox/107.0","version":"25.0.1.1","exception":{"Exception":"OCP\\Files\\GenericFileException","Message":"file_put_contents failed","Code":0,"Trace":[{"file":"/config/www/nextcloud/lib/private/Files/SimpleFS/SimpleFile.php","line":92,"function":"putContent","class":"OC\\Files\\Node\\File","type":"->"},{"file":"/config/www/nextcloud/lib/private/Template/JSCombiner.php","line":194,"function":"putContent","class":"OC\\Files\\SimpleFS\\SimpleFile","type":"->"},{"file":"/config/www/nextcloud/lib/private/Template/JSCombiner.php","line":97,"function":"cache","class":"OC\\Template\\JSCombiner","type":"->"},{"file":"/config/www/nextcloud/lib/private/Template/JSResourceLocator.php","line":125,"function":"pro" while reading response header from upstream, client: xxx.xx.xx.xxx, server: _, request: "GET /apps/dashboard/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "myhostname.com" 2022/11/26 23:53:56 [error] 263#263: *5 FastCGI sent in stderr: "PHP message: {"reqId":"mD6fa0vltJXldEalQPUy","level":3,"time":"2022-11-26T15:53:56+00:00","remoteAddr":"xxx.xx.xx.xxx","user":"admin","app":"PHP","method":"GET","url":"/apps/dashboard/","message":"fopen(/data/nextcloud.log): Failed to open stream: Permission denied at /config/www/nextcloud/lib/private/Log/File.php#84","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:107.0) Gecko/20100101 Firefox/107.0","version":"25.0.1.1","data":{"app":"PHP"}}" while reading upstream, client: xxx.xx.xx.xxx, server: _, request: "GET /apps/dashboard/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "myhostname.com"

While I look forward to k8s, I suspect the odds are not good. We may have better chance setting up a new k8s bare-metal server, and let it be managed by unraid k8s if possible. Let UnRaid do what it does best: NAS. I find that even the VMs are somewhat painful. Say windows VM (can't upgrade 10 -> 11 directly, lack bluetooth support, gpu passthrough, xml vs UI etc)