![\"\"\/](\"https:\/\/lh7-rt.googleusercontent.com\/docsz\/AD_4nXfgCht1ekbRGa9YnbqdhI0QihsTVdtuRAeMLkjWMjqNkT2DOtqI2rKZCFXr8ONlctuIbR8TIRcGkE3ecabN3STwCpYeGL6BCA7usfDYHQh7sqLEXnnEOveYAXrw4ovDpOCYtwM0Dg?key=Bdmdiqf1sGhwYrOgdYy5yIsf\")
<\/figure>\n\n\n\nThe error message RunCloud Agent “security-bannedip”<\/strong> and the inability to communicate with the server, such as \u2018server name\u2019(x.x.x.x)<\/strong>, typically indicates a connection issue between your server and the RunCloud agent. <\/p>\n\n\n\n What\u2019s Behind This Error?<\/strong><\/p>\n\n\n\n +++++++++++++++++++++++++++<\/p>\n\n\n\n This error typically occurs due to multiple factors, such as:<\/p>\n\n\n\n If the server is offline or unresponsive, the RunCloud agent will be unable to establish a connection to it. This situation can arise for various reasons, such as scheduled maintenance, unexpected system crashes, or unplanned downtime. During maintenance, servers are intentionally taken offline for updates or repairs, which temporarily disrupts communication. Similarly, a system crash caused by software errors, hardware malfunctions, or resource overloads can render the server unresponsive, preventing the agent from reaching it. In some cases, servers may experience sudden, unforeseen outages due to network failures or other technical issues, which can prevent the agent from connecting and cause communication errors.<\/p>\n\n\n\n A firewall, whether it\u2019s on the server itself or within the network infrastructure, could be preventing the connection between RunCloud and your server. Firewalls are designed to control incoming and outgoing traffic based on specified security rules, but if certain essential ports\u2014such as 22 (SSH), 443 (HTTPS), 80 (HTTP), and 34210 (for RunCloud agent communication)\u2014are blocked, or if the required IP addresses aren\u2019t whitelisted, the RunCloud agent will be unable to establish a connection with the server. As a result, this can lead to communication failures and errors in managing the server through RunCloud. <\/p>\n\n\n\n If your server is experiencing resource exhaustion, such as high CPU usage or insufficient RAM, often due to increased traffic or resource-intensive processes, it may become overwhelmed and unable to manage incoming connections effectively. This can cause the RunCloud agent to fail to communicate with the server.<\/p>\n\n\n\n To diagnose this issue, you can monitor your server’s resource usage through the Server Monitoring dashboard<\/strong> in the RunCloud panel. <\/p>\n\n\n\n RunCloud comes preconfigured with custom packages, such as\u00a0lsws-rc,\u00a0nginx-rc,\u00a0apache2-rc,\u00a0php74rc, and others,\u00a0specifically designed to ensure optimal performance and compatibility within the RunCloud environment. Installing additional packages outside of these predefined ones can disrupt the carefully configured setup. This could lead to conflicts or inconsistencies in the system, potentially disrupting the smooth operation of your web applications.<\/p>\n\n\n\n \u00a0Temporary network issues, such as connectivity interruptions, DNS problems, or routing issues, can prevent the RunCloud agent from communicating successfully with the server.<\/p>\n\n\n\n If that’s the case, simply follow the steps below to resolve the issue with ease:<\/strong><\/p>\n\n\n\n ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<\/p>\n\n\n\n To check if your server is down, you can use the ping<\/strong> command or online monitoring tools. If the server is unresponsive, it\u2019s advisable to contact your server provider for further assistance and to investigate the issue.<\/p>\n\n\n\n To verify if your firewall is blocking essential ports, use the nmap<\/strong> command to check the status of ports on your server. Ensure that ports 22<\/strong>, 443<\/strong>, 80<\/strong>, and 34210<\/strong> are open on your server\u2019s external firewall to maintain proper communication.<\/p>\n\n\n\n If your server is experiencing high resource usage, it’s crucial to identify the root cause in real time. Taking proactive steps to manage resources and prevent future overloads is essential. If you need help, feel free to reach out to us, and we\u2019ll assist you in resolving the issue.<\/p>\n\n\n\n Custom packages installed outside the standard RunCloud setup can compromise the system\u2019s integrity. In such cases, it\u2019s essential to carefully remove these custom packages from your server to restore the proper functioning of RunCloud. Always ensure that any package installation or modification is compatible with the RunCloud environment to prevent potential system malfunctions.<\/p>\n\n\n\n To resolve network-related issues, check your server\u2019s internet connection, ensure that DNS settings are correct, and verify that there are no disruptions in the network path. A stable and reliable network is crucial for seamless operation and communication between your server and the RunCloud platform.<\/p>\n\n\n\n Note: In some cases, even after the issue is resolved, communication between RunCloud and the server may not be re-established immediately. If this happens, you may need to manually restart the RunCloud agent on your server.<\/p>\n\n\n\n Still having trouble or need some help? Don\u2019t hesitate to reach out \u2013 we\u2019re here to assist you every step of the way!!!<\/p>\n\n\n\n Facing issues? <\/p>\n\n\n\n Our technical support\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
engineers can solve it. <\/p>\n\n\n\n![\"Contact](\"https:\/\/no-cache.hubspot.com\/cta\/default\/2725694\/3350a795-db50-482f-9911-301930d1b1be.png\")
<\/a><\/span>