cancel
Showing results for 
Search instead for 
Did you mean: 

UCA Agent failing to connect with "Not Connected" or "Never Connected"

05 Base Camper

UCA Agent failing to connect with "Not Connected" or "Never Connected"

Hi 

I am trying to set up the IR UC assessor on our network, we have opened up the neccessary firewall ports and defined the proxy server addressing as recommended in the start up guide, however we are still failing to get the client failing to connect.

 

We have an infrastructure that uses Zscaler as our proxy and using Windows 10 Dell laptops.

 

Is there any troubleshooting steps I can go through to investigate further.

 

Warm Regards

2 REPLIES 2
Community Manager

Re: Agent failing to connect

Hi Krishan,

 

I received good news that you resolved it with proxy configuration for the required secure websocket connection. Here are some general troubleshooting steps for this kind of scenario: 

 Prognosis-UC-Assessor-Agent-Not-Connected-or-Never-Connected.png

 

1. Confirm which agents (or all of them) and is it "Not Connected" or "Never Connected";

2. If "Never Connected" then make sure the agent is installed (on the designated agent PC Download Installer, copy to clipboard the Key, run the installer );

3. If "Not Connected" then check if the 'Prognosis Agent' service is running on that PC, if not, start it up.

4. Consider Help Center: 'Firewall requirements' and 'Configuring the Prognosis Agent to use a forward proxy' articles;

5. Test successful initial connection in a browser (not IE) this 'https://data.iot.us-west-2.amazonaws.com/' returns: 

{"message":"Not Found","traceId":"93f9…"}

6. Test successfully kept connection over several minutes, in a browser 'https://www.websocket.org/echo.html' with wss://echo.websocket.org 

7. If these work from browser, check the browser proxy server setting, set the same for the agent in the PROGNOSIS_HTTP_PROXY environment variable using Help Center 'Configuring the Prognosis Agent to use a forward proxy'.

8. Check for 'error:' in the log "C:\ProgramData\Prognosis Agent\Logs\agent.log" if still failing and Google search the error messages, as they can help identify issues in the environment outside of the Prognosis Agent.

9. Submit a request for assistance to IR and attach log and details.

HTH

 

How-to-submit-request-to-IR-Support.png

Community Manager

Re: Agent failing to connect

Also try give the Prognsis Agent service a restart and then check if the service started up and spawned processes successfully and then was able to establish a TCP on port 443 connection to the amazon cloud:

 

tasklist | findstr "PrognosisAgentService.exe node.exe Session# ========"
netstat -ano | findstr "<the PIDs identified in the tasklist output>"

Example:

Agent-Service-Restart.png

 

When the Prognosis Agent has connected successfully:

Agent-Connected-Successfully.pngAnother example with comments explaining:

Example-verifying-Agent-connect-to-cloud.png

Blog: Path Insight key 11.5 release highlights

The latest version of Path Insight is now available together as part of the Prognosis 11.5 release, and contains a lot of exciting updates that can be used for deeper dive network troubleshooting. In this blog post we cover some of the key highlights in the latest version of Path Insight.

Read blog
Top Liked Members