Failed to start nginx - high performance web server

failed to start the nginx http and reverse proxy server.
see "systemctl status nginx.service" and "journalctl -xe" for details
nginx: configuration file /etc/nginx/nginx.conf test failed
nginx.service is not active, cannot reload.
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: address already in use)
restart nginx ubuntu
failed to start nginx.service: unit nginx.service is masked.
nginx the control process exited with error code

I am trying to install Yii and use Nginx service to run my web application. When i try to do

sudo systemctl restart nginx.service, i have an error..

Then i try to see the status and i get this..

i found somewhere that i need to run nginx -t -c /etc/nginx/nginx.conf to see what is causing the error.. but everything is ok. it says, syntax is ok and test is successful.

what seems to be the problem with this.. please help.

Run ls -l /usr/share/nginx/ This is where it is looking to save the access logs, check the directory exists and that the user you are running nginx as has write access here.

Can't start Nginx, myusername@droplet1:~$ sudo service nginx restart Job for nginx.service - A high performance web server and a reverse proxy server Feb 20 16:17:49 django-s-1vcpu-1gb-lon1-01 nginx[1439]: nginx: [emerg] "location" directive is not allowed here in /etc/nginx/nginx.conf:87 Feb 20 16:17:49 django-s-1vcpu-1gb-lon1-01 nginx[1439]: nginx: configuration file /etc/nginx/nginx.conf test failed Feb 20 16:17:49 django-s-1vcpu-1gb-lon1-01 systemd[1]: nginx.service: Control process

It seems 80 port is in use, just have a checked, like

sudo netstat -lnp | grep 0.0.0.0:80

Nginx "Failed to start A high performance web server and a reverse , There was just 2 sites that uses same ports, I just deleted one of them. Re: nginx issue: Failed to start nginx - high performance we Post by ramasilveyra » Mon Oct 06, 2014 12:26 am I thought it's a clean install of CentOs, and how to check what web server it's running?

You probably have a process bound to the HTTP port 80 (maybe apache2). You can run command

sudo lsof -i:80 

to get a list of processes using the port and then stop/disable web server.

Nginx: the High-Performance Web Server and Reverse Proxy, Nginx, pronounced “Engine X”, is a high-performance Web server and reverse proxy. Now that Nginx is installed, you can use the startup script to start, requests to a failed back-end server until it starts responding again. Failed to start A high performance web server and a reverse proxy server nginx.service - A high performance web server and a A high performance web server and

Nginx: Failed to start A high performance web server , service - A high performance web server and a reverse proxy server Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset:  Debian 8.4 (Jessie ) Nginx 1.6.2-5+deb8u1 (standard package) I have 4 units running Nginx in different OS versions either on debian 8.0, 8.4 or Ubuntu 14.04. Since yesterday NGINX startup fails on

nginx issue: Failed to start nginx - high performance web se, service - nginx - high performance web server Loaded: loaded (/usr/lib/systemd/​system/nginx.service; disabled) Active: failed (Result: exit-code)  That Web server exists, and it's called Nginx. Nginx, pronounced “Engine X”, is a high-performance Web server and reverse proxy. It was created by Igor Sysoev for www.rambler.ru, Russia's second-largest Web site. Rambler has used Nginx since summer 2004, and it's currently serving about 500 million requests per day.

Nginx won't start [FAILED] Failed to start A high performance, I would start by taking a look at the command suggested in the failed message. The output of that command should offer you some guidance on  Failed to start nginx - high performance web server. Hey guys need some help fixing my nginx web server. It was working fine until I rebooted and now nginx won't start at boot.

Comments
  • Hi, I am also facing this issue on my server. Were you able to solve this?
  • hi Luke. Thanks for your reply. When i run the command, i have access.log and error.log file and html which is a directory. what do you mean by has write access here?
  • This comes down to unix file permissions, your user 'root' needs the ability to write to the log files, check that you didn't create them as another user first, or that the directory itself you have the write permissions to. ls -la /usr/share/nginx . Check out, tutorialspoint.com/unix/unix-file-permission.htm If you include the output of that command it might help understanding your setup.