Hello Everyone,
It appears when I get a DirectAdmin update it seems to break my Nginx for some reason.
I have tried rebuilding it but it keeps failing as it is binding to the wrong IP Address, any ideas how to resolve this. It's not the first time this has happened, I am using Apache and Nginx as a reverse proxy.
Thanks
Rockyuk
It appears when I get a DirectAdmin update it seems to break my Nginx for some reason.
Code:
May 26 23:56:58 Hostname systemd[1]: Starting The nginx HTTP and reverse proxy server...
May 26 23:57:02 Hostname nginx[159259]: nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" >
May 26 23:57:02 Hostname nginx[159259]: nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" >
May 26 23:57:02 Hostname nginx[159259]: nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
May 26 23:57:02 Hostname nginx[159259]: nginx: [emerg] bind() to Wrong IP:80 failed (99: Cannot assign requested a>
May 26 23:57:02 Hostname nginx[159259]: nginx: configuration file /etc/nginx/nginx.conf test failed
May 26 23:57:02 Hostname systemd[1]: nginx.service: Control process exited, code=exited status=1
May 26 23:57:02 Hostname systemd[1]: nginx.service: Failed with result 'exit-code'.
May 26 23:57:02 Hostname systemd[1]: Failed to start The nginx HTTP and reverse proxy server.
I have tried rebuilding it but it keeps failing as it is binding to the wrong IP Address, any ideas how to resolve this. It's not the first time this has happened, I am using Apache and Nginx as a reverse proxy.
Thanks
Rockyuk