---
title: "Connector Log Collection"
slug: "connector-log-collection"
updated: 2025-05-22T03:26:21Z
published: 2025-05-22T03:26:21Z
canonical: "docs.ssw.splashtop.com/connector-log-collection"
---

> ## 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.

# Connector Log Collection

If you need to collect logs for troubleshooting the Splashtop Secure Workspace Connector, you can either upload logs directly through the web console or manually collect them depending on your situation.

---

## Option 1: Upload Logs via Web Console (Recommended)

If the connector is running and accessible:

1. Navigate to the **SSW Web Console** → **Deployment** → **Connector** page.
2. Locate your connector and click the **“Upload Logs”** button under the **Actions** column.
3. Once the logs are uploaded successfully, please provide your **Organization ID** and **Connector Name** to support so we can help identify the issue.

---

## Option 2: Manual Log Collection

If the connector cannot upload logs (e.g., due to startup or upgrade issues), please follow the instructions below based on your operating system or deployment method.

## **Windows Log Collection**

### **Locating the Logs**

1. Open **File Explorer**.
2. Navigate to the following directory:

```
C:\ProgramData
```
3. Locate a folder with your connector’s name. The folder name follows this format:

```
connector-{connector-name}
```

For example, if your connector name is `foobar`, then the folder name will be `connector-foobar`.
4. Inside this folder, locate the **log** directory.
5. The main log file to collect is:

```
log\connector.log
```

### **Compressing and Sending Logs**

Once you have located the logs:

1. Right-click the **log** folder.
2. Select **Send to > Compressed (zipped) folder**.
3. Send the compressed file to support or attach it to your ticket.

---

## **MacOS Log Collection**

### **Locating the Logs**

1. Open the **Terminal** application.
2. Navigate to the connector log directory:

```
cd /Library/Application\ Support/connector-{connector-name}/log
```
3. Identify the primary log file:

```
connector.log
```

### **Compressing and Sending Logs**

To prepare logs for support:

1. Run the following command to create a compressed archive:

```
tar -czvf connector-logs.tar.gz connector.log
```
2. Attach `connector-logs.tar.gz` to your support ticket or send it to support.

---

## **Linux Log Collection**

### **Locating the Logs**

1. Open a **terminal**.
2. Navigate to the connector log directory:

```
cd /etc/connector-{connector-name}/log
```
3. Identify the main log file:

```
connector.log
```

### **Compressing and Sending Logs**

To package logs for support:

1. Run the following command:

```
tar -czvf connector-logs.tar.gz connector.log
```
2. Attach `connector-logs.tar.gz` to your support ticket or send it to support.

---

## **Docker Log Collection**

If you deployed the connector using Docker, you can collect logs using the following method:

### **Retrieving Logs from a Running Container**

1. Identify the running container:

```
docker ps | grep ssw-connector
```
2. Retrieve logs from the container:

```
docker logs {container-id} > connector-logs.txt
```

### **Compressing and Sending Logs**

1. Compress the log file:

```
tar -czvf connector-logs.tar.gz connector-logs.txt
```
2. Attach `connector-logs.tar.gz` to your support ticket or send it to support.

---

## **Helm Log Collection**

If you deployed the connector using Helm, use the following steps to collect logs:

### **Retrieving Logs from Kubernetes Pods**

1. List running pods:

```
kubectl get pods -n ssw-connector
```
2. Retrieve logs from the connector pod:

```
kubectl logs {pod-name} -n ssw-connector > connector-logs.txt
```

### **Compressing and Sending Logs**

1. Compress the log file:

```
tar -czvf connector-logs.tar.gz connector-logs.txt
```
2. Attach `connector-logs.tar.gz` to your support ticket or send it to support.

---

## **Additional Notes**

- Ensure that log collection is performed **before uninstalling** the connector.
- If experiencing issues, also collect **system logs** (Windows Event Viewer logs, MacOS Console logs, or Linux syslogs) for additional debugging.
- If the logs are too large, consider splitting them before sending.