> For the complete documentation index, see [llms.txt](https://docs.cstplus.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cstplus.org/documentation/troubleshooting/installation-issues.md).

# Installation Issues

{% hint style="success" %}
Most installation problems are caused by a wrong OS, a firewall blocking outbound connections, or a missing license key. Check these three things first before going deeper.
{% endhint %}

***

### Installer exits with "Unsupported architecture"

CST+ supports `x86_64` and `aarch64` only.

Run `uname -m` to check your architecture. If it returns something else (e.g. `armv7l`), your server is not supported.

***

### Installer exits with "Please run as root"

The installer must run as root. Add `sudo` before the command:

```bash
curl -fsSL https://install.vxdgroup-cloud.xyz/install.sh | sudo bash -s -- --key YOUR_KEY
```

***

### Installer hangs or fails to download

The server needs outbound HTTPS access to `install.vxdgroup-cloud.xyz`. Check:

```bash
curl -v https://install.vxdgroup-cloud.xyz/install.sh
```

If this times out, your VPS firewall or provider is blocking outbound traffic. Contact your VPS provider or temporarily disable the outbound firewall.

***

### "invalid ELF header" error on startup after install

This means the wrong `better-sqlite3` binary was installed. 

Fix: run the update command to pull a clean Linux build:

```bash
cstplus update --force
```

***

### Services not starting after install

Check systemd status for each service:

```bash
systemctl status cstplus-control
systemctl status cstplus-edge
systemctl status cstplus-web
```

View detailed logs:

```bash
journalctl -u cstplus-control -n 50
journalctl -u cstplus-edge -n 50
```

Common causes:

| Error in logs            | Cause                       | Fix                                                       |
| ------------------------ | --------------------------- | --------------------------------------------------------- |
| `EADDRINUSE`             | Port already in use         | Find and stop the process using the port: `lsof -i :3000` |
| `Cannot find module`     | Broken node\_modules        | Run `cstplus update --force`                              |
| `Integrity check failed` | Tampered or corrupted files | Run `cstplus update --force`                              |

***

### Panel is not accessible on port 3000

1. Verify the web service is running: `cstplus status`
2. Check your VPS firewall allows inbound on port 3000
3. If using a cloud provider (Hetzner, DigitalOcean, etc.), check their network security group rules as well

{% hint style="info" %}
The panel is bound to `0.0.0.0:3000` by default. If you set an IP allowlist in Settings before your IP was added, you may have locked yourself out. Reset it via SSH:

```bash
cstplus admin ip-allowlist clear
```

{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cstplus.org/documentation/troubleshooting/installation-issues.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.