更新：中英文排错指南-Dashboard

docs/en_US/guide/dashboardq.md

@@ -1 +1,31 @@
-# Dashboard
+## Why the IP displayed in the admin panel and the actual IP of the Agent are not the same?  
+First of all, explain how the IP displayed in the admin panel is gotten: the Agent will request the IP-API every once in a while, get the IP information and report it to the Dashboard, the IP-API currently used can be viewed here: [myip.go](https://github.com/naiba/nezha/blob/master/cmd/agent/monitor/myip.go)  
+If you find that the IP displayed in the admin panel is not the same as the IP provided to you by the service provider, the biggest possibility is that the service provider gave you the **entry IP**, but the Agent tested out your **exit IP**. This problem may also occur in BGP servers and Leased line.  
+::: tip  
+To take a simple and very common example, the service provider to provide you a anti-DDoS server, in order to meet the goals of both DDoS protection and low network disruption rate, the IP provided to you may be the mapped anti-DDoS IP and not the real exit IP of your server  
+:::   
+
+You can also test the exit IP by running the following command in the Agent server:  
+```shell
+curl api.myip.la
+curl ip.sb
+curl ip-api.com
+```  
+
+## Forgot your access password or deleted your access password
+Please view or edit the `/opt/nezha/dashboard/data/config.yaml` file.   
+The password is located in the site-viewpassword item.  
+
+## Dashboard install/restart/update failed: iptables ......
+First, try restarting docker and retrying again  
+```shell
+systemctl status docker
+systemctl restart docker
+systemctl status docker
+```  
+Restart and try to reinstall the Dashboard.  
+If you still get iptables... etc. errors, then consider simply closing iptables or even removing it.  
+This issue may also be kernel related, try replacing the official kernel as well.  
+
+## Dashboard reboot failed: Invalid hostPort: nz_site_port etc.
+Usually this does not occur, if it does, you can modify the configuration through the installation script. 

docs/guide/dashboardq.md

@@ -1,35 +1,31 @@
-## 实时通道断开/在线终端连接失败
-请查看[常见问题-实时通道断开/在线终端连接失败](/guide/q4.html)  
-在此不再赘述。
-
-## 后台显示的IP和Agent实际IP不一致？
-首先解释后台显示的IP是怎么来的：Agent会每隔一段时间请求一遍IP-API，获取到IP信息后进行上报，目前使用的IP-API可在此查看[myip.go](https://github.com/naiba/nezha/blob/master/cmd/agent/monitor/myip.go)。  
-如您认为后台显示的IP和服务商提供给您的IP不一致，最大的可能是服务商给您的是**入口**，但Agent测试的是您的**出口**。这个问题也可能会出现在多线主机中。    
+## 为什么管理面板中显示的IP和Agent实际IP不一致？  
+首先解释管理面板中显示的IP是怎么得到的：Agent会每隔一段时间请求一遍IP-API，获取到IP信息后上报到Dashboard，目前使用的IP-API可在此查看：[myip.go](https://github.com/naiba/nezha/blob/master/cmd/agent/monitor/myip.go)。  
+如您发现管理面板中显示的IP和服务商提供给您的IP不一致，最大的可能是服务商给您的是**入口IP**，但Agent测试的是您的**出口IP**。这个问题也可能会出现在多线服务器和IPLC专线中。    
 ::: tip  
-举个简单也十分常见的例子，服务商给您提供的是一台高防主机，为了同时满足高防和低网络中断率的目标，提供给您的IP可能是经过映射后的高防IP而并非您主机的真实出口IP 
+举个简单也十分常见的例子，服务商给您提供的是一台高防服务器，为了同时满足高防和低网络中断率的目标，提供给您的IP可能是经过映射后的高防IP而并非您服务器的真实出口IP 
 :::  
 
-您也可以使用以下命令在Agent部署主机中进行测试:   
+您也可以在Agent服务器中运行以下命令测试出口IP:   
 ```shell
 curl api.myip.la
 curl ip.sb
 curl ip-api.com
 ```
 
-## 查看密码忘记\删除查看密码
+## 忘记查看密码\删除查看密码
 请查看或编辑 `/opt/nezha/dashboard/data/config.yaml` 文件。   
-密码位于 site-viewpassword。
+密码位于 site-viewpassword 项中。
 
 ## 面板安装/重启/更新失败: iptables ......
-首先尝试重启docker再操作
+首先尝试重启docker再操作  
 ```shell
 systemctl status docker
 systemctl restart docker
 systemctl status docker
 ```
 重启后尝试重新安装面板。  
-若依然出现iptables...等错误，则考虑是否直接关闭iptables甚至移除iptables。  
-这个问题也可能由内核引起，也可以尝试更换官方内核。  
+若依然出现iptables...等错误，则考虑直接关闭iptables甚至移除iptables。  
+这个问题也可能与内核有关，也可以尝试更换官方内核。  
 
 ## 面板重启失败：Invalid hostPort: nz_site_port 等
-按理不应该出现这个情况，如出现可以通过脚本修改配置。  
+通常不会出现这个情况，如出现可以通过安装脚本修改配置。