Troubleshooting steps if the server monitor fails to show up on the Site24x7 web client even after successful installation of the agent

In cases where the server monitor does not show up even after proper installation of the agent, check if:

• The device key given is correct.
  
• Ensure TLS version 1.2 is enabled. 
  
• Check connectivity to Site24x7 servers from your Windows/Linux machines.
  
• The plus.site24x7.com/eu/in/cn/.net.au domain is blocked in the agent machine's firewall. Know the necessary ports to allow access to the server monitoring agent in your firewall. 
  
• There is sufficient licensing in your account. If not, purchase add-ons or upgrade to a higher pack.
  
• The customer ID in your machine matches the device key available in the Site24x7 web client. Depending on the OS, follow the steps below to perform this check:

             For Windows:

1. Open regedit.exe 
   
2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageEngine\Site24x7WindowsAgent
   
3. Check the value for CustomerId. This should match the device key (Log in to Site24x7 and go to Server > Server Monitor > Servers (+)  > Windows) of the account.
   
   

             For Linux, FreeBSD, and MacOS:

1. Open file -> /opt/site24x7/monagent/conf/monagent.cfg
   
2. Check the value of customer_id. This should match the device key of the account.
   

If the Customer ID field is not visible, it indicates that the key has been encrypted by the agent and cannot be accessed. Please share this information with our support team for a faster resolution.

If the issue still persists, please contact support@site24x7.com

• Related Articles

• Steps to install Linux monitoring agent in custom platforms/distributions

  If you want to install the Site24x7 Server Monitoring agent in platforms/flavors other than Debian, Ubuntu, CentOS, RedHat, Madriva, Fedora, Suse, Amazon Linux, Gentoo, CoreOS, Raspberry Pi (requires Python 3 and above), ARM Processor (requires ...

• Troubleshooting bulk installation failures of the APM Insight .NET agent

  You can perform a bulk installation during the .NET agent installation. If the bulk installation fails, it could be due to one of the following reasons: Error message/Issue Troubleshooting tip Network connectivity failure Ensure all machines within ...

• Troubleshooting steps for On-Premise Poller

  Prerequisites and basic details: Prerequisites for installing On-Premise Poller Necessary ports to allow access to the installed On-Premise Poller How secure is On-Premise Poller Amount of bandwidth consumed by the On-Premise Poller software Adding ...

• How to install packages to support Web Transaction (Browser) monitor in Linux On-Premise Poller

  To support Web Transaction (Browser) monitor on an On-Premise Poller, you can execute the following command in the terminal to install packages in CentOS 7.0 to 7.8 or in RHEL 7.x. Note: The Installation is supported only on 64-bit OS. Execute the ...

• How to retrieve logs from server-agent-based monitors?

  If you have a Windows agent, you can use the following path to retrieve the agent logs: Go to the installation directory > Site24x7 > WinAgent > Monitoring > Logs If you have a Linux server, you can retrieve logs for your server agent by using the ...