-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Hosting your bot
You will need a VPS (or dedicated server) first. Check out the list at Where to host Telegram Bots if you don't have one already.
Your login details should contain
- The IP address of your server
- Your username (usually
root) - Your password
You should also receive some information on the type of server you got, including Operating System, RAM, storage and monthly traffic.
Once you received that information, you can connect to the server via SSH.
Note that although the explanations below mention entering your password, it is strongly recommended to authenticate using a SSH public key instead of the password. You can read this explanation on how to generate keys and send the public key to the server, or check your VPS provider's documentation.
Run the following command in the terminal and replace <user> with your username and <ip> with your servers IP address:
ssh <user>@<ip>
Confirm that you want to trust the host and enter the password if you are asked to do so.
Install puTTY and start it.
In the field Host Name (or IP address) enter the IP address of your server. As the connection type, select SSH and set Port to 22. You can save these settings my entering a name in the field below Saved Sessions and clicking Save. Then, click Open and enter your username and password when asked to do so.
First, install the Python package manager pip.
apt-get update && apt-get install python3-pip
Now, install the python-telegram-bot library:
pip3 install python-telegram-bot
Finally, confirm the installation:
python3 -c "import telegram;print(telegram.__version__)"
Of course, this is the easy way; the correct way (especially if you have multiple Python projects on your server) is to install a virtual environment (like pipenv or poetry) first.
Now you can upload your bot to the server. There are multiple ways to do that, one way is to use FileZilla. Install it (if you're on Linux, chances are you already have it) and start it. Open the Server Manager and create a new server with the button on the left. Give it a nice name, then go to the right and fill in the fields:
- Server: Your servers IP address
- Port: 22
- Protocol: SFTP
- Connection type: Normal
- Username: Your username
- Password: Your password
Now, click Connect. You will probably see the /root directory (your user's home directory) on the right and your local files on the left. Create a directory for your bot and upload all the files needed by your bot into that directory.
To run your bot, connect to your server again via SSH (or go back to the connection) and cd into the directory you created. You could now immediately start the bot, but then it would stop working once you disconnect from the server. There are again several ways to make sure that doesn't happen:
- Use a terminal multiplexer like
screenortmux. - Run your bot as a systemd service.
screen is called a "terminal multiplexer". It creates virtual terminals that you can attach to and detach from and that can run processes without you being logged in.
Create a new screen and attach to it:
screen -S mybot
Start the bot:
python3 bot.py
Detach from the screen by holding CTRL and pressing A, then D. You can now disconnect from the server by typing exit if you want.
To re-attach to the screen after you logged back in:
screen -r mybot
or
screen -d -r mybot
A known alternative to screen is tmux.
Choosing this option will mean that your Python program will be running in the background. Another upside to this option is that you can set it up to start at system boot, which means that if you reboot your server (e.g. to apply system upgrades), your bot will start automatically afterwards.
- Install
python-dotenv. - Create the
.envfile and put your bot-related environment variables in there (you didn't put your bot token right into your code, hopefully!). If you're using Git, make sure.envis in.gitignoreso it doesn't get checked in. - Follow e.g. this tutorial to run your Python script as a service. If you're using a virtual environment (see this external article for details), you have to locate the Python executable first. To do that, activate the virtual environment on the remote server and enter
which pythonin your bash console. You will get a path to the Python instance you will need to use when configuring systemd.
Steps 1 and 2 are optional if you're not using any virtual environment, but it's better to go through them anyway because if you set the environment variables manually, they will be lost after system reboot.
If you plan on hosting multiple bots on your server, it's recommended to use virtualenv. It allows you to install and upgrade Python modules via pip for one project, without worrying how it affects other projects on the server. Read this external article for more information.
Learn about how to use a webhook for your bot in this article.
You might also read the article on Performance Optimizations if you didn't read it yet.
Wiki of python-telegram-bot © Copyright 2015-2025 – Licensed by Creative Commons
- Architecture Overview
- Builder Pattern for
Application - Types of Handlers
- Working with Files and Media
- Exceptions, Warnings and Logging
- Concurrency in PTB
- Advanced Filters
- Storing data
- Making your bot persistent
- Adding Defaults
- Job Queue
- Arbitrary
callback_data - Avoiding flood limits
- Webhooks
- Bot API Forward Compatiblity
- Frequently requested design patterns
- Code snippets
- Performance Optimizations
- Telegram Passport
- Bots built with PTB
- Automated Bot Tests