Skip to main content
Open Configurations → Telegram proxy in Flow Studio. Here you create separate Telegram connections on your nodes. Each record and link relates to a single server; the canvas, shared subscription and automatic balancing between records are not used.

Select the mode and prepare the node

| Mode | What to Prepare | What to Get to | User |---|---|---| | MTProto | Node address and free public TCP port | Address, port, secret and link/QR Telegram | | WEB | Managed domain of selected node, straight A/AAAAAA without CDN proxing, free TCP 80/443 | HTTPS input and tg://webproxy link for compatible | client You need a Linux node x86_64 with Docker Engine, Python 3.8+ and SSH root or sudo -n. Remnawave is optional. Ports must be open both on the node and from the provider. Installation does not free occupied ports by stopping other people’s services. For WEB add a domain in advance to Nodes → Domains and TLS: Instruction for domains. The proxy master offers only bindings of the selected node. DNS is checked against the stored IP node; a separate public address for the NAT may not pass this verification. The certificate for WEB is issued when installed via Caddy.

Create and install

  1. Open the creation of a proxy and select the mode.
  2. Select the node, specify the name and parameters of the address.
  3. For WEB select a domain, check the DNS and set up a public site: a template from the SelfSteal library or your text page.
  4. If necessary, specify the sponsor tag: 32 hexadecimal characters from @MTProxyBot. This is not an ID or a channel name.
  5. Check the result. Save settings leaves a draft; Save and install also starts the installation on the node.
  6. Wait for the result of the operation and perform a connection check.
If the DNS is not ready, you can save the draft. Save and install for WEB requires successful verification; when you start the installation, the DNS is checked again from the node. If the start after saving failed, a second attempt in the same wizard updates the created record. The site WEB is installed along with a proxy. You don’t need to create a separate SelfSteal record and a second HTTPS server for it. The name and description of the template change the metadata of the page; the visible text depends on the chosen template. The sponsor’s channel display depends on Telegram.

Reference, QR and Changes

The link contains a secret of access. Get it only for the right users. The right to view the list does not give you the right to obtain a secret: the issuance of a link requires connection_units.apply and is recorded in the audit. After editing, the saved settings may differ from those that work. Set/Apply deploys the changes, and the link and QR use the previous configuration before successful application. Transfer to another node to create a new record.

Status of operation and verification

The card shows the stage, the duration, the age of the installer’s response and the output activity of the build. No response for more than 30 seconds and no new assembly output for more than two minutes are displayed separately. The live installer does not guarantee the progress of the build. For old operations, phase information may not be available. Verification distinguishes between missing, stopped and unchecked container. Status Service run requires local availability of MTProxy and confirmation of connections to Telegram; for WEB also check relay and certificate. After five minutes, the result requires an update. Updating the list does not in itself trigger a new SSH check. Before issuing a link, check Telegram from the user’s network: connection, messages and necessary calls. Server status does not confirm all these scenarios. For WEB be sure to check the right versions of customers: support for this transport varies. If the link does not open, you can manually specify the domain and secret in the compatible client.

Stopping, rolling back and removing

Stop it. If you make a new configuration error, the plant tries to return the previous container, and if you make an uncompleted operation, you don’t succeed: check the report and the status before you restart it. To manually return the settings, restore the previous values and apply them again. Delete removes the park record and its secret regardless of the availability of SSH. After Attempting Installation, Cleaning Containers, Configuration and Condition Certificates on the node are executed separately in the background. Disappearance of the card does not confirm clearance. Inaccessible server: after the connection is restored, check it and delete it the remaining runtime manually if the background operation fails. Deleting the record is not a reversible rollback. active, competitive action may be rejected. Blocks the removal of the associated node. The availability of features depends on the version installed; code verification is not a substitute for checking your infrastructure.