> For the complete documentation index, see [llms.txt](https://hellbot-docs.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hellbot-docs.gitbook.io/docs/string-session/repl.it.md).

# REPL.it

Guide to generate a session string using Repl.it

### :link: Follow these steps carefully to generate string sessions:

* Open the repl link from below.
* Click on the Play Button.
* Wait for requirements to finish.
* Do human verification.
* Select the type of session.
* *<mark style="color:purple;">**`Telethon:`**</mark>*
  * Fill API ID, API HASH, Phone number (with country code).
  * Paste the OTP received on Telegram.
  * If You have Enabled 2-Step Verification then fill your password.
  * Your Telethon Session Will be saved in your Telegram Saved Message.
* *<mark style="color:purple;">**`Pyrogram:`**</mark>*
  * Fill API ID, API HASH, Phone number (with country code).
  * Paste the OTP received on Telegram.
  * If You have Enabled 2-Step Verification then fill your password.
  * Your Pyrogram Session will be saved in your Telegram Saved Message.
* *<mark style="color:purple;">**`Instagram:`**</mark>*

  * Fill instagram username and password.
  * If asked for OTP check yout email and fill up the OTP from there.
  * Your Instagram Session will be displayed on the screen.
  * Copy it carefully and Do Not Share With Anyone!
  * Using a fake account is recommended.

{% embed url="<https://replit.com/@TheHellBot/HellBot?v=1>" %}
HellBot's Official Repl.it
{% endembed %}

## <mark style="color:red;">Error while Generating Session</mark>

Due to telegram's new and updating privacy & policies, many users have been facing a problem while generating the session from the repl. This is because telegram detects so many requests from the same network and it refuses to connect through it.  And since hellbot only works with its personal session that is known as HellBot Session that can only be generated using HellBot's official repl, you won't be able to generate any session whatsoever.

### Using Terminal

This issue can be bypassed when you're using a VPS or RDP or a Local Machine to host hellbot.  You can simply run a python script in the terminal.

`python3 hell_string.py`

Using this command mentioned above you can run the session generator file and generate hellbot session which will be automatically saved in your telegram's saved message. Then you only need to copy that session and paste it in your config vars.

### Heroku

If you're using heroku or any other platform to deploy hellbot, you can always generate the session in their terminal. Here we will talk about Heroku as it is widely in use.

* Deploy the bot without filling up the HELLBOT\_SESSION variable. You can fill up anything randomly just to bypass the required field.
* Now, go to the app's dashboard and click on "More" button.
* There you'll get an option "Run Console", click on that.
* Now, it'll ask for an command you can copy this and paste it in that input box.

`python3 hell_string.py`

* It'll start the session generator and you'll be able to generate the HellBot Session.
* The session will get saved in your telegram's saved messages. Copy that session.
* Now go to settings tab > Reveal Config Vars > HELLBOT\_SESSION
* Paste the session in that field.
* Now you can turn on the dynos and enjoy your HellBot.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hellbot-docs.gitbook.io/docs/string-session/repl.it.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.