natiz

I can't get Fan Control to work on Dell PowerEdge T420. On the Fan Control tab, a popup appears: But there's no Configure button (Fan control is indeed stopped). Note that I am able to control the fan manually using the ipmitool (installed via NerdTools), eg `ipmitool raw 0x30 0x30 0x01 0x00` and `ipmitool raw 0x30 0x30 0x02 0xff 0x20` to set it to 20%.

Well, I feel a bit ashamed I tried removing/changing as you suggested, and then I started triple-checking my router is forwarding as it should As it turns out, I'm using a VERY old firmware version of DD-WRT (DD-WRT v24-sp2 (12/24/13) std). After some reading, there seem to be a known issue around NAT loopback/port forwarding which was fixed in later versions There's a workaround available but I decided to upgrade to the latest firmware, which seem to resolve the issue. All is working as expected - thanks @CHBMB

After reading a bit on certbot I think I understand better - the script runs certbot in standalone mode - it itself listens on 443 to perform the verification. I did some troubleshooting (built the image w/o the starter script, nginx turned off) from the container itself: certbot certonly --verbose --non-interactive --renew-by-default --standalone --preferred-challenges tls-sni --rsa-key-size 4096 --email "[email protected]" --agree-tos -d "x.mydomain.com" Same error, only this time, I ran watch on curl https://localhost, and after a few seconds, got this: After that certbot finished and from then it was connection refused (which is fine).. btw, here's my docker run cmd (Router routes both 443 and 80 to 443 and 81): docker run -d --name="letsencrypt" --net="bridge" --privileged="true" -e HOST_OS="unRAID" -e "EMAIL"="[email protected]" -e "URL"="mydomain.com" -e "SUBDOMAINS"="x," -e "ONLY_SUBDOMAINS"="true" -e "DHLEVEL"="2048" -e "PUID"="99" -e "PGID"="100" -p 81:80/tcp -p 443:443/tcp -v "/mnt/user/appdata/letsencrypt":"/config":rw linuxserver/letsencrypt

Yes its resolved and answered. I do think its trying to connect, as the error clearly says: also, see this: https://tools.ietf.org/html/draft-ietf-acme-acme-01#section-7.3

I can't seem to get this one up and running - and can't seem to figure out how anyone else did it The thing is, letsencrypt tries to validate my domain before nginx is even up - and that fails since no one is listening on port 443 (no nginx) Since this occurs on the init script, which fails, s6 terminates everything bringing the container down - so nginx doesn't even come up. How did you guys set it up? An easy fix for me would running another container with just nginx - but that misses the point of having both on the same container Here are my logs: