Checking the accessibility of Site24x7 server from the On-Premise Poller

Checking the accessibility of Site24x7 server from the On-Premise Poller

Once you've installed the On-Premise Poller, perform the following actions to check if the On-Premise Poller can connect to Site24x7 servers. Ensure to allow access to the necessary ports.
Notes
Note: The domain referenced in this page applies to the United States region. Please use the appropriate domain for your specific region:
European Union: pluspoller.site24x7.eu
India: pluspoller.site24x7.in
China: pluspoller.site24x7.cn
Australia: pluspoller.site24x7.net.au
Canada: pluspoller.site24x7.ca
Japan: pluspoller.site24x7.jp
Saudi Arabia: pluspoller.site24x7.sa

1. Verifying the accessibility via web browser 

  • Open a browser and enter the URL https://plus.site24x7.com/ (.eu, .cn, .in, .net.au, .jp, .sa, .ca)  or https://plus2.site24x7.com/ (.eu, .cn, .in, .net.au, .jp, .sa, .ca) or http://pluspoller.site24x7.com/ (.eu, .cn, .in, .net.au, .jp, .sa, .ca). 
  • Check if the following page is displayed in the case of https://plus.site24x7.com/ (.eu, .cn, .in, .net.au, .jp, .sa, .ca), https://plus2.site24x7.com/ (.eu, .cn, .in, .net.au, .jp, .sa, .ca), and http://pluspoller.site24x7.com/ (.eu, .cn, .in, .net.au, .jp, .sa, .ca). 

  • If yes, your On-Premise Poller is connected to the Site24x7 server. 
NotesNote: If the Site24x7 server is not reachable, please check your network connectivity.

2. Verifying the accessibility on Linux machines via terminal

If you have installed the On-Premise Poller using a silent installation on your machine, follow these steps to check accessibility:  

  1. Testing accessibility without a proxy

To check the accessibility without a proxy, execute the following command to verify access:
wget plus.site24x7.com (.eu, .cn, .in, .net.au, .jp, .sa, .ca) 

  1. Testing accessibility with a proxy

If the proxy details are unclear, verify them using the commands below:
  1. Proxy without authentication: To use a proxy without credentials, execute the following command:
    curl -A "Site24x7-Poller" --proxy "https://proxy_host:proxy_port" -Lksv "https://pluspoller.site24x7.com"    
  2. Proxy with authentication: To use a proxy with the required credentials, execute the following command:
    curl -A "Site24x7-Poller" --proxy "https://proxy_user:proxy_password@proxy_host:proxy_port" -Lksv "https://pluspoller.site24x7.com" 
  3. Alternative command: If the On-Premise Poller is configured to use a proxy, execute the following command:
    wget -e use_proxy=yes -e https_proxy=proxy_host --proxy-user=proxy_username --proxy-password=proxy_password https://pluspoller.site24x7.com/ (.eu, .cn, .in, .net.au, .jp, .sa, .ca) 
Notes
Note: Make sure to replace the placeholders with the appropriate values:
proxy_host
your_proxy_hostname
proxy_port
your_proxy_port_number
proxy_user
your_proxy_username
proxy_password
your_proxy_password
WarningImportant: Follow the same steps for the domain plus2.site24x7.com (.eu, .cn, .in, .net.au, .jp, .sa, .ca) by replacing the URL in the above commands.

A successful connection will return HTTP response code 200, confirming that the On-Premise Poller has proper access.

3. Verifying the accessibility on Windows machine via terminal

To verify your PowerShell version on your machine, follow the below steps:
  1. Open the PowerShell console.
  2. Enter the command:
    $PSVersionTable
If the command executes successfully, the machine will display the current PowerShell version.

  1. Supported command for PowerShell 4.0 and previous versions

To verify access for the machines running PowerShell versions below 5.0, execute the following commands on the machine where the On-Premise Poller is installed:
$ProxyAddress = "proxy_address" [system.net.webrequest]::defaultwebproxy = New-Object system.net.webproxy($ProxyAddress) [System.Net.CredentialCache]$credentialCache = New-Object System.Net.CredentialCache  $credential = New-Object System.Net.NetworkCredential("username", "Password","domain") $credentialCache.Add($ProxyAddress,"Basic",$credential) [system.net.webrequest]::defaultwebproxy.credentials = $credentialCache [system.net.webrequest]::defaultwebproxy.BypassProxyOnLocal = $true [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 
Invoke-WebRequest -uri "https://pluspoller.site24x7.com/(.eu, .cn, .in, .net.au, .jp, .sa, .ca)

  1. Supported command for PowerShell 5.0 and above versions

1. Testing accessibility without a proxy
To verify basic connectivity,  execute the following command:
Invoke-WebRequest -Uri "https://pluspoller.site24x7.com"(.eu, .cn, .in, .net.au, .jp, .sa, .ca)
2. Testing accessibility with a proxy
    1. Proxy without credentials: To use a proxy that does not require authentication, execute the following command: 
      Invoke-WebRequest -Uri "https://pluspoller.site24x7.com" -Proxy "http://proxy_host:proxy_port" (.eu, .cn, .in, .net.au, .jp, .sa, .ca)
    2. Proxy with credentials: To use a proxy with required authentication, execute the following command:
      Invoke-WebRequest -Uri "https://pluspoller.site24x7.com" -Proxy "http://proxy_host:proxy_port" -ProxyCredential 
    3. Alternative command (with explicit credentials): To authenticate the details within the script, execute the following command:
      $ProxyAddress = "http://proxy_url:proxy_port [system.net.webrequest]::defaultwebproxy = New-Object system.net.webproxy($ProxyAddress)
      $CredCache = [System.Net.CredentialCache]::new()
      $NetCreds = [System.Net.NetworkCredential]::new("username","password","domain")
      $CredCache.Add($ProxyAddress, "Basic", $NetCreds) [system.net.webrequest]::defaultwebproxy.credentials = $CredCache [system.net.webrequest]::defaultwebproxy.BypassProxyOnLocal = $true [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
      Invoke-WebRequest -uri "https://pluspoller.site24x7.com/" (.eu, .cn, .in, .net.au, .jp, .sa, .ca)
Note: Make sure to replace the placeholders with the appropriate values
proxy_url
Your proxy host IP 
proxy_port
Your proxy port 
username
Your proxy user name
password
Your proxy password
ProxyCredential
Your proxy credentials
domain
Your domain name.
If there is no domain, then type an empty string.
Example: $ProxyAddress = "http://192.168.100.100:3128/"
Successfully connecting and verifying an HTTP response code of 200 confirms that your On-Premise Poller is properly configured and communicating with the Site24x7 servers. Regular checks and updates to configurations can further maintain optimal performance and security for your systems.

    • Related Articles

    • Exclude the selective SSH algorithms in On-Premise Poller during SFTP Transfer monitoring

      By excluding SSH algorithms, you can restrict Site24x7 SSH Client from using the excluded algorithm while connecting to the SSH server during SFTP Transfer monitoring. Follow the steps mentioned below for SSH algorithm exclusion in On-Premise Poller ...

    • Executables and scripts to allow for Windows server monitoring

      One of the reasons you could not enable Site24x7 server monitoring could be your organization's group policy denying access to the executables, scripts, and batch files associated with Site24x7 server monitoring. Mark the following executables, ...

    • No data for service and process in Windows server monitor

      If you see "No Data" for process and service metrics (such as CPU or memory usage of monitored services) in the Site24x7 Windows server monitor user interface, follow the troubleshooting steps below. Run PowerShell Commands Open PowerShell as ...

    • Compare our various methodologies for Website Monitoring

      Get to know Site24x7 monitors better and choose the one that best fits your monitoring needs. Compare the functionality of the following monitors: Website Monitoring Webpage Speed (Browser) Web Transaction Monitoring Web Transaction (Browser) SSL/TLS ...

    • Monitor and validate DNS IP changes using regex

      DNS administrators often monitor their DNS servers to detect changes in domain resolution and ensure IP mappings remain secure and accurate. Problem When your organization adds or modifies an IP address for your domain name, it’s critical to: Be ...