---
title: "SSW Connector Network Requirements"
slug: "ssw-connector-network-requirements"
updated: 2026-05-26T15:19:27Z
published: 2026-05-26T15:19:27Z
canonical: "docs.ssw.splashtop.com/ssw-connector-network-requirements"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ssw.splashtop.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SSW Connector Network Requirements

## **Overview**

To ensure the Splashtop Secure Workspace (SSW) Connector operates correctly, the connector must be able to establish outbound connections to SSW control plane services over the internet.

These connections are required for:

- Secure tunnel establishment (WSS / TLS)
- Authentication and policy retrieval
- Continuous heartbeat and session maintenance

---

## **Required Outbound Access**

### **Protocols**

- HTTPS / TLS (TCP 443)
- Custom service port (TCP 9202)

### **Domains**

Please allow outbound access to:

```
*.ssw.splashtop.com
```

---

## **IP Whitelist (Optional)**

If your environment requires IP-based whitelisting instead of domain-based access, please allow outbound traffic to the following IP addresses:

### **1. Frankfurt, Germany**

- 3.125.253.149

### **2. London, England**

- 18.134.83.41

### **3. Portland, Oregon (US West)**

- 35.165.150.126
- 35.83.7.84
- 44.253.255.91

### **4. Ashburn, Virginia (US East)**

- 35.169.75.78
- 52.72.11.238
- 3.223.223.207

### **5. Hong Kong, China**

- 16.162.248.105
- 18.163.142.232
- 54.46.86.130

### **6. Taipei, Taiwan**

- 15.220.84.77

### **7. Tokyo, Japan**

- 13.159.0.147
- 57.183.80.25
- 52.196.78.119

---

## **Firewall / Network Requirements**

### Must Allow

- Outbound TCP traffic to the above domains/IPs on ports **443 and 9202**
- Long-lived connections (persistent TCP sessions)

---

### Must NOT Block or Interfere

To ensure stable operation, avoid the following:

- SSL/TLS inspection (MITM / Deep Packet Inspection)
- WebSocket blocking or rewriting
- Idle connection timeout that is too short
- Proxy interference with WebSocket (WSS)

---

## **Proxy Considerations**

If a proxy is required:

- It must support **WebSocket over TLS (WSS)**
- It must not terminate or rewrite TLS traffic
- Authentication-based proxies may require additional configuration

---

## **Common Symptoms of Network Misconfiguration**

If the above requirements are not met, you may observe:

- `i/o timeout` when connecting to port 443
- Frequent disconnections (`EOF`, `abnormal ping`)
- Connector stuck in reconnect loop
- Services appear discovered but are inaccessible

---

## **Verification Steps**

From the connector host, you can test connectivity:

```
curl https://<region>.ssw.splashtop.com
```

or

```
nc -vz <IP> 443
```

---

## **Recommendation**

For best reliability:

- Use **domain-based whitelisting (`*.ssw.splashtop.com`)**
- Avoid IP-only rules unless required
- Disable SSL inspection for these destinations