A domain or subdomain pointed at your bot on MyBotCloud really serves HTTP traffic, not just sits registered. This post explains both kinds, from the dashboard, the CLI and the VS Code extension.
The two kinds
Every app can have one or more domains pointed at it (how many depends on your plan — Start: 1, Pulse: 5, Orbit: 10):
- Platform subdomain: active immediately, with a name picked for you from a fixed pool of countries, states and territories (
argentina.mybotcloud.io,nebraska.mybotcloud.io, that sort of thing). You cannot type your own name here — on purpose: a free-text subdomain under our own domain would let anyone grab a short, attractive name or spell something designed to impersonate another brand. Don't like the one you got? In the dashboard's Domain tab, click Draw another (in the CLI or the extension, remove it and add a new one); the old address stops working the moment you do. - Custom domain (
bot.example.com): starts pending. To prove you own it, create a DNS TXT record at_mybotcloud-challenge.bot.example.comwith the value the platform shows you, then verify. DNS propagation can take a few minutes — if verification does not find the record yet, just try again shortly after.
It really serves HTTP now
Where routing is turned on (it is, in production), an active domain is not just bookkeeping: a request to it is proxied straight to your app's own HTTP server, on the port you set. If your bot only talks to Discord and makes outbound connections, none of this matters to you — skip it. If it also runs a small web server (a status page, a webhook receiver, a dashboard of its own), this is what makes yourbot.mybotcloud.io actually answer.
One limitation worth knowing: adding a domain or changing its port takes effect on the app's next deploy, not instantly on a plain restart. After creating a domain or changing its port, redeploy from the Update tab (or mybotcloud deploy / a git push if you use GitHub integration) to make it live.
Where to manage them
- Dashboard: open an app, go to its Domain tab — draw a subdomain, add a custom domain, see the DNS record to verify, edit the port, or remove a domain.
- CLI:
mybotcloud domains add --sub --port 3000 mybotcloud domains add --host bot.example.com --port 3000 mybotcloud domains verify bot.example.com mybotcloud domains port bot.example.com 8080 mybotcloud domains list mybotcloud domains remove bot.example.com - VS Code extension: right-click an app (or the command palette) → Add a domain, Verify domain (DNS), Remove domain.
Does your bot also need somewhere to keep data? See PostgreSQL database: how to use it.
Still stuck? Open a ticket in Support in the dashboard.