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

# Discord Bot Hosting Setup guide

> Register, redeem a license, and get a Node.js or Python Discord bot running and receiving webhooks on EchoAuth Bothosting.

EchoAuth Bothosting runs your Discord bot in its own container on [bothosting-eu01.echoauth.dev](https://bothosting-eu01.echoauth.dev), with a billing dashboard for your account and credits, and a [Pterodactyl](https://pterodactyl.io)-based control panel for the server itself (console, files, and startup settings).

This guide walks through the full flow: creating an account, redeeming a license, creating a server, uploading your bot, and receiving webhooks.

## Quick start

1. [Create your account](#create-your-account) at [control-hosting.echoauth.dev/register](https://control-hosting.echoauth.dev/register)
2. [Redeem your license](#redeem-your-license) on the Store page to add credits
3. [Create a server](#create-a-server) — pick a runtime, name it, confirm
4. [Upload your bot files](#upload-your-bot-files) and set the startup variables
5. [Start the server and test your webhook](#start-the-server)

> [!NOTE]
>
> **Before you start, have ready:**
>
> * A license code (from a checkout email after buying hosting time)
> * Your bot's code — a Node.js `index.js` or a Python `app.py`, plus a Python `requirements.txt` if you have dependencies

## Create your account

Go to [control-hosting.echoauth.dev/register](https://control-hosting.echoauth.dev/register), create an account, and log in. You land on the Dashboard, which shows your server count and credit balance.

![EchoAuth Bothosting dashboard after login, showing 0 servers and 0.00 credits](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/01-dashboard.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=44a55bf2156a5be753248292b30a0ffa)

The dashboard right after logging in: 0 servers, 0 credits.

## Redeem your license

Open **Store** in the sidebar, then click **Redeem code** and enter your license code.

> [!TIP]
>
> 1 credit = 1 month of runtime on one bot container, and there's no limit on how many containers you can run — each one just needs enough credits to cover its monthly cost.

![Store page listing 1, 6 and 12 month license options and a Redeem code button](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/02-store.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=d22be1809910deac312b6cc81cc0708f)

The Store page, with the Redeem code button and the 1 credit = 1 month pricing.

![Redeem voucher code dialog with a license code filled in](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/03-redeem-filled.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=5e5333a498707f29e30f975978eef72b)

A license code entered in the Redeem voucher code dialog.

Once redeemed, the credit is added to your balance immediately and logged in your dashboard's Activity Logs.

![Redeem dialog showing a success message that 1.00 credit was added](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/04-redeem-success.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=a79d87f20c1c7ebed2268dbdcbecd925)

A successful redemption adds the credit to your balance right away.

## Create a server

Go to **Servers** and click **Create Server**. Give it a name and pick a **Language** — **Node.js** or **Python**. The location and resource plan (the **Bot Container** product: 0.3 vCPU, 256 MB RAM, 512 MB disk, 1 backup, 1 port, 1 credit/month) fill in automatically.

![Create server form with a name filled in, Node.js selected as the language, and the Bot Container plan details listed below](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/05-create-server.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=d2eca2740ee95cbaf0c73a1282542ab0)

The create-server form with Node.js selected, showing the Bot Container resource plan and price.

Click **Create server**. It's charged against your credit balance immediately and shows up as **Active** on the Servers page.

![Server card showing status Active, specification Node.js, resource plan Bot Container, and a price of 1.00 credits per month](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/06-server-active.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=8efdd67bc293af11210788908d4f7f12)

The new server, active and billed at 1.00 credit per month.

## Tour the control panel

Click the wrench icon on a server card to open it in the control panel at [controlpanel.echoauth.dev](https://controlpanel.echoauth.dev). The panel has **Console**, **Files**, **Databases**, **Schedules**, **Users**, **Backups**, **Network**, **Startup**, **Settings** and **Activity** tabs.

![Pterodactyl panel dashboard listing the newly created server](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/07-panel-dashboard.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=338631775f65f91731e5077d1d39bd43)

The control panel's server list after opening it from the dashboard.

A fresh server starts offline, with an empty file manager, waiting for your code.

![Console tab showing Server marked as offline, with Start, Restart and Stop buttons](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/08-console-offline.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=065bea5d4fd06fd09ed92566554b0b8f)

Console tab on a server that hasn't been started yet.

![Empty file manager showing the /home/container directory with no files](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/09-files-empty.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=1bb3ee4e94d3e98217f508c56db8fa4d)

The file manager on a freshly created server.

## Upload your bot files

Open the **Startup** tab first to see what your runtime expects.

> [tab] Node.js
>
> The startup command runs `${MAIN_FILE}` from `/home/container`. The **Main File** variable defaults to **`index.js`** — if your entry file has a different name, update this variable to match it (it can be `.js` or `.ts`).
>
> ![Startup tab showing the Node.js startup command and a Docker image dropdown set to Nodejs 26](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/10-startup-command.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=44f941a8fa4f4797b6d95348d78b4af3)
>
> Node.js startup command and Docker image selector.
>
> ![Main File startup variable with a default value of index.js](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/11-main-file.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=373d4355cf41af1cf989e5cc5e1f1d8b)
>
> The Main File variable, defaulting to index.js.
>
> There's no separate HTTP/HTTPS switch on the Node.js runtime — your code decides which one it listens on.

> [tab] Python
>
> The startup command always runs **`app.py`** from `/home/container` — name your entry file exactly that (the "App Py File" variable is descriptive only; it isn't substituted into the actual command).
>
> ![App Py File startup variable with a default value of app.py](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/19-python-main-file.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=0a2a66543153c5bf520179357ef7d1a5)
>
> The Python App Py File variable, which must stay app.py.
>
> The Python runtime also has a **Use HTTPS** switch: `0` = HTTP (the default) and `1` = HTTPS, in which case it looks for `cert.pem` and `key.pem` in your server directory and falls back to a self-signed certificate if they're missing.
>
> ![Use HTTPS startup variable with a toggle set to off, described as 0 = HTTP default, 1 = HTTPS](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/20-python-use-https.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=eb21f9df848c94c86d160a8158528de1)
>
> The Use HTTPS variable, available on the Python runtime only.
>
> > [!WARNING]
> >
> > The public HTTPS webhook proxy (below) expects your bot to be listening on plain HTTP. Leave **Use HTTPS** at `0` unless you're terminating TLS yourself and connecting directly to your port.
>
> List any packages your bot needs in **`requirements.txt`** — it's installed automatically on startup.

Open **Files**, click **New File** (or **Upload** to send a file from your computer), and add your code.

![New file editor with example webhook server code pasted in](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/12-new-file-editor.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=202c32cf6ecd7d4021aa46cd952ba328)

Writing bot code directly in the panel's file editor.

> [tab] Node.js
>
> ![File manager showing index.js in /home/container](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/13-files-index-js.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=ed83b61d895d03949133422c43be0ce0)
>
> index.js uploaded and ready to run.

> [tab] Python
>
> ![File manager showing app.py and requirements.txt in /home/container](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/21-python-files.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=8fb281d9be6156356abed7fcb9b1c0c6)
>
> app.py and requirements.txt uploaded and ready to run.

## Start the server

Go to **Console** and click **Start**. The panel pulls the Docker image, runs your startup command, and streams the output live.

![Console showing the startup script running and then Bot webhook server listening on port 25500](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/14-console-running.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=f118d50404f795183ec1dd8b0b1ef499)

Console output right after a Node.js server starts, with the bot logging that it's listening.

## Find your server's address and port

Open the **Network** tab. Your server's public address is `<hostname>:<port>` — for example `bothosting-eu01.echoauth.dev:25500`. Allowed ports are in the `25500`–`25650` range.

![Network tab with hostname bothosting-eu01.echoauth.dev and port 25500](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/15-network-tab.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=72e0554fadab4528c1cbd9a90b694380)

Network tab showing the server's hostname and assigned port.

## Receive webhooks

There are two ways to reach your bot from the outside:

| Format | URL | Notes |
| - | - | - |
| Direct HTTP | `http://bothosting-eu01.echoauth.dev:<port>/<path>` | Hits your container's port directly. |
| HTTPS proxy | `https://bothosting-eu01.echoauth.dev/hook/<port>/<path>` | TLS-terminated for you — requires your bot to be in HTTP mode (`Use HTTPS = 0`). |

```bash Direct HTTP theme={null}
curl -X POST http://bothosting-eu01.echoauth.dev:25500/webhook \
  -H "Content-Type: application/json" \
  -d '{"event": "ping"}'
```

```bash HTTPS proxy theme={null}
curl -X POST https://bothosting-eu01.echoauth.dev/hook/25500/webhook \
  -H "Content-Type: application/json" \
  -d '{"event": "ping"}'
```

Both return the same response from the example bot above:

```json theme={null}
{"status": "ok", "received": true}
```

...and both calls show up live in the console, together with the server's CPU, memory and uptime stats.

![Console showing two Webhook received log lines, plus Address, Uptime, CPU Load and Memory stat tiles](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/16-webhook-logs.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=9da134cabf2ca3125e723ba7374ebc3b)

Two webhook deliveries logged live in the console, with resource stats below.

The same thing working end-to-end on the Python runtime:

![Python console log showing the server starting, then two Webhook received lines from two different source IPs](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/22-python-webhook-logs.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=59e609ce210b24b4f1811e9e4300c632)

A Python bot logging a webhook received over both the direct port and the HTTPS proxy.

## Manage your server

Use **Restart** and **Stop** on the Console tab to control the running process.

### Backups

Your Bot Container plan includes 1 backup slot. Open **Backups** and click **Create Backup** to snapshot your files.

![Backups tab showing no backups currently stored, with a Create Backup button](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/17-backups-empty.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=9770bee3f420389ffac1676a6999477e)

No backups yet — the Backups tab on a new server.

![Backups list showing one backup created a few seconds ago, 1 of 1 backups used](https://mintcdn.com/echoauth/bj_a1F8xj-bFCqK4/images/bothosting-setup/18-backup-created.jpg?fit=max\&auto=format\&n=bj_a1F8xj-bFCqK4\&q=85\&s=7ccf5835b8ca402d763fac7997c4ffbe)

The first backup, created and ready.

### Renew your license

Buy or redeem another license code the same way as [Redeem your license](#redeem-your-license) — the added credits cover your server's next monthly billing cycle automatically.

## Troubleshooting

> [accordion] Server won't start
>
> Check the **Startup** tab: on Node.js, the **Main File** variable has to match your uploaded file's name exactly; on Python, your entry file has to be named `app.py`. A missing or misnamed file is the most common cause.

> [accordion] Port not reachable
>
> Use the exact hostname and port shown on the **Network** tab, not a port you picked yourself — only the allocated port (`25500`–`25650` range) is routed to your container.

> [accordion] Webhook not arriving
>
> Confirm you're using the right format for your bot's mode: the HTTPS proxy (`/hook/<port>/<path>`) only works when your bot is listening on plain HTTP (`Use HTTPS = 0` on Python). Double-check the path matches what your code expects — a typo there returns a 404 from your own server, not from EchoAuth.

> [accordion] Still stuck?
>
> Open **Support Ticket** in the sidebar with your server name and what you've tried.

## FAQ

> [accordion] How many servers can I run?
>
> As many as your credit balance supports — each Bot Container costs 1 credit (1 month) and is billed monthly from your balance.

> [accordion] Can I use TypeScript on the Node.js runtime?
>
> Yes — set **Main File** to a `.ts` file and it runs via `tsx` instead of `node`.

> [accordion] Do I need a requirements.txt on Python if I have no dependencies?
>
> No — it's optional. If present, its packages are installed on every startup; if your bot only uses the standard library, you can leave it out.

> [accordion] What happens if my license runs out?
>
> Redeem a new license code on the Store page before your credits reach zero — the added credits apply to your next billing cycle automatically.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.