---
title: "Troubleshoot"
description: "Troubleshooting guidance for TrustEdge installation, connectivity, configuration, and certificate issues."
source_url: https://dev.digicert.com/trustedge/troubleshoot.html
---

When using TrustEdge, you might encounter issues that can affect its operation. This section provides guidance on diagnosing and resolving common problems to restore expected operation.

## Common issues and solutions

### Installation errors

**Issue:**

When installing on Windows using WSL, installation fails with the error message: "System has not been booted with systemd as init system (PID 1). Can’t operate. Failed to connect to bus: Host is down."

**Solution:**

1. Ensure your WSL version is greater than 2. Check with:
   ```bash
   wsl --status
   ```
2. If the version is lower than 2, update it with:
   ```bash
   wsl --set-default-version 2
   ```
3. Launch the Ubuntu environment within WSL and gain root access:
   ```bash
   sudo su -
   ```
4. Edit the WSL configuration file:
   ```bash
   sudo nano /etc/wsl.conf
   ```
   Add the following lines:
   ```ini
   [boot]
   systemd=true
   ```
5. Save and exit (Ctrl+O and Ctrl+X), then proceed with the [install](https://dev.digicert.com/md/trustedge/install-and-configure.md).

### Connectivity problems

See [Network requirements](https://dev.digicert.com/md/trustedge/system-requirements.md).

### Configuration errors

**Issue:**

TrustEdge agent fails to start due to configuration file errors.

**Solution:**

1. Check the syntax and structure of your `trustedge.json` and `bootstrap_config.json` files.
2. Validate JSON files to ensure they are correctly formatted.
3. Verify file paths and credentials specified in the configuration files.

### Certificate issues

**Issue:**

Problems with certificate generation or CSR submission.

**Solution:**

Ensure that the keys and certificates are correctly specified in the command line or configuration files.

### Troubleshooting commands

**Check service status**

Verify the status of the TrustEdge agent service:

```bash
sudo systemctl is-active trustedge
```

**View logs**


> **Important**
>
> When running TrustEdge commands, log information is written to the terminal.


To view TrustEdge logs when running as a service:

```bash
sudo journalctl -f -u trustedge.service
```

**Test connectivity**

Test network connectivity to required endpoints:

```bash
ping one.digicert.com
curl -I https://one.digicert.com
```