duskofdawn

First command returns the following: 140695964602432:error:0200206E:system library:connect:COnnection timed out:../crypto/bio/b_sock2.c:108: 140695964602432:error:200BA077:BIO routines:BIO_connect:connect error:../crypto/bio/b_sock2.c:109: Second command returns the following: OCI runtime exec failed: exec failed: container_linux.go:346: starting container process called "exec: \"nslookup\": executable file not found in $PATH": unknown. I'm using the standard config files from the github.

Certificate was created in Letsencrypt through NPM, DNS isn't proxied, just Google domains DNS, wildcard record pointing to IP, updated through dynamic DNS (different server, same network). I know that it works because I've got a second proxy host set to route unsecure to the same server, and that one works. It's just when adding the SSL.

SSL worked for about a day before breaking again. I'm not sure what I was doing that got it to work vs not work. I spun up a new VM, downloaded the example config, and after initial setup, created two hosts. They both point to the same server, one has SSL enabled with a letsencrypt certificate generated by NPM. The other is HTTP only. When I go to the SSL one (in CHrome), it throws up "Your connection is not private NTT::ERR_CERT_AUTHORITY_INVALID. The cert itself is from BMS. If I click advanced, and then proceed, I get ERR_EMPTY_RESPONSE.

I've got NPM up and running, and I've got it working with a host (jellyfin), however, when I enable/force SSL, it breaks. As soon as I disable SSL, it works again. I made sure to request a letsencrypt cert, and it seems to have been successful. It's behind a pfsense firewall, and any time port 80 appears, ports 443 and 81 appear with it (alias for web ports). Any suggestions/troubleshooting? EDIT: Nevermind. Working flawlessly now. Not sure if it was that particular computer I was using, dns cache or what. Thanks for this program, it's saved me a lot of headache.