From ab75e73d33d6f204c658729a3f171c8d94c3b117 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E5=8D=96=E5=A5=B3=E5=AD=A9=E7=9A=84=E5=B0=8F=E7=81=AB?= =?UTF-8?q?=E6=9F=B4?= <44471469+Erope@users.noreply.github.com> Date: Mon, 3 Jul 2023 10:22:05 +0000 Subject: [PATCH] Fix IP-API --- docs/en_US/guide/dashboardq.md | 4 ++-- docs/en_US/guide/loginq.md | 3 ++- docs/guide/dashboardq.md | 4 ++-- docs/guide/loginq.md | 3 ++- 4 files changed, 8 insertions(+), 6 deletions(-) diff --git a/docs/en_US/guide/dashboardq.md b/docs/en_US/guide/dashboardq.md index 20e3af90..dd957bc3 100644 --- a/docs/en_US/guide/dashboardq.md +++ b/docs/en_US/guide/dashboardq.md @@ -7,7 +7,7 @@ To take a simple and very common example, the service provider to provide you a You can also test the exit IP by running the following command in the Agent server: ```shell -curl api.myip.la +curl https://ipapi.co/ip/ curl ip.sb curl ip-api.com ``` @@ -28,7 +28,7 @@ If you still get iptables... etc. errors, then consider simply closing iptables 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. +Usually this does not occur, if it does, you can modify the configuration through the installation script or edit `/opt/nezha/dashboard/docker-compose.yaml` directly. ## Wrong Dashboard layout, CSS resources cannot be loaded If the Dashboard page has an incorrect layout, the usual reason is that the CSS file is missing or cannot be loaded. diff --git a/docs/en_US/guide/loginq.md b/docs/en_US/guide/loginq.md index 5f811918..157a44d4 100644 --- a/docs/en_US/guide/loginq.md +++ b/docs/en_US/guide/loginq.md @@ -14,7 +14,8 @@ 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. +1. Clear your browser cookies and log in again, or change your browser. +2. Check the callback address to ensure that your callback address is correct and that both **the port and protocol** are correct! The address from which the request is initiated needs to be in the same domain as the callback address, and the port, protocol, and domain name (or IP) all need to be consistent. ### lookup xxx DNS resolution failure, in most cases, is due to iptables-related configuration changes. diff --git a/docs/guide/dashboardq.md b/docs/guide/dashboardq.md index 6bd65267..1acff542 100644 --- a/docs/guide/dashboardq.md +++ b/docs/guide/dashboardq.md @@ -7,7 +7,7 @@ 您也可以在 Agent 服务器中运行以下命令测试出口IP: ```shell -curl api.myip.la +curl https://ipapi.co/ip/ curl ip.sb curl ip-api.com ``` @@ -28,7 +28,7 @@ systemctl status docker 这个问题也可能与内核有关，也可以尝试更换官方内核。 ## 面板重启失败：Invalid hostPort: nz_site_port 等 -通常不会出现这个情况，如出现可以通过安装脚本修改配置。 +通常不会出现这个情况，如出现可以通过安装脚本修改配置，或者直接修改 `/opt/nezha/dashboard/docker-compose.yaml`文件。 ## 面板布局错误、CSS 资源无法被加载 如果出现 Dashboard 页面布局出现错误，通常的原因是 CSS 文件丢失或无法被加载 diff --git a/docs/guide/loginq.md b/docs/guide/loginq.md index 58187878..5ff61b1e 100644 --- a/docs/guide/loginq.md +++ b/docs/guide/loginq.md @@ -15,7 +15,8 @@ ## 登录后面板报错 ### http: named cookie not present -清理cookies后重新登录，或换个浏览器 +1. 清理cookies后重新登录，或换个浏览器 +2. 检查回调地址，确保您的回调地址正确且**端口与协议**均正确！发起请求的地址需要和回调地址处于同域，端口、协议和域名(或IP)都需要一致。 ### lookup xxx 容器DNS解析失败，多数情况下为修改了iptables相关配置。