Back to articles
DevOps & Systems

Host React Next.js SSR Applications on VPS: Ultimate Performance Optimization Guide

Deploying React Next.js SSR applications on a VPS requires careful system configuration to achieve maximum performance, reduce response times, and optimize resource usage. This...

DPTCloud Engineering5 min read
Host React Next.js SSR Applications on VPS: Ultimate Performance Optimization Guide

Deploying React Next.js SSR applications on a VPS requires careful system configuration to achieve maximum performance, reduce response times, and optimize resource usage. This guide provides a detailed, step-by-step process from initial setup to advanced performance tuning, including Nginx configuration, PM2 process management, Gzip compression, JavaScript/CSS optimization, and effective caching strategies. The steps are clearly explained with practical examples, making it suitable for both development and production environments.

1. Prepare the VPS Environment

To host a React Next.js SSR application, you need a VPS with sufficient resources. Use NVMe Cloud VPS with at least 2GB RAM and 1 CPU core to ensure smooth application performance. Choose Ubuntu 22.04 or Debian 11 as the operating system, as they support all necessary tools.

First, update the system:

sudo apt update && sudo apt upgrade -y

Then install Node.js and npm. Use NodeSource to install the latest LTS version:

curl -sL https://deb.nodesource.com/setup_lts.x | sudo -E bash -&& sudo apt install -y nodejs

Verify that Node.js and npm are installed correctly:

node --version&& npm --version

2. Install and Optimize the Next.js SSR Application

Initialize a Next.js application if you haven't already:

npx create-next-app@latest my-app --typescript --tailwind --eslint&& cd my-app

To optimize SSR performance, configure the `next.config.js` file:

module.exports = {&& reactStrictMode: true,&& swcMinify: true,&& experimental: {&& serverComponents: true,&& serverActions: true,&& },&& images: {&& domains: ['localhost'],&& },&& webpack: (config, { isServer }) => {&& if (!isServer) {&& config.resolve.fallback = { fs: false };&& }&& return config;&& },&& };

Set up the production environment by creating a `.env.production` file:

NEXT_PUBLIC_API_URL=https://api.yourdomain.com&& NODE_ENV=production

Run the build command to create the production build:

npm run build

3. Configure Nginx and Reverse Proxy

Nginx is an efficient web server for handling HTTP requests and distributing load for Next.js applications. Install Nginx:

sudo apt install nginx -y

Create a new configuration file in `/etc/nginx/sites-available/`:

sudo nano /etc/nginx/sites-available/my-app

Add the following content:

server {&& listen 80;&& server_name your-domain.com;&& && location / {&& proxy_pass http://localhost:3000;&& proxy_http_version 1.1;&& proxy_set_header Upgrade $http_upgrade;&& proxy_set_header Connection 'upgrade';&& proxy_set_header Host $host;&& proxy_set_header X-Real-IP $remote_addr;&& proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;&& proxy_set_header X-Forwarded-Proto $scheme;&& proxy_cache_bypass $http_upgrade;&& }&& && location /api {&& proxy_pass http://localhost:3000;&& proxy_set_header Host $host;&& proxy_set_header X-Real-IP $remote_addr;&& }&& }

Link the configuration file to the `sites-enabled` directory:

sudo ln -s /etc/nginx/sites-available/my-app /etc/nginx/sites-enabled/

Restart Nginx:

sudo systemctl restart nginx

4. Optimize Performance with PM2 and Gzip

Use PM2 to manage the Node.js application, ensuring automatic startup and preventing interruptions:

npm install -g pm2&& pm2 start npm -- start

To enable Gzip for CSS, JavaScript, and HTML files, modify the `next.config.js` file:

module.exports = {&& // ... previous config&& compress: true,&& };

Additionally, configure Nginx to support Gzip:

gzip on;&& gzip_vary on;&& gzip_proxied any;&& gzip_comp_level 6;&& gzip_types text/plain text/css text/xml application/json application/javascript application/xml+rss application/atom+xml;

5. Optimize Cache and Images

To reduce server load, set up caching for static files. In `next.config.js`, add:

module.exports = {&& // ... previous config&& images: {&& domains: ['your-domain.com'],&& loader: 'custom',&& loaderFile: './my-image-loader.js',&& },&& experimental: {&& images: {&& loader: 'custom',&& loaderFile: './my-image-loader.js',&& },&& },&& };

For images, use an external storage service like Cloudinary or self-host with Nginx to manage caching effectively. Create a `.htaccess` file or configure Nginx to set long-term caching:

location ~* \.(jpg|jpeg|png|gif|ico|css|js)$ {&& expires 1y;&& add_header Cache-Control "public, immutable";&& }

6. Test and Verify

After completing the configuration, test the application using the command:

curl -I http://your-domain.com

Ensure the HTTP response is 200 OK. Use tools like Google PageSpeed Insights or WebPageTest to measure load times and optimize further if needed.

7. Troubleshoot and Debug

If the application fails to start, check the logs using:

pm2 logs

If Nginx reports a 502 error, verify that the Next.js application is running. Check port 3000 with:

netstat -tuln | grep 3000

If it's not found, restart the application:

pm2 restart my-app

In case of image errors, verify the `next.config.js` file and ensure the domains are allowed in `images.domains`.

Reference

For more information on Next.js SSR and performance optimization, refer to the official documentation at Next.js Documentation.

Performance Optimization Checklist

Component Condition Optimal Value
RAM Minimum 2GB
CPU Minimum 1 Core
Node.js Version Latest LTS
Web Server Proxy Nginx
Process Manager Tool PM2
Compression Enable Gzip
Image Optimization Loader Custom (via next.config.js)
Cache Static Files Expires 1 year

References

For more information on Next.js SSR and performance optimization, refer to the official documentation at Next.js Documentation.

Related infrastructure & engineering guides: Self-Hosting a Private PDF Conversion Service for Enterprise Offices Using Gotenberg and Docker VPS

DPTCloud Tier III Infrastructure

Recommended NVMe Cloud VPS Plans to Deploy This Setup

Enterprise RAID 10 NVMe SSDs, CMC & FPT District 9 uplinks with Anycast Anti-DDoS and 99.99% SLA.

View 22 VPS Plans
ECO · vn-02

VPS-2E

94.600 ₫ / mo

10% VAT included

  • CPU: 2 vCPU
  • RAM: 2 GB
  • SSD: 30 GB NVMe
ECO · vn-02Recommended

VPS-3E

170.500 ₫ / mo

10% VAT included

  • CPU: 2 vCPU
  • RAM: 4 GB
  • SSD: 50 GB NVMe
BASIC · vn-01Recommended

VPS-05

457.600 ₫ / mo

10% VAT included

  • CPU: 4 vCPU
  • RAM: 8 GB
  • SSD: 50 GB NVMe

Related Articles

View all
ZaloZalo SupportDiscord0384 753 478