1. Core Conventions

Before starting, please follow these conventions to avoid affecting system stability.

1.1 Files and Directories

1.2 Port Usage

All operations require root privileges.

If your application needs to use the default Web service ports (80/443), you must change the system Web service ports to other ports. Run the following commands to modify the default Web management interface ports:

sudo uci set web_server.http_port 8080
sudo uci set web_server.https_port 8443

sudo uci commit

2. Comparison of Two Methods

Choose the most suitable method based on your requirements.

Tip: HTTP (80) access is automatically redirected to HTTPS (443) by default, so Location Proxy only works under HTTPS.

3. Deployment Steps

3.1 Method 1: Adding a Standalone Port Service

Example: deploying a static website on port 8888.

1. Create Configuration File

# Write configuration to /etc/nginx/sites-available/my_static_site
sudo tee /etc/nginx/sites-available/my_static_site > /dev/null <<'EOF'
server {
    listen 8888;
    server_name _;

    root /var/www/my_static_site;
    index index.html;

    # Simplified logging and security headers
    access_log /var/log/nginx/my_static_site.log;
    error_log /var/log/nginx/my_static_site.error.log;
    add_header X-Frame-Options "SAMEORIGIN";

    location / {
        try_files $uri $uri/ =404;
    }
}
EOF

2. Create Web Files

sudo mkdir -p /var/www/my_static_site
echo "<h1>Hello from Port 8888</h1>" | sudo tee /var/www/my_static_site/index.html

3. Enable Service

# Create symlink to enable
sudo ln -s /etc/nginx/sites-available/my_static_site /etc/nginx/sites-enabled/

# Test configuration and reload
sudo nginx -t && sudo systemctl reload nginx

Access: http://:8888

3.2 Method 2: Adding a Location Proxy

Proxy all requests to https://device-IP/myapp/ to a local service running on port 5000.

1. Create Proxy Configuration

# Write configuration to /etc/nginx/server_common_conf/myapp_proxy.conf
sudo tee /etc/nginx/server_common_conf/myapp_proxy.conf > /dev/null <<'EOF'
location /myapp/ {
    proxy_pass http://127.0.0.1:5000/; # Note the trailing slash
    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;
}
EOF

2. Reload Nginx

sudo nginx -t && sudo systemctl reload nginx

Access: https:///myapp/ (Note: use HTTPS)

4. Diagnostics and Recovery

4.1 Quick Diagnostic Commands

4.2 Common Issues

4.3 Quick Recovery

If configuration causes Nginx to fail to start, follow these steps to restore to system default configuration.

sudo systemctl stop nginx
# Remove custom symlinks and proxy configurations
sudo rm -f /etc/nginx/sites-enabled/my_static_site
sudo rm -f /etc/nginx/server_common_conf/myapp_proxy.conf
# Re-link default service
sudo ln -s /etc/nginx/sites-available/rosp_web /etc/nginx/sites-enabled/
sudo nginx -t && sudo systemctl start nginx

5. Common Scenario Configurations

5.1 WebSocket Proxy

# ... above or below proxy_pass and other directives
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";

5.2 Proxy to Docker Container

Proxy to Grafana container (port 3000) and map to /monitoring/ path.

location /monitoring/ {
    # rewrite directive removes /monitoring/ prefix from URL
    rewrite ^/monitoring/(.*) /$1 break;
    proxy_pass http://127.0.0.1:3000;

    # ... other proxy_set_header directives ...
}

Note: Some applications (like Grafana) require their own root_url configuration to support subpath access.

5.3 Adding HTTP Basic Authentication

Protect path /admin/, requiring username and password for access.

1. Install Tools and Create Password

sudo apt-get update && sudo apt-get install -y apache2-utils
sudo htpasswd -c /etc/nginx/auth.htpasswd admin
# Enter password when prompted

2. Add Authentication in Location Configuration

location /admin/ {
    auth_basic "Restricted Area";
    auth_basic_user_file /etc/nginx/auth.htpasswd;

    # ... proxy_pass and other directives ...
}

Appendix

• Nginx Official Documentation: https://nginx.org/en/docs/

• Configuration File Naming: Recommend using descriptive names, such as monitoring_dashboard, rather than app1.

• File Permissions: Configuration files (.conf) recommended 644, Web directories recommended 755, Web files recommended 644.