import{_ as e,c as t,o as a,a as s}from"./app.4f7c959e.js";const b='{"title":"Why the IP displayed in the admin panel and the actual IP of the Agent are not the same?","description":"","frontmatter":{},"headers":[{"level":2,"title":"Why the IP displayed in the admin panel and the actual IP of the Agent are not the same?","slug":"why-the-ip-displayed-in-the-admin-panel-and-the-actual-ip-of-the-agent-are-not-the-same"},{"level":2,"title":"Forgot your access password or deleted your access password","slug":"forgot-your-access-password-or-deleted-your-access-password"},{"level":2,"title":"Dashboard install/restart/update failed: iptables ......","slug":"dashboard-install-restart-update-failed-iptables"},{"level":2,"title":"Dashboard reboot failed: Invalid hostPort: nzsiteport etc.","slug":"dashboard-reboot-failed-invalid-hostport-nz-site-port-etc"}],"relativePath":"en_US/guide/dashboardq.md","lastUpdated":1656077214000}',o={},r=s(`<h2 id="why-the-ip-displayed-in-the-admin-panel-and-the-actual-ip-of-the-agent-are-not-the-same" tabindex="-1">Why the IP displayed in the admin panel and the actual IP of the Agent are not the same? <a class="header-anchor" href="#why-the-ip-displayed-in-the-admin-panel-and-the-actual-ip-of-the-agent-are-not-the-same" aria-hidden="true">#</a></h2><p>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: <a href="https://github.com/naiba/nezha/blob/master/cmd/agent/monitor/myip.go" target="_blank" rel="noopener noreferrer">myip.go</a><br> 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 <strong>entry IP</strong>, but the Agent tested out your <strong>exit IP</strong>. This problem may also occur in BGP servers and Leased line.</p><div class="tip custom-block"><p class="custom-block-title">TIP</p><p>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</p></div><p>You can also test the exit IP by running the following command in the Agent server:</p><div class="language-shell"><pre><code><span class="token function">curl</span> api.myip.la
<span class="token function">curl</span> ip.sb
<span class="token function">curl</span> ip-api.com
</code></pre></div><h2 id="forgot-your-access-password-or-deleted-your-access-password" tabindex="-1">Forgot your access password or deleted your access password <a class="header-anchor" href="#forgot-your-access-password-or-deleted-your-access-password" aria-hidden="true">#</a></h2><p>Please view or edit the <code>/opt/nezha/dashboard/data/config.yaml</code> file.<br> The password is located in the site-viewpassword item.</p><h2 id="dashboard-install-restart-update-failed-iptables" tabindex="-1">Dashboard install/restart/update failed: iptables ...... <a class="header-anchor" href="#dashboard-install-restart-update-failed-iptables" aria-hidden="true">#</a></h2><p>First, try restarting docker and retrying again</p><div class="language-shell"><pre><code>systemctl status <span class="token function">docker</span>
systemctl restart <span class="token function">docker</span>
systemctl status <span class="token function">docker</span>
</code></pre></div><p>Restart and try to reinstall the Dashboard.<br> If you still get iptables... etc. errors, then consider simply closing iptables or even removing it.<br> This issue may also be kernel related, try replacing the official kernel as well.</p><h2 id="dashboard-reboot-failed-invalid-hostport-nz-site-port-etc" tabindex="-1">Dashboard reboot failed: Invalid hostPort: nz_site_port etc. <a class="header-anchor" href="#dashboard-reboot-failed-invalid-hostport-nz-site-port-etc" aria-hidden="true">#</a></h2><p>Usually this does not occur, if it does, you can modify the configuration through the installation script.</p>`,13),i=[r];function n(d,l,h,p,c,u){return a(),t("div",null,i)}var f=e(o,[["render",n]]);export{b as __pageData,f as default};