Question

Problem with running nginx web server with Ubuntu

I am having trouble running nginx webserver with Unbuntu 16.04

Following this tutorial https://www.digitalocean.com/community/tutorials/how-to-troubleshoot-common-site-issues-on-a-linux-server

Running - sudo apt-get update

I get - Hit:1 https://repos.sonar.digitalocean.com/apt main InRelease Ign:2 https://download.serverpilot.io/ubuntu xenial InRelease Hit:3 https://download.serverpilot.io/ubuntu xenial Release Reading package lists… Done

Then running - sudo apt-get install nginx

I get - Note, selecting ‘sp-nginx’ instead of ‘nginx’ sp-nginx is already the newest version (1.15.2-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Then running - sudo netstat -plunt | grep nginx

I get - tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 15003/nginx
tcp6 0 0 :::80 :::* LISTEN 15003/nginx

Then - sudo service nginx start

sudo: start: command not found

Please can someone help!


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hello friend!

Standard documentation will actually not work completely with a server that has been configured by ServerPilot. Their software configures things in a more unique way. They do keep great documentation though: https://serverpilot.io/docs/

Specifically I think this will help: https://serverpilot.io/docs/how-to-restart-services

With that in mind, try: service nginx-sp restart

Though that might not resolve the underlying problem that led to this moment.

Kind Regards, Jarland