Guides
Step-by-step answers to one task at a time, with the exact config.
- aiogram bot hosting: how to deploy an aiogram 3 botAn aiogram 3 bot needs one process that never stops, the token in an environment variable, state kept outside memory and a clean exit on SIGTERM. On Livops you push a repository with bot.py and requirements.txt, and it runs for 19 credits a month (19,000 so'm), polling or webhook.
- App not listening on $PORT: why the health check failed after deployThe platform started your app, tried the port it gave it, and nothing answered in time. Almost always the app listens on its own fixed port instead of the PORT variable, listens on localhost (127.0.0.1) instead of 0.0.0.0, or crashed or was still starting when the check gave up. Listen on 0.0.0.0 and the port in PORT, and it passes.
- Conflict: terminated by other getUpdates request — how to fix itTelegram is telling your bot that another process called getUpdates with the same token and took the connection over. Two copies of the bot are polling at once: stop the other one (usually the copy still running on your computer or an old server), or get a new token from @BotFather, and the error stops.
- Deploy from Claude Code: connect Livops over MCPRun one command, claude mcp add --transport http livops https://livops.uz/api/mcp, then sign in through /mcp. From then on Claude Code can list your projects, deploy, read the build log, explain a failure and roll back, as you and only in the team you picked.
- Deploy from Codex CLI: connect Livops over MCPAdd a [mcp_servers.livops] table with url = "https://livops.uz/api/mcp" to ~/.codex/config.toml and run codex mcp login livops. Codex can then deploy, read build logs, explain a failure and roll back, and with default_tools_approval_mode = "writes" it asks before anything that changes.
- Deploy from Cursor: connect Livops over MCPAdd Livops to ~/.cursor/mcp.json with just its address, https://livops.uz/api/mcp, and sign in through the browser. Cursor's agent can then deploy, read build logs, explain a failure and roll back, and it asks you before each tool call unless you change that.
- Deploy from VS Code: Copilot agent sessions and the Livops MCP serverIn VS Code, add Livops to the workspace's .mcp.json as an http server at https://livops.uz/api/mcp, select the Copilot harness in a chat session, and complete the sign-in when prompted. Copilot can then deploy, read build logs, explain a failure and roll back, and each tool call still needs your approval.
- DisallowedHost: Invalid HTTP_HOST header — Django's 400 Bad RequestDjango received a request for a host name that is not in ALLOWED_HOSTS, so it answered 400 Bad Request. Add the domain the site is served on to ALLOWED_HOSTS, without https:// and without a port, or read the list from an environment variable, and redeploy.
- Error: listen EADDRINUSE: address already in use — how to fix itYour server tried to listen on a port that another process on the same machine already holds. On your computer, stop the old process, usually a dev server still running in another terminal. In a deploy, it almost always means the app starts its server twice, or two processes in one container ask for the same port.
- exec format error in Docker: the image was built for another CPUThe kernel refused to run the container's program because it is not an executable for this machine: almost always a binary or image built for arm64 (an Apple Silicon Mac) running on an amd64 server, or the reverse. Build for the server's platform with --platform linux/amd64, or as a multi-platform image; if the file is a script, give it a #! line.
- grammY bot deploy: polling, webhooks and hostingDeploy a grammY bot as one always-on Node.js process: bot.start() for polling, or webhookCallback() behind an HTTP server, with bot.stop() on SIGTERM. On Livops a repository with grammy in package.json runs as a bot from every push, for 19 credits a month (19,000 so'm).
- Gunicorn "Worker failed to boot": what it means and how to fix itGunicorn's worker could not load your application, so the master process shut down. The cause is the Python traceback printed just above the message: most often a missing package or variable, or a wrong module:variable path in the gunicorn command. Fix what the traceback names and the workers boot.
- JavaScript heap out of memory during next build: how to fix itNode's JavaScript heap reached its limit while Next.js was building, and V8 stopped the process. Raise the heap limit with NODE_OPTIONS=--max-old-space-size, staying below the memory the build really has, and cut what the build holds in memory: source maps, type checking during the build, and heavy dependencies.
- Laravel: No application encryption key has been specifiedLaravel's encrypter has no key, because the APP_KEY environment variable is empty on the server. Generate one with php artisan key:generate --show, set it as APP_KEY where the app runs, clear any cached configuration, and keep the same key from then on.
- MCP server for deploying apps: what to look forAn MCP deploy server lets Claude Code, Cursor, Codex or Copilot deploy, read logs and roll back on your hosting account. Judge one by how it signs in, how far a key reaches, whether its tools say which ones change things, and what you can see and revoke afterwards. Vercel, Render, Railway, Netlify and Livops all ship one.
- ModuleNotFoundError: No module named — after a deployPython searched sys.path and could not find the module you import. After a deploy that almost always means the package is not in requirements.txt, is listed under a different name than the one you import, or the start command runs a Python that the packages were not installed into.
- npm ERR! code 1: why the build failed with exit code 1npm ERR! code 1 (npm error code 1 in newer npm) only says that a script npm ran exited with code 1. The real error is printed above it: usually a compile or type error, a lockfile out of sync with package.json, or a dependency whose install script failed. Find the first error line above code 1, fix that, and the build passes.
- python-telegram-bot hosting: deploying a v22 botA python-telegram-bot bot runs as one Application: run_polling() for polling, run_webhook() with the webhooks extra for a webhook. Both stop cleanly on SIGTERM. On Livops it runs from a push with bot.py and requirements.txt for 19 credits a month (19,000 so'm).
- Telegraf bot hosting: deploying a Telegraf 4 bot on Node.jsA Telegraf bot is one Node.js process: bot.launch() for polling, or bot.webhookCallback() behind an HTTP server for a webhook, with bot.stop() on SIGTERM. On Livops a repository with telegraf in package.json is run as a bot from every push, for 19 credits a month (19,000 so'm).
- Telegram bot webhook vs polling: which one to usePolling means your bot asks Telegram for updates in a loop; a webhook means Telegram POSTs each update to your HTTPS address. Polling is simpler and needs no address; a webhook needs HTTPS but no always-running loop. A bot uses one or the other, never both. On Livops both run for the same 19 credits a month.
- What Livops's AI assistant does when a build failsWhen a build fails on Livops, the previous version keeps running and one button asks the assistant why. It reads the failed build's log and your project's commands, says what went wrong and how to fix it, and may offer one fix as a button that changes nothing until you press it. It never deletes, never sees variable values, and does not edit your code.