nezhahq.github.io/assets/en_US_guide_q2.md.8b3617ad.js

import{_ as e,o as t,c as o,R as n}from"./chunks/framework.1625126e.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/q2.md","filePath":"en_US/guide/q2.md","lastUpdated":1695608737000}'),r={name:"en_US/guide/q2.md"},a=n('<h4 id="let-the-agent-start-on-line-and-the-self-test-process-of-the-problem" tabindex="-1">Let the Agent start/on-line, and the self-test process of the problem <a class="header-anchor" href="#let-the-agent-start-on-line-and-the-self-test-process-of-the-problem" aria-label="Permalink to &quot;Let the Agent start/on-line, and the self-test process of the problem&quot;">​</a></h4><ol><li>Run <code>//opt/nezha/agent/nezha-agent -s IP/Domin(Panel IP or Domain not connected to CDN):port(Panel RPC port) -p secret(Agent Secret) -d</code> Check the logs to see if the timeout is due to a DNS problem or poor network</li><li><code>nc -v domain/IP port(Panel RPC port)</code> or <code>telnet domain/IP port(Panel RPC port)</code> to check if it&#39; s a network problem, check the inbound and outbound firewall between the local machine and the panel server, if you can&#39; t determine the problem you can check it with the port checking tool provided by <a href="https://port.ping.pe/" target="_blank" rel="noreferrer">https://port.ping.pe/</a></li><li>If the above steps work and the Agent is online, please try to turn off SELinux on the panel server. <a href="https://www.google.com/search?q=How+to+disable+SELinux" target="_blank" rel="noreferrer">How to close SELinux？</a></li></ol>',2),s=[a];function l(i,c,h,p,d,_){return t(),o("div",null,s)}const u=e(r,[["render",l]]);export{m as __pageData,u as default};