Kaushal,
The answer from Sergey is actaully accurate. You'd have to modify the
build scripts to exclude the webdav module and then recompile the NGINX
packaging for your environment. This is not *hard* but requires more
knowledge than just NGINX to provide a solution that fits your
organiza
your SSL listen commands are commented out and so are your cert declarations.
Uncomment them and restart your nginx and see if that fixes it
Sent from my Galaxy
Original message
From: Victor Oppenheimer
Date: 2/11/24 17:17 (GMT-05:00)
To: Jeremy Cocks via nginx
Subject: S
I misread. NGINX doesnt see the certs exist meaning whatever user is running
it doesnt have permissions. Make sure your user running NGINX has access down
the whole folder chain.
Sent from my Galaxy
Original message
From: Victor Oppenheimer
Date: 2/11/24 17:17 (GMT-05:0
Rereading from my computer, and sorry for the partial snippet/quote,
your entire path is being prepended with `C:\nginx/conf/` so your
setting that triggers this of `conf/ssl/...` is not proper. Your
configuration root is `C:\nginx\conf` already, so either change your
configuration lines to j
If you only have one IP, then you cannot fix this. SNI is what determines
which certificate to serve for the request. The only solution would be
individual IPs for each domain, thus not needing SNI to get the correct cert
for each domain.
Sent from my Galaxy
Original message ---
--- Original message
From: Jeffrey Walton
Date: 3/15/24 14:24 (GMT-05:00)
To: nginx@nginx.org
Cc: Thomas Ward
Subject: Re: No SNI support on multisite installation
On Fri, Mar 15, 2024 at 2:05 PM Thomas Ward via nginx wrote:
>
> If you only have one IP, then you cannot fix thi
