WillyThunder

Ok, thanks for your post. I recently got a new 5060 Ti, so I have to use the open‑source driver, which might be the problem.

Hi everybody. Since about two weeks ago, I’ve been getting an “Out of Memory” warning in the Fix Common Problems plugin. I’ve already run a memtest, and it seems to be fine. Could someone please have a look at the diagnostics? I’m a bit worried because I read a post about possible login attacks that can trigger an “Out of Memory” warning. Thanks in advance. ares-diagnostics-20260201-0941.zip

Hi everybody, I have a strange problem with NPM and renewing my certificates. My setup is as follows: I own several domains; let’s use "example.com" as an example. I’ve configured a CNAME for a subdomain "test.example.com" that points back to example.com. The DNS A record is set to my IP address. However, I’m unable to renew my certificate with this configuration. When I set the CNAME for the subdomain "test.example.com" to a DuckDNS domain (with the same IP as the A record), the certificate is created without any issues. Why on earth is this happening? The ports are open; otherwise, I wouldn’t be able to get a certificate in the first place.

Yes I have. Otherwise i could not get SSL-Certificates for the subdomains which i totally can, right? Log says [2/3/2023] [9:41:31 AM] [Express ] › ⚠ warning Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-60" --agree-tos --authenticator webroot --email "[email protected]" --preferred-challenges "dns,http" --domains "example.com" Any Ideas?

Same message if i uncheck HSTS or HTTP/2 Support or even Force SSL

Hi There I got this worked out, passing the traffic from the maindomain to docker is now possible. I can't figure out why i can get a ssl-certificate with a subdomain no problem "cloud.example.com" but I am unable to to this with the maindomain "example.com". Proxy Host is right?

Hello There I got kind of a basic question. I'm using the nginx proxy manager for most of my dockers like nextcloud, homeassistant using a subdomain like cloud.example.com or homeassistant.example.com how do i get the main domain "example.com" to work with a specific docker? I always get the message "example.com is already in use". Thanks