Error codes · Network

PULSE-NET-002 Server certificate not accepted

What does this mean

Pulse refused to connect to the server because it could not verify its certificate - the “passport” with which the server confirms that it is who it claims to be. This is how Pulse protects your data from tampering.

Why does this happen

  • The connection is intercepted by a proxy or antivirus on your network and substitutes its own certificate, which the computer does not trust. A common occurrence in organizational networks.
  • The date or time on the computer is incorrect: the certificate appears to be expired or not yet valid.

In “Details” - verification code: net::ERR_CERT_…, CERT_HAS_EXPIRED, SELF_SIGNED_CERT_IN_CHAIN, unable to get local issuer certificate or git answer SSL certificate problem.

What to do

  1. Check the date, time and time zone on your computer; It is better to enable their automatic installation.
  2. On an organization's network, ask the administrator what root certificate needs to be installed and install it in the system certificate store: The Pulse window goes to the network through the system settings.
  3. For agents, specify the same certificate in the file: “Settings → Network and privacy → Network for agents”, line “Root certificate (PEM)”.
  4. The error came from git - it has its own certificate store: git config --global http.sslCAInfo <file path>.
  5. Restart Pulse and try again.

When to write to support

Write to us if the date and time are correct, the organization’s certificate is installed, but the error remains. Click “Send report” in the error card - a report form will open, where the code and details have already been entered, the secrets are hidden in them. Add which server you connected to and click “View and Send”: the window will show exactly what is left - check and click “Submit”. If the cloud is turned off, the button is called “View and save” - send the resulting file to us in any way.