ÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐ

Geeks, please accept the hero post of 2021 Microsoft x Intel hacking contest>>>

nginx: [warn] conflicting server name “blog.xueyi.com” on 0.0.0.0:80, ignored

After modifying nginx configuration parameters, use nginx – t to check the configuration

After the prompt is successful, you can use nginx – s reload to reload the configuration

I encountered such a problem in the process of configuration, that is, after binding the host name, there will be a warning when reloading the configuration

one

nginx: [warn] conflicting server name

"localhost"

on

0.0.0.0:80, ignored

one

nginx: [warn] conflicting server name

"blog.jianghang.name"

on

0.0.0.0:80, ignored

The domain name blog.jianghang.name appears twice or even many times, resolving the same domain name to different directories. Generally, this error occurs when the configuration file is separated separately

Server name is bound repeatedly, but this warning will not affect the operation of the server. Moreover, this duplicate binding means that the nginx service running now and the new configuration to be loaded are duplicated. Therefore, this warning is unnecessary

Query which files contain blog. Jianghang. Name fields. Use the grep command. An example of this command is as follows:

one

sudo grep -r blog.jianghang.name /etc/nginx/conf.d/

Similar Posts: