>> 2. The proximate cause for all these problems: Certbot did not generate an >> SSL certificate for a server block with a 'dot' prefix name even when it was >> listening to 443. It didn't complain, it just didn't expand the >> certificate. > > That seems like a curious thing to do. > > Maybe certbot "knows" that wildcard certificates are somehoby David27 - Nginx Mailing List - English
Hello Francis, thanks for the hints. It is working now. >> 2) Gosh I am also hesitant to put >> the entire sites .conf file in a public email list where for evermore they >> are viewable by people who might notice exploits, even those unrelated to >> the issue at hand. > >That is a valid concern; best is if you can include a complete-but-minimal > configby David27 - Nginx Mailing List - English
Hello Francis, > If you have no "server_name www.thomas-walker-lynch.com;" ( There is indeed a server block already defined with a server name www.thomas-walker-lynch.com. Nginx just chooses to use a different block that has a different server name. (Or perhaps I messed up the syntax for it lol) Note that everything else seems to be working. As for copying *everything*by David27 - Nginx Mailing List - English
"https://www.thomas-walker-lynch.com" is picked up by a server block with a different virtual host name. A bit of a head scratcher so perhaps the experts here can tell me what rookie mistake I have made? Detailed information and .txt file versions of the conf files at this link. thomaswlynch.com/conf/info.txtby David27 - Nginx Mailing List - English