Re: curious .conf problem

2022-01-11 Thread David27
>> 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 certb

Re: curious .conf problem

2022-01-10 Thread Francis Daly
On Sat, Jan 08, 2022 at 06:49:39PM -0500, David27 wrote: Hi there, > Hello Francis, thanks for the hints. It is working now. Good to hear you have something that works for you :-) > I will endeavor to provide a description that a reader can follow here. And thank you for this; it is very har

Re: curious .conf problem

2022-01-08 Thread David27
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

Re: curious .conf problem

2022-01-07 Thread Francis Daly
On Fri, Jan 07, 2022 at 01:46:06PM -0500, David27 wrote: Hi there, > > 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. "in a suitable server{}". For a connection to port 80, there

Re: curious .conf problem

2022-01-07 Thread David27
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 l

Re: curious .conf problem

2022-01-06 Thread Francis Daly
On Thu, Jan 06, 2022 at 08:37:46AM -0500, David27 wrote: Hi there, It's better for future readers if you include the full details in the email; but in this case it seems straightforward based on the url content I see. > "https://www.thomas-walker-lynch.com"; is picked up by a server block with a

curious .conf problem

2022-01-06 Thread David27
"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.co