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.

The domain referenced in this page applies to the United States region. Please use the appropriate domain for your specific region:

1. European Union: pluspoller.site24x7.eu
2. India: pluspoller.site24x7.in
3. China: pluspoller.site24x7.cn
4. Australia: pluspoller.site24x7.net.au
5. Canada: pluspoller.site24x7.ca
6. Japan: pluspoller.site24x7.jp
7. Saudi Arabia: pluspoller.site24x7.sa
8. UAE: pluspoller.site24x7.ae
9. UK: pluspoller.site24x7.uk
   

Verifying the accessibility via web browser   

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

• If yes, your On-Premise Poller is connected to the Site24x7 server.

If the Site24x7 server is not reachable, please check your network connectivity.

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. Check DNS resolution and TCP connectivity  

Run the following command:

nc -zv pluspoller.site24x7.com 443

Alternatively, run:

timeout 3 bash -c '</dev/tcp/pluspoller.site24x7.com/443' && echo "OPEN" || echo "CLOSED"

2. Perform a full connectivity check  

• Without a proxy:
  curl -s -o /dev/null -w "HTTP Status: %{http_code}\nRemote IP: %{remote_ip}\nSSL Connect Time: %{time_appconnect}s\nTotal Time: %{time_total}s\n" https://pluspoller.site24x7.com

• With a proxy and credentials:
  curl -x http://proxy.yourdomain.com:8080 -U "username:password" -s -o /dev/null -w "HTTP Status: %{http_code}\nRemote IP: %{remote_ip}\nSSL Connect Time: %{time_appconnect}s\nTotal Time: %{time_total}s\n" https://pluspoller.site24x7.com

• With a proxy without credentials:
  curl -x http://proxy.yourdomain.com:8080 -s -o /dev/null -w "HTTP Status: %{http_code}\nRemote IP: %{remote_ip}\nSSL Connect Time: %{time_appconnect}s\nTotal Time: %{time_total}s\n" https://pluspoller.site24x7.com

If curl is not installed, use the following commands.

• Without a proxy:
  echo "Q" | openssl s_client -connect pluspoller.site24x7.com:443 -brief

• With a proxy:
  echo "Q" | openssl s_client -connect pluspoller.site24x7.com:443 -proxy user:password@proxy_host:proxy_port -brief

3. Check the network path  

To verify the network path, run the following command:

traceroute pluspoller.site24x7.com

Verifying the accessibility on Windows machine via terminal

1. Check DNS resolution and TCP connectivity  

Open PowerShell and run:

Test-NetConnection -ComputerName pluspoller.site24x7.com -Port 443

The above command works in PowerShell 4.0 or later.

Alternatively, run:

if ((New-Object System.Net.Sockets.TcpClient).ConnectAsync("pluspoller.site24x7.com", 443).Wait(3000)) { "OPEN" } else { "CLOSED" }

2. Perform a full connectivity check  

If curl is installed, use the following commands:

• Without a proxy:
  curl.exe -s -o NUL -w "HTTP Status: %{http_code} | Remote IP: %{remote_ip} | SSL Connect Time: %{time_appconnect}s | Total Time: %{time_total}s" https://pluspoller.site24x7.com

• With a proxy:
  curl.exe -x http://proxy.yourdomain.com:8080 -U "username:password" -s -o NUL -w "HTTP Status: %{http_code} | Remote IP: %{remote_ip} | SSL Connect Time: %{time_appconnect}s | Total Time: %{time_total}s" https://pluspoller.site24x7.com

Remove -U "username:password" if authentication is not configured.

If curl.exe is not installed, open PowerShell and use the following commands.

• Without a proxy:
  Invoke-WebRequest -Uri "https://pluspoller.site24x7.com" -UseBasicParsing

• With a proxy without credentials:
  Invoke-WebRequest -Uri "https://pluspoller.site24x7.com" -Proxy "http://proxy_host:proxy_port"

• With a proxy and credentials:
  Invoke-WebRequest -Uri "https://pluspoller.site24x7.com" -Proxy "http://proxy_host:proxy_port" -ProxyCredential (New-Object System.Management.Automation.PSCredential("", (ConvertTo-SecureString "" -AsPlainText -Force))) -UseBasicParsing

3. Check the network path  

To verify the network path, run the following command:

tracert pluspoller.site24x7.com

Make sure to replace the following in the code:

Value	Replace with
pluspoller.site24x7.com	Data center-specific Site24x7 server address
proxy.yourdomain.com	Proxy hostname
8080	Proxy port
username	Proxy username
password	Proxy password
proxy_host	Proxy hostname
proxy_port	Proxy port
<DOMAIN\username>	Proxy username, including domain if applicable
<your_password>	Proxy password

Data center-specific server addresses  

Use the Site24x7 server address corresponding to your data center: