Bashed

Well-Known Member
Dec 18, 2013
146
4
68
cPanel Access Level
Root Administrator
Just installed nginx using the nginxcp plugin. Swift, but one question and concern.

This is how it ended on multiple boxes. Is this normal?

Code:
 ****************************************************
*               Installation Complete              *
*run /etc/init.d/httpd restart to start Nginx Admin*
****************************************************
[email protected] [/usr/local/src/publicnginx]# service httpd restart
Restarting nginx daemon: nginxRemaining processes: 7823
nginx: [warn] conflicting server name "123.123.22.5" on 123.123.22.5:80, ignored
nginx: [warn] conflicting server name "123.123.22.5" on 123.123.22.5:80, ignored
nginx: [warn] conflicting server name "123.123.22.5" on 123.123.22.5:80, ignored
nginx: [warn] conflicting server name "123.123.22.5" on 123.123.22.5:80, ignored
nginx: [warn] conflicting server name "123.123.22.5" on 123.123.22.5:80, ignored
nginx: [warn] conflicting server name "123.123.22.5" on 123.123.22.5:80, ignored
nginx: [warn] conflicting server name "123.123.22.5" on 123.123.22.5:80, ignored
nginx: [warn] conflicting server name "123.123.22.5" on 123.123.22.5:80, ignored
nginx: [warn] conflicting server name "123.123.22.4" on 123.123.22.4:80, ignored
nginx: [warn] conflicting server name "123.123.22.5" on [::]:80, ignored
nginx: [warn] conflicting server name "123.123.22.5" on [::]:80, ignored
nginx: [warn] conflicting server name "123.123.22.5" on [::]:80, ignored
nginx: [warn] conflicting server name "123.123.22.5" on [::]:80, ignored
nginx: [warn] conflicting server name "123.123.22.5" on [::]:80, ignored
nginx: [warn] conflicting server name "123.123.22.5" on [::]:80, ignored
nginx: [warn] conflicting server name "123.123.22.4" on [::]:80, ignored
nginx: [warn] conflicting server name "123.123.22.5" on [::]:80, ignored
nginx: [warn] conflicting server name "123.123.22.5" on [::]:80, ignored
.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,909
2,229
463
Hello,

I suggest reporting this issue to the developer or support team for that plugin, as it's not something that's developed by cPanel/WHM.

Thank you.