OK, I’ve inserted that return into the conf file. BUT, there’s an error from
an entry I’ve had in there before of a master error.log. It says the path
provided is no such file or directory. That path is nowhere to be found in
nginx.conf or alpha.conf.
Something wrong with nginx? It isn’t re
I did notice that nginx.conf structure started to recognize trailing semicolons
recently. I have updated to a new OS from an old box on several versions ago.
Comments are allowed on the same line in nginx.conf still?
Cheers, Bee
> On Jun 28, 2021, at 7:08 PM, Sergey A. Osokin wrote:
>
> We
Ya that’s too many to report. I have a catch-all with *.conf. I can restrict
it down to that main nginx.conf and the extra VHost.
Same as I posted before. Same result. This has the main two in my nginx.conf,
and the included one. That last one has its own conf file:
include /opt/
Same result. Default returned. Nothing in access log nor error log.
Cheers, Bee
> On Jun 28, 2021, at 6:35 PM, Sergey A. Osokin wrote:
>
> Seem like curl didn't send a valid "Host: alpha.local" header for some reason,
> that's why NGINX replied with an answer for default_server.
>
> Could
I have a VHost that isn’t serving up. I’ve changed nothing, and it just
started defaulting to the default_server.
The VHost is included in a catch-all for all the other local domains (my
workstation):
include /opt/homebrew/etc/nginx/servers/*.conf;
I’ve even hard coded the VHost in its own
