tamalero

False Alarm: (last update lol) It was cloudflare blocking let'sencrypt. Somehow it triggered a block in my security settings. For those having a similar issue. Just add a SECURITY RULE that whitelists all letsencrypt production hostnames or the ACME directory URL of your website. Then choose to "SKIP" any other rule or challenge. Very useful if you're blocking countries with the proxied version or adding JS/managed challenges to protect your site from bots. Strangely it is not working for the addon domain. Unsure why. my primary domain resolves correctly. domain1 does not. The weird part is that the resolver ips makes absolutely no sense. The docker nginx/php image that hosts my website is in a 192.168.1.62 address. So.. from where are those 104.21.X.X addresses coming from? Here is the log: edit There is something really weird about this specific domain. Despite mirroring all the settings I did for my own domain. Including setting the cloudflare DDNS docker, setting up up the cloudflare domain.. Im getting weird stuff.. For example, trying to audit or checking the domain from the proxy manager outside the adding domain, shows this: domain1.cc: There is a server found at this domain but it returned an unexpected status code 403. Is it the NPM server? Please make sure your domain points to the IP where your NPM instance is running. removing ALL cloudflare blocks (country blocks). It gives a similar error. About site being there but NPM not being detected. edit2 Something went wrong with my server. Now all lets encrypt renewals fail. I think something went wrong with my config. As I cannot use connect to outside domains

Question: What is the proper way to add multiple domains to a single nginx/apache instance? If I try to add it as a new separate entry going to the same container ip address. It always me errors about failing (unauthorized, invalid response)

Hi Folks! Getting some errors on trackers after I updated to 5.1 The error on the trackers show: host not found (non authorizative) try again later Note all trackers worked fine with prior versions. Someone shared this error report: https://github.com/qbittorrent/qBittorrent/issues/22366 But how does this work with the Docker version for Unraid? Can this be fixed? Note that not all trackers fail, just a few.

Hi Folks! Is there a way to install python or other libraries inside the container to be able to run local scripts for automation? Because so far I notice with the default n8n docker image for Unraid does not seem to have yum, apt-get, dnf nor even microdnf.

I have run the command to locate the MCE_AMD file and its present. What needs to be done so I still do not get the error? If I have the AMD one present, why I am still seeing the error? @trurl: Were you able to check the logs?

Here you go. cesnas-diagnostics-20220804-0415.zip And you were right, I see now the MCELOG error in the other diagnostics tab. Jul 30 17:18:28 CesNAS kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) Jul 30 17:18:28 CesNAS kernel: floppy0: no floppy controllers found Jul 30 17:18:28 CesNAS kernel: ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\GSA1.SMBI) (20210730/utaddress-204) Jul 30 17:18:29 CesNAS mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead.

Having this same issue as well. Now my Server refuses to fully shutdown. It hangs with a Kernel panic when shutting down/rebooting. Otherwise works correctly as long I do not shutdown/reboot. system: AMD Threadripper 3970X (24 core 48 thread) on an Gigabyte Aorus Pro WIFI TRX40. Any recommendation? And no, its not a MCELOG error.