KJZH001/nezhahq.github.io
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

补充内网穿透说明 (#102)

Browse Source
This commit is contained in:
UUBulb
2024-10-14 10:55:57 +02:00
committed by GitHub
parent 16c26f62d4
commit 54ff2467eb
4 changed files with 9 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en_US/guide/nat.md
+3 -3
View File
@@ -3,7 +3,7 @@ outline: deep
---
# NAT Traversal Configuration
Nezha Server Monitoring includes built-in NAT traversal capabilities, allowing users to expose internal services running on an Agent (such as home OpenWrt routers or NAS devices) to the public internet. This functionality facilitates remote access and is currently limited to supporting HTTP protocol traversal.
Nezha Server Monitoring includes built-in NAT traversal capabilities, allowing users to expose internal services running on an Agent (such as home OpenWrt routers or NAS devices) to the public internet. This functionality facilitates remote access and is currently limited to supporting plain HTTP traversal.
## Preparation
@@ -23,8 +23,8 @@ If your Dashboard server uses tools like the aaPanel or similar management platf
2. Click the "Add" button and provide the following required details:
- **Name**: Assign a custom name to this traversal setup, for example, `OpenWrt Login Page`.
- **Agent ID**: Input the ID of the Agent for which traversal is needed.
- **Internal Service Address**: Specify the internal service address that requires traversal, in the `IP:port` format, such as `127.0.0.1:80`.
- **Domain Name**: Enter the previously configured public domain name, like `service-1.example.com`.
- **Local service**: Specify the internal service address that requires traversal, in the `IP:port` format, such as `127.0.0.1:80`.
- **Bind hostname**: Enter the previously configured public domain name, such as `service-1.example.com`. If a non-standard port is used by Dashboard (e.g. default `8008`), be sure to include it as well.
3. After filling in the details, click the "Add" button and wait for the traversal setup to activate.
4. Test the configuration by accessing `http://service-1.example.com` to ensure the internal service on the Agent is successfully accessible.
docs/en_US/guide/servers.md
+2 -1
View File
@@ -41,11 +41,12 @@ It is available for both Linux and Windows and supports Ctrl+Shift+V for pasting
If the connection fails, refer to [Real-Time Channel Disconnection/Online Terminal Connection Failure](/en_US/guide/q4.html).
## FM
Added in Dashboard v0.19.1 / Agent v0.19.0. A pseudo file manager embedded in WebShell, supports file download/upload, directory navigation and copying current path. Access it by clicking the blue button in the bottom-right corner of the WebShell.
## DDNS Functionality
The DDNS functionality is suitable for servers with dynamic IPs. When the Agent reports a new IP, the Dashboard will automatically update the DNS records based on the configuration.
The DDNS functionality is suitable for servers with dynamic IPs. When the Agent reports a new IP (every 10 minutes), the Dashboard will automatically update the DNS records based on the configuration.
### Why Use Nezha Monitoring's DDNS Functionality?