On Thu, Dec 12, 2019 at 04:52:25PM +0000, James Read wrote: > On Thu, Dec 12, 2019 at 4:42 PM Francis Daly <fran...@daoine.org> wrote:
Hi there, > > If not, "nginx -V" should show the "configure arguments", which will > > show any --conf-path or --prefix that will indicate the default config > > file that nginx will use, if it is not the default-default. > > nginx version: nginx/1.16.1 (Ubuntu) > built with OpenSSL 1.1.1c 28 May 2019 > TLS SNI support enabled > configure arguments: --with-cc-opt='-g -O2 > --conf-path=/etc/nginx/nginx.conf --http-log-path=/var/log/nginx/access.log > --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock > This is the config file that I edited /etc/nginx/nginx.conf That looks correct to me, thanks. When you do the "reload", do you get anything new at the end of the error_log file, probably /var/log/nginx/error.log? If, for example, there is a config file error, then "reload" will not actually use the new file, and there should be something saying why. If that shows no problems, then something like nginx -T | grep 'server\|listen' should show the "server" blocks, "listen" directives, and "server_name" configurations that nginx will use. If you consider any of the information there private -- names, or public IP addresses, for example -- feel free to edit them; but please do so consistently, so that any patterns remain visible. That configuration fragment may make it possible to learn which server{} nginx uses to handle your test request. Cheers, f -- Francis Daly fran...@daoine.org _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx