Re: nginx.conf woes

2022-10-10 Thread Richard Hector
On 3/10/22 02:07, Patrick Kirk wrote: Hi all, I have 2 sites to run from one server.  Both are based on ASP.Net Core. Both have SSL certs from letsencrypt.  One works perfectly.  The other sort of works. Firstly, I notice that cleardragon.com and kirks.net resolve to different addresses,

Re: nginx.conf woes

2022-10-06 Thread hede
On 02.10.2022 15:07, Patrick Kirk wrote: I have 2 sites to run from one server. ... If I try lynx http://cleardragon.com a similar redirect takes place and I get a "Alert!: Unable to connect to remote host" error and lynx closes down. ... You can check if the correct SNI information results

Re: nginx.conf woes

2022-10-02 Thread Patrick Kirk
On 02/10/2022 16:12, Greg Wooledge wrote: On Sun, Oct 02, 2022 at 04:07:05PM +0300, Patrick Kirk wrote: If I try lynx http://cleardragon.com a similar redirect takes place and I get a "Alert!: Unable to connect to remote host" error and lynx closes down. I'm not an expert on nginx

Re: nginx.conf woes

2022-10-02 Thread Greg Wooledge
On Sun, Oct 02, 2022 at 04:07:05PM +0300, Patrick Kirk wrote: > If I > try lynx http://cleardragon.com a similar redirect takes place and I get a > "Alert!: Unable to connect to remote host" error and lynx closes down. I'm not an expert on nginx configuration, but I did notice one thing: >      

nginx.conf woes

2022-10-02 Thread Patrick Kirk
Hi all, I have 2 sites to run from one server.  Both are based on ASP.Net Core.  Both have SSL certs from letsencrypt.  One works perfectly.  The other sort of works. If I go to http://localhost:5100 by redirecting to https://localhost:5101 and then it warns of an invalid certificate.  If I