NGINX is an open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers.
Package | Version | License |
---|---|---|
nginx | 1.23.3 | BSD-2-Clause |
Click the Deploy to DigitalOcean button to create a Droplet based on this 1-Click App. If you aren’t logged in, this link will prompt you to log in with your DigitalOcean account.
In addition to creating a Droplet from the NGINX 1-Click App using the control panel, you can also use the DigitalOcean API. As an example, to create a 4GB NGINX Droplet in the SFO2 region, you can use the following curl
command. You need to either save your API access token) to an environment variable or substitute it in the command below.
If you’ve setup an SSH key while launching the Droplet, use ssh -i <ssh_key> <user>@<your_droplet_public_ipv4>
.
Otherwise, if you’ve setup a user and password, use ssh <user>@<your_droplet_public_ipv4>
to log into the instance.
Before you start tweaking NGINX, make sure it is indeed present and working. Run curl <your_droplet_public_ipv4>
or open the IP address on your web browser of choice. If NGINX is running, you should be greeted with the default “Welcome to nginx!” landing page.
Detailing how to configure NGINX would take more space than what’s available here. As such, we recommend you check our Beginner’s Guide and our full module reference documentation available at https://nginx.org/en/docs/.
In addition to installing NGINX, this 1-Click also enables the UFW firewall to allow only SSH (port 22, rate limited), HTTP (port 80), and HTTPS (port 443) access. We recommend you tweak your environment to further restrict SSH access to the droplet.
Have a question about how to use NGINX? Want to chat with like minded fellows? Join our NGINX community Slack!
Alternatively, feel free to reach out to the NGINX team using the NGINX mailing list!