mirror of
https://github.com/acepanel/acepanel.github.io.git
synced 2026-02-04 11:27:14 +08:00
feat: 添加中文翻译
This commit is contained in:
@@ -30,10 +30,7 @@ const members = [
|
||||
|
||||
# About
|
||||
|
||||
## About RatPanel
|
||||
|
||||
RatPanel is a professional server operation and maintenance management panel dedicated to providing users with simple,
|
||||
efficient, and secure server management solutions.
|
||||
RatPanel is a professional server operation and maintenance management panel dedicated to providing users with simple, efficient, and secure server management solutions.
|
||||
|
||||
| Vision | Mission | Values |
|
||||
|----------------------------------------------------------|---------------------------------------------|---------------------------------------------------|
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
|
||||
## Overview
|
||||
|
||||
RatPanel provides a secure RESTful interface for interacting with the panel system. All API requests require HMAC-SHA256
|
||||
signature authentication to ensure the security and integrity of communications.
|
||||
RatPanel provides a secure RESTful interface for interacting with the panel system. All API requests require HMAC-SHA256 signature authentication to ensure the security and integrity of communications.
|
||||
|
||||
## Basic Information
|
||||
|
||||
@@ -13,8 +12,7 @@ signature authentication to ensure the security and integrity of communications.
|
||||
|
||||
## Authentication Mechanism
|
||||
|
||||
The API uses the HMAC-SHA256 signature algorithm for authentication. Each request must include the following HTTP
|
||||
headers:
|
||||
The API uses the HMAC-SHA256 signature algorithm for authentication. Each request must include the following HTTP headers:
|
||||
|
||||
| Header Name | Description |
|
||||
|-----------------|------------------------------------------------------------------------------------------|
|
||||
@@ -652,8 +650,7 @@ sendApiRequest();
|
||||
If you encounter signature verification failures, check:
|
||||
|
||||
- Ensure you are using the correct API token and ID
|
||||
- Check that the client and server times are accurate; timestamp differences greater than 300 seconds will cause
|
||||
verification to fail
|
||||
- Check that the client and server times are accurate; timestamp differences greater than 300 seconds will cause verification to fail
|
||||
- Ensure the request body hasn't been modified before or after signature calculation
|
||||
- Ensure the URL path is handled correctly; remember to remove the entry prefix when normalizing the path
|
||||
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
# Configure Container Image Acceleration
|
||||
|
||||
Due to certain reasons, domestic users in China may be unable to connect to Docker Hub to pull container images, thus
|
||||
requiring image acceleration configuration.
|
||||
Due to certain reasons, domestic users in China may be unable to connect to Docker Hub to pull container images, thus requiring image acceleration configuration.
|
||||
|
||||
## For Podman
|
||||
|
||||
@@ -16,8 +15,7 @@ location = "docker.io"
|
||||
location = "docker.1ms.run"
|
||||
```
|
||||
|
||||
Where docker.1ms.run is the configured image acceleration address. You can refer to other tutorials to set up and use
|
||||
it.
|
||||
Where docker.1ms.run is the configured image acceleration address. You can refer to other tutorials to set up and use it.
|
||||
|
||||
## For Docker
|
||||
|
||||
@@ -31,5 +29,4 @@ Add the following configuration and save:
|
||||
}
|
||||
```
|
||||
|
||||
Where https://docker.1ms.run is the configured image acceleration address. You can refer to other tutorials to set up
|
||||
and use it.
|
||||
Where https://docker.1ms.run is the configured image acceleration address. You can refer to other tutorials to set up and use it.
|
||||
|
||||
@@ -1,7 +1,5 @@
|
||||
# Configure Reverse Proxy
|
||||
|
||||
RatPanel v2.4.10+ comes with a built-in reverse proxy configuration generator, which you can access through the top
|
||||
right corner of the site rewrite configuration page.
|
||||
RatPanel v2.4.10+ comes with a built-in reverse proxy configuration generator, which you can access through the top right corner of the site rewrite configuration page.
|
||||
|
||||
Note: If you encounter issues with static resources like CSS/JS not loading properly after setting up a reverse proxy,
|
||||
please remove the **Do not log static files** section from the site's main configuration file.
|
||||
Note: If you encounter issues with static resources like CSS/JS not loading properly after setting up a reverse proxy, please remove the **Do not log static files** section from the site's main configuration file.
|
||||
|
||||
@@ -1,17 +1,15 @@
|
||||
# Configure QUIC (HTTP3)
|
||||
|
||||
RatPanel currently supports automatic QUIC configuration, but for compatibility reasons, the `Alt-Svc` header is not
|
||||
added by default. Browsers will not attempt to use QUIC connections without detecting the `Alt-Svc` header.
|
||||
RatPanel currently supports automatic QUIC configuration, but for compatibility reasons, the `Alt-Svc` header is not added by default. Browsers will not attempt to use QUIC connections without detecting the `Alt-Svc` header.
|
||||
|
||||
If you are not using a CDN, you can add the configuration below to your website's rewrite rules to let browsers know
|
||||
that the website supports and uses QUIC connections.
|
||||
If you are not using a CDN, you can add the configuration below to your website's rewrite rules to let browsers know that the website supports and uses QUIC connections.
|
||||
|
||||
```
|
||||
add_header Alt-Svc 'h3=":$server_port"; ma=2592000';
|
||||
```
|
||||
|
||||
If you are using a CDN or there are proxy servers in front, then QUIC needs to be enabled on the CDN / frontend.
|
||||
|
||||
If the configuration still doesn't work, please check your browser version and the availability of UDP port 443.
|
||||
|
||||
* According to Nginx's git commit history, all QUIC draft versions have been removed in version 1.25, so there's no need
|
||||
to add draft version numbers to `Alt-Svc`.
|
||||
* According to Nginx's git commit history, all QUIC draft versions have been removed in version 1.25, so there's no need to add draft version numbers to `Alt-Svc`.
|
||||
|
||||
@@ -4,15 +4,11 @@ With the following security measures, almost all hacking/malware issues can be p
|
||||
|
||||
### Website Aspects
|
||||
|
||||
Based on past experience, most hacking and malware incidents are caused by program vulnerabilities, unrelated to the
|
||||
Panel or environment. For website security, you should:
|
||||
Based on experience, most hacking and malware incidents are caused by program vulnerabilities, unrelated to the Panel or environment. For website security, you should:
|
||||
|
||||
1. Avoid using pirated programs or software, especially when you cannot determine if they have been tampered with.
|
||||
2. Regularly update website programs and software environments; don't use outdated software due to inconvenience, as
|
||||
their security cannot be guaranteed.
|
||||
3. Never use weak passwords for website admin areas. Passwords are strongly recommended to be generated using a random
|
||||
generator with more than 20 mixed characters and stored in a secure location. If possible, enable multi-factor
|
||||
authentication (2FA) for your programs.
|
||||
2. Regularly update website programs and software environments; don't use outdated software due to inconvenience, as their security cannot be guaranteed.
|
||||
3. Never use weak passwords for website admin areas. Passwords are strongly recommended to be generated using a random generator with more than 20 mixed characters and stored in a secure location. If possible, enable 2FA for your programs.
|
||||
4. Set up scheduled backups of all site data; don't operate without backups.
|
||||
5. PHP has disabled some high-risk functions by default; don't remove these restrictions unless absolutely necessary.
|
||||
|
||||
@@ -21,25 +17,16 @@ Panel or environment. For website security, you should:
|
||||
The probability of serious security vulnerabilities in modern systems is low, but you should still:
|
||||
|
||||
1. Regularly update system software. (Use `yum update` or `apt upgrade`).
|
||||
2. Prohibit weak passwords and the default port 22 for SSH. Passwords are strongly recommended to be generated using a
|
||||
random generator with more than 20 mixed characters and stored in a secure location. If possible, consider installing
|
||||
Fail2ban for targeted protection.
|
||||
3. Don't arbitrarily assign 777 permissions or execution permissions to the www user, as this may cause major security
|
||||
risks.
|
||||
2. Prohibit weak passwords and the default port 22 for SSH. Passwords are strongly recommended to be generated using a random generator with more than 20 mixed characters and stored in a secure location. If possible, consider installing Fail2ban for targeted protection.
|
||||
3. Don't arbitrarily assign 777 permissions or execution permissions to the www user, as this may cause major security risks.
|
||||
4. If your service provider offers VNC server management, consider disabling SSH to solve the problem at the source.
|
||||
|
||||
### Panel Aspects
|
||||
|
||||
RatPanel has the same privileges as root, and improper management can cause serious security problems. You should:
|
||||
|
||||
1. Regularly update the Panel and applications installed through it. We recommend following our channel or group to
|
||||
receive various update messages promptly.
|
||||
2. Prohibit weak passwords and the default 8888 port for the Panel. Passwords are strongly recommended to be generated
|
||||
using a random generator with more than 20 mixed characters and stored in a secure location.
|
||||
3. Consider modifying the Panel entry point and enabling HTTPS for the Panel to prevent scanner detection and
|
||||
man-in-the-middle attacks.
|
||||
4. Unless necessary, do not allow firewall access to internal service ports (Redis 6379, MySQL 3306, PostgreSQL 5432,
|
||||
etc.), as this may cause serious security risks. (Local website connections don't require firewall access; connection
|
||||
issues are program problems).
|
||||
5. For high-security requirements, consider stopping the Panel operation routinely and starting it only when needed (
|
||||
stopping the Panel will not affect websites, scheduled tasks, etc.).
|
||||
1. Regularly update the Panel and applications installed through it. We recommend following our channel or group to receive various update messages promptly.
|
||||
2. Prohibit weak passwords and the default 8888 port for the Panel. Passwords are strongly recommended to be generated using a random generator with more than 20 mixed characters and stored in a secure location.
|
||||
3. Consider modifying the Panel entry point and enabling HTTPS for the Panel to prevent scanner detection and man-in-the-middle attacks.
|
||||
4. Unless necessary, do not allow firewall access to internal service ports (Redis 6379, MySQL 3306, PostgreSQL 5432, etc.), as this may cause serious security risks. (Local website connections don't require firewall access; connection issues are program problems).
|
||||
5. For high-security requirements, consider stopping the Panel operation routinely and starting it only when needed (stopping the Panel will not affect websites, scheduled tasks, etc.).
|
||||
|
||||
@@ -1,6 +1,5 @@
|
||||
# Configure Process Monitoring
|
||||
|
||||
1. Install Supervisor manager and open it.
|
||||
2. Create processes that need to be monitored in the Supervisor manager (it's not recommended to use root as the running
|
||||
user).
|
||||
2. Create processes that need to be monitored in the Supervisor manager (it's not recommended to use root as the running user).
|
||||
3. Common issues: [https://tom.moe/t/supervisor/3112](https://tom.moe/t/supervisor/3112)
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
# Configure TLSv1.1 TLSv1
|
||||
|
||||
The current Panel OpenResty is compiled with OpenSSL 3.5, which by default disables the deprecated TLSv1.1 and TLSv1
|
||||
protocols.
|
||||
The current Panel OpenResty is compiled with OpenSSL 3.5, which by default disables the deprecated TLSv1.1 and TLSv1 protocols.
|
||||
|
||||
Of course, if your business must use these two protocols, you can enable them using the SSL configuration below.
|
||||
|
||||
@@ -9,4 +8,4 @@ Of course, if your business must use these two protocols, you can enable them us
|
||||
ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;
|
||||
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA256:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:@SECLEVEL=0;
|
||||
ssl_prefer_server_ciphers on;
|
||||
```
|
||||
```
|
||||
|
||||
@@ -6,11 +6,9 @@ next: false
|
||||
|
||||
# Certificates
|
||||
|
||||
If the 3-month free certificate cannot meet your needs, you can choose to purchase higher-level certificates. We offer
|
||||
DV single-domain certificates and DV wildcard certificates for your selection.
|
||||
If the 3-month free certificate cannot meet your needs, you can choose to purchase higher-level certificates. We offer DV single-domain certificates and DV wildcard certificates for your selection.
|
||||
|
||||
Due to pricing policy restrictions, please contact our sales team directly through the group link in the upper right
|
||||
corner for specific prices and purchases.
|
||||
Due to pricing policy restrictions, please contact our sales team directly through the group link in the upper right corner for specific prices and purchases.
|
||||
|
||||
<style>
|
||||
.cert-cards-container {
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
---
|
||||
# https://vitepress.dev/reference/default-theme-home-page
|
||||
layout: home
|
||||
|
||||
hero:
|
||||
@@ -13,10 +12,7 @@ hero:
|
||||
target: _blank
|
||||
- theme: alt
|
||||
text: Quick install
|
||||
link: /install
|
||||
- theme: alt
|
||||
text: Browse docs
|
||||
link: /docs
|
||||
link: /quickstart/install
|
||||
|
||||
features:
|
||||
- icon: ✨
|
||||
|
||||
@@ -2,11 +2,9 @@
|
||||
|
||||
Before starting, you need to install the Docker / Podman container engine.
|
||||
|
||||
After the container engine is installed, you can go to the Panel's container management section to create containers (
|
||||
pgadmin4 is used as an example here).
|
||||
After the container engine is installed, you can go to the Panel's container management section to create containers (pgadmin4 is used as an example here).
|
||||
|
||||
First, navigate to the Images tab to pull the required images. This may take several minutes to tens of minutes
|
||||
depending on your network environment.
|
||||
First, navigate to the Images tab to pull the required images. This may take several minutes to tens of minutes depending on your network environment.
|
||||
|
||||

|
||||
|
||||
@@ -14,15 +12,14 @@ After the image is pulled, navigate to the Containers tab to start creating a co
|
||||
|
||||

|
||||
|
||||
Fill in the form according to the container's instructions. The pgadmin4 image used here needs to map port 80 and
|
||||
configure 2 default environment variables, with no need to map directories.
|
||||
Fill in the form according to the container's instructions. The pgadmin4 image used here needs to map port 80 and configure 2 default environment variables, with no need to map directories.
|
||||
|
||||
After the container is created, you can click the refresh button in the upper right corner and the log button on the
|
||||
right side of the container to check if it has started properly.
|
||||
After the container is created, you can click the refresh button in the upper right corner and the log button on the right side of the container to check if it has started properly.
|
||||
|
||||

|
||||
|
||||
If the container fails to start, please make corrections according to the logs.
|
||||
|
||||
If you have mapped external ports, you need to go to the firewall menu to allow the corresponding ports.
|
||||
|
||||

|
||||
|
||||
@@ -1,11 +1,9 @@
|
||||
# Mount Partitions
|
||||
|
||||
If your server has unmounted data disks, you can log in as `root` user before installation and run the following command
|
||||
to automatically mount them. Cross-directory migration is not supported after Panel installation.
|
||||
If your server has unmounted data disks, you can log in as `root` user before installation and run the following command to automatically mount them. Cross-directory migration is not supported after Panel installation.
|
||||
|
||||
```shell
|
||||
curl -fsLm 10 -o auto_mount.sh https://dl.cdn.haozi.net/panel/auto_mount.sh && bash auto_mount.sh
|
||||
```
|
||||
|
||||
You can also contact your server provider via ticket to request assistance with mounting partitions, or mount the
|
||||
partitions yourself before installing the Panel.
|
||||
You can also contact your server provider via ticket to request assistance with mounting partitions, or mount the partitions yourself before installing the Panel.
|
||||
|
||||
@@ -1,13 +1,10 @@
|
||||
# Install Panel
|
||||
|
||||
The Panel supports mainstream systems under `amd64` | `arm64` architectures. LNMP environment installation has been
|
||||
tested on all systems listed in the table below.
|
||||
The Panel supports mainstream systems under `amd64` | `arm64` architectures. LNMP environment installation has been tested on all systems listed in the table below.
|
||||
|
||||
It is recommended to use systems marked as **recommended**. Unless there are special circumstances, it is not
|
||||
recommended to use systems marked as **not recommended**.
|
||||
It is recommended to use systems marked as **recommended**. Unless there are special circumstances, it is not recommended to use systems marked as **not recommended**.
|
||||
|
||||
For systems not listed in the table below, you can try installing on your own, but no free technical support will be
|
||||
provided.
|
||||
For systems not listed in the table below, you can try installing on your own, but no free technical support will be provided.
|
||||
|
||||
| System | Version | Note |
|
||||
|---------------------|---------|-----------------|
|
||||
@@ -28,8 +25,7 @@ provided.
|
||||
| Anolis | 8 | Not Recommended |
|
||||
| openEuler | 22 | Not Recommended |
|
||||
|
||||
As system versions continue to update, we may also terminate support for some overly outdated systems to ensure the
|
||||
robustness of the Panel.
|
||||
As system versions continue to update, we may also terminate support for some overly outdated systems to ensure the robustness of the Panel.
|
||||
|
||||
## Start Installation
|
||||
|
||||
|
||||
@@ -18,12 +18,10 @@ Follow the prompts to complete the necessary commands for operation.
|
||||
|
||||
It is primarily recommended to back up data and reinstall the system, as this ensures a clean system.
|
||||
|
||||
If you are unable to reinstall the system, please log in to the server as `root` user and execute the following command
|
||||
to uninstall the Panel:
|
||||
If you are unable to reinstall the system, please log in to the server as `root` user and execute the following command to uninstall the Panel:
|
||||
|
||||
```shell
|
||||
curl -fsLm 10 -o uninstall.sh https://dl.cdn.haozi.net/panel/uninstall.sh && bash uninstall.sh
|
||||
```
|
||||
|
||||
Before uninstalling the Panel, be sure to back up all data and uninstall all Panel applications in advance. Data will be
|
||||
**unrecoverable** after uninstallation!
|
||||
Before uninstalling the Panel, be sure to back up all data and uninstall all Panel applications in advance. Data will be **unrecoverable** after uninstallation!
|
||||
|
||||
@@ -14,8 +14,7 @@ We provide a free forum service where you can ask questions, discuss, and share
|
||||
|
||||
## Paid Remote Service
|
||||
|
||||
Website errors, slow speed, malware infections? High server resource usage, configuration optimization, intrusion
|
||||
tracing? We provide all these services in one place.
|
||||
Website errors, slow speed, malware infections? High server resource usage, configuration optimization, intrusion tracing? We provide all these services in one place.
|
||||
|
||||
### Remote Service Price List
|
||||
|
||||
|
||||
Reference in New Issue
Block a user