Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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!
This comment has been deleted
I don’t think I understand it correctly. Trying to set thing up for a gaming system at 7sultans. Almost done, but having some troubles with Node.js. Actually, I did get it, thank to your guide but still… have no clue what that line means.
"This is a very basic configuration that listens on port 80 and serves files from the web root we just created. It will only respond to requests to the name provided after server_name, and any files ending in .php will be processed by the php-fpm process before Nginx sends the results to the user.
Save and close the file when you’re done customizing it."
Everything worked great until I got to this part. “Save and close the file…”
I was not able to do that. Save it or close it. I am looking through nginx info and even things like :x and :wq which may save it, but the console shows the same thing with a list of commands using up arrow and a letter. None of them said save and exit and when I tried any of them, they did nothing anyway… Save and close! It sounds SO easy!
Good tutorial, thanks.
There’s a typo in the symlink part. “.conf” shouldn’t be in the file name there, otherwise it will create a symlink to nowhere, as we didn’t use “.conf” in the original sites-available one.
Someone else mentioned it here, I am pretty sure you don’t need the .conf format in sites-enabled. I followed the tutorial and I could not get nginx to read the config file, so I just linked it with no .conf and it worked.
Hi, edit this line your_domain.conf to make it consistent throughout, because it creates confusion. Anyone copy-pasting it would have conflicts. Use your_domain placeholder all through.
sudo ln -s /etc/nginx/sites-available/your_domain.conf /etc/nginx/sites-enabled/