Documentation
Quick start + feature guide for every section and device (continuously updated)
Website Management
This document explains the panel's "Website Management" — full lifecycle website management comparable to BaoTa/1Panel.
In a Nutshell
Create a website, configure its SSL certificate (HTTPS), URL rewrite, logs, password protection, and more — all within the panel — by remotely operating Nginx on the target server over SSH. No need to hand-write Nginx configuration files.
Overview
Website Management lets you handle a website's full configuration — creation, SSL certificates, URL rewrite, logs, password protection — within the panel, remotely operating Nginx on the target server over SSH.
Prerequisites
The target server must have Nginx installed.
Main Features
Website Creation
- Fill in the domain, port, and website root directory
- Automatically generates the Nginx site configuration
Reverse Proxy Websites
- When creating, choose "Reverse Proxy", fill in the domain, port, the proxy target address (e.g.
http://localhost:8080), and whether to enable WebSocket - Nginx forwards requests for that domain to the proxy target (commonly used for frontend/backend deployments, Docker containers, and applications running on a specific port)
- Website details → "Reverse Proxy Settings" can be edited at any time: proxy target address, port, WebSocket toggle, domain — Nginx reloads automatically after changes take effect
SSL Certificate (HTTPS)
- One-click issuance/renewal of free Let's Encrypt certificates
- Configure HTTPS with automatic redirect
- SSL email persistence: the email you first enter is saved, and subsequent certificate applications on the same server reuse it automatically — no need to re-enter
- Auto-renewal: the SSL page shows the "auto-renewal" status (whether the certbot timer is running). Certificates renew automatically before expiry, so no manual renewal every three months; if a server has it disabled, click "Enable auto-renewal" (a systemd timer / cron is created automatically)
URL Rewrite
- Configure URL rewrite rules for applications like WordPress, Typecho
Logs
- View access logs and error logs
Password Protection
- Add HTTP basic authentication to a website directory (username/password access)
Use Cases
- Deploying a production website with HTTPS
- Adding SSL or configuring URL rewrite for an existing website
- Troubleshooting website issues (reading logs)
How to Use
1. Go to the target server's "Website Management"
2. Click "Add Website" and fill in the domain and other details
3. After the website is created, continue configuring SSL, URL rewrite, and password protection
4. After modifying configuration, the panel reloads Nginx automatically to apply the changes
Glossary
- Nginx: the most widely used web server / reverse proxy software; the panel uses it to host websites.
- SSL certificate: enables HTTPS for a website (the browser address bar shows a padlock). Let's Encrypt provides free certificates.
- URL rewrite: rewrites "pretty URLs" (e.g.
/article/123) into a format the application can understand (e.g.?id=123). - Reverse proxy: forwards requests for a domain to another address (e.g. a local port).
- HTTP basic authentication: prompts for a username and password before accessing the website.
Notes
1. The domain must first resolve to the target server's public IP (DNS must take effect before applying for SSL).
2. Applying for a Let's Encrypt certificate requires port 80 to be publicly reachable (for HTTP validation).
3. The Website Management window supports maximize, drag, and free resize, making it easy to view long configurations.
4. If the target server has no public IP (NAT/Tunneling), SSL certificate application may be restricted and must be paired with port mapping.