Skip to main content
Question

SilentPush Integration – Test Connection fails with "Connection failed: None" (no HTTP response)

  • September 2, 2026
  • 1 reply
  • 16 views

Omskirt
Forum|alt.badge.img+7

Hi all,

 

We're trying to set up the built-in **SilentPush integration (v3.0)** in Google SecOps SOAR, but Test Connection consistently fails with no useful error detail. Hoping someone from the community or Google team can help point us in the right direction.

 

**Environment:**

  • ​Google SecOps SOAR (Google-managed / SaaS instance)
  • ​No self-hosted Remote Agent — running entirely on Google-managed infrastructure
  • ​SilentPush integration version 3.0

 

**What we've already verified/tried:**

1. Confirmed the correct API base URL per SilentPush's official docs (https://help.silentpush.com/docs/get-started-with-api): https://api.silentpush.com (root domain only, scheme included, no trailing path)

2. Confirmed API Key is populated and valid

3. Tested with "Verify SSL" enabled

4. Tested on two separate integration instances (a Shared Instance and the System Default Instance) — identical failure on both

5. Ruled out URL formatting issues — we initially hit a MissingSchema error (missing https://) and a wrong subdomain (app. instead of api.), both of which we've since corrected

 

**Current error on Test Connection:**

=============== Main - Started ===============

Connecting to Silent Push-Google SecOps...

Failed to connect to the Silent Push-Google SecOps server!

Error: Connection failed: None

 

Traceback (most recent call last):

  File ".../silent_push_manager.py", line 522, in test_connection

    raise e

  File ".../silent_push_manager.py", line 495, in test_connection

    raise SilentPushExceptions(f"Connection failed: {error_msg}")

exceptions.SilentPushExceptions: Connection failed: None

 

Status: 2

Result Value: False

 

The error message itself is empty (error_msg is None), which suggests the connection attempt is failing before any HTTP response is returned — not a credential/auth rejection, but something failing at the connection level itself.

 

**Question:** Is there a known outbound network/egress restriction on the Google-managed SecOps SOAR environment that would block or require allowlisting for api.silentpush.com? Has anyone else run into this with the SilentPush integration specifically, and if so, how was it resolved?

 

Appreciate any pointers — happy to provide more logs/screenshots if needed.

 

Thanks!

1 reply

matt-amastra
Forum|alt.badge.img+1
  • Bronze 1
  • September 2, 2026

Confirmed the correct API base URL per SilentPush's official docs

 

What is the exact ` Silent Push Server *` URL you are using in your SOAR Instance Config?

Looking at the manager for this integration in the IDE, it looks like "/api/v1/merge-api" is automatically appended to whatever you enter in this field before requests are made to their API.

Based on that plus Silent Push’s docs having the base URL as `https://api.silentpush.com/api/v1/merge-api/`, I believe the value you should enter in your SOAR Instance Config should be either `https://api.silentpush.com` or `api.silentpush.com`. If those don’t work, it may be worth trying simply `silentpush.com` just to see if your symptoms change with any of those inputs.