更新：中英文排障指南- Login

docs/en_US/guide/loginq.md

@@ -1 +1,40 @@
-# Login
+## Page refuses to connect or times out after login callback  
+1. Your server cannot connect to Github, consider trying several times or switching to Gitlab.
+2. You have configured the wrong callback URL, make sure your callback URL is correct and **port and protocol** are correct!
+3. An unknown error occurred in Dashboard, you can use the script to check the logs.  
+
+::: tip  
+What is a protocol?   
+In the browser, your domain name ending with `://` is the protocol, usually `http` and `https`. Since the Dashboard may be accessible by multiple protocols + domain + port combinations under normal deployment, please make sure to choose the most appropriate one as the callback.  
+:::    
+
+### How do I check if my callback URL is wrong?  
+Please make sure the protocol+domain+port displayed by your browser before login and the protocol+domain+port you jump to after login are the same.  
+Please make sure your path is `/oauth2/callback`, **all lowercase**.  
+
+## Dashboard errors after login
+### http: named cookie not present
+Clear your browser cookies and log in again, or change your browser.  
+
+### lookup xxx
+DNS resolution failure, in most cases, is due to iptables-related configuration changes.  
+It is recommended to restart docker first, `sudo systemctl restart docker`, and then use the script to restart the Dashboard.  
+If the lookup error still occurs, it is recommended to check whether there are other tools to control iptables, such as Aapanel Firewall.  
+This problem may also be related to the kernel, please try to change the official kernel.  
+
+### The authorization method is invalid, or the login callback URL is invalid, expired, or has been revoked
+Suggest changing the authentication method to Github/Gitlab.  
+
+### oauth2: server response missing access_token
+It may be caused by a number of factors, the most likely is a network problem, we suggest to check the network and retry.  
+If you can't solve it, we suggest changing the authentication method to Github/Gitlab.  
+
+### This user is not the administrator or cannot log in
+You have logged into the wrong account or configured the wrong username, note that **username is not email**, you can use a script to modify it.  
+
+### dial tcp xxx:443 i/o timeout
+If the server has network problems, you can restart docker first, `sudo systemctl restart docker`, and then use the script to restart the Dashboard.  
+You can also change to another OAuth method if necessary.  
+
+### net/http: TLS handshake timeout
+Same as above.

docs/guide/loginq.md

@@ -1,11 +1,12 @@
 ## 登录回调后页面卡住\拒绝连接\响应时间过长
 还有其他一些表现形式，总之登录后浏览器无法正常显示。  
-1. 您的主机无法连接到Github/Gitee，最常见于国内主机配置Github情况下，可以考虑多尝试几次或者切换到Gitee。
+1. 您的服务器无法连接到Github/Gitee，最常见于国内服务器配置Github情况下，可以考虑多尝试几次或者切换到Jihulab/Gitee。
 2. 您配置错了回调地址，确保您的回调地址正确且**端口与协议**均正确！
 3. Dashboard发生未知错误，您可以使用脚本查看日志，但此项可能性较低。
 
 ::: tip  
-什么是协议？在浏览器中，您的域名以://结尾的字符串即为协议，通常为http和https两种。由于正常部署情况下面板可能有多种协议+域名+端口组合均可访问，请务必选一个最合适的作为回调。  
+什么是协议？  
+在浏览器中，您的域名以`://`结尾的字符串即为协议，通常为 `http` 和 `https` 两种。由于正常部署情况下面板可能有多种协议+域名+端口组合均可访问，请务必选一个最合适的作为回调。  
 :::  
 
 ### 如何检查我的回调地址是否错误？  
@@ -20,7 +21,7 @@
 容器DNS解析失败，多数情况下为修改了iptables相关配置。  
 建议先重启docker，`sudo systemctl restart docker`，再使用脚本重启面板。  
 仍然出现lookup错误建议查看是否有其他控制iptables的工具，如宝塔防火墙等。  
-这个问题也可能由内核引起，请尝试更换官方内核。  
+这个问题也可能与内核有关系，请尝试更换官方内核。  
 
 ### 授权方式无效，或者登录回调地址无效、过期或已被撤销
 只出现在Gitee登录方式中，原因不明，建议更换到Jihulab。
@@ -34,7 +35,7 @@
 
 ### dial tcp xxx:443 i/o timeout
 网络问题，可先重启docker，`sudo systemctl restart docker`，再使用脚本重启面板。  
-如为国内主机配置Github登陆方式，则建议切换到Jihulab以避免网络干扰。
+如为国内服务器配置Github登陆方式，则建议切换到Jihulab以避免网络干扰。
 
 ### net/http: TLS handshake timeout
 同上。