Skip to main content
EchoAuth Bothosting runs your Discord bot in its own container on bothosting-eu01.echoauth.dev, with a billing dashboard for your account and credits, and a Pterodactyl-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 at control-hosting.echoauth.dev/register
  2. Redeem your license on the Store page to add credits
  3. Create a server — pick a runtime, name it, confirm
  4. Upload your bot files and set the startup variables
  5. Start the server and test your webhook
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, 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

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

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

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

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

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

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. The panel has Console, Files, Databases, Schedules, Users, Backups, Network, Startup, Settings and Activity tabs.
Pterodactyl panel dashboard listing the newly created server

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

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

Empty file manager showing the /home/container directory with no files

The file manager on a freshly created server.

Upload your bot files

Open the Startup tab first to see what your runtime expects.
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

Node.js startup command and Docker image selector.

Main File startup variable with a default value of index.js

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

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

File manager showing index.js in /home/container

index.js 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

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

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

Receive webhooks

There are two ways to reach your bot from the outside:
Both return the same response from the example bot above:
…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

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

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

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

The first backup, created and ready.

Renew your license

Buy or redeem another license code the same way as Redeem your license — the added credits cover your server’s next monthly billing cycle automatically.

Troubleshooting

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.
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.
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.
Open Support Ticket in the sidebar with your server name and what you’ve tried.

FAQ

As many as your credit balance supports — each Bot Container costs 1 credit (1 month) and is billed monthly from your balance.
Yes — set Main File to a .ts file and it runs via tsx instead of node.
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.
Redeem a new license code on the Store page before your credits reach zero — the added credits apply to your next billing cycle automatically.