---
title: "Deploy Telegram MTProxy (Private Telegram Proxy)"
description: "Private Telegram MTProto proxy. One click, zero config, stable tg:// link"
category: "Other"
url: https://railway.com/deploy/telegram-mtproxy-private-telegram-proxy
---

# Deploy Telegram MTProxy (Private Telegram Proxy)

Private Telegram MTProto proxy. One click, zero config, stable tg:// link

**[Deploy Telegram MTProxy (Private Telegram Proxy) on Railway](https://railway.com/template/telegram-mtproxy-private-telegram-proxy)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/telegram-mtproxy-private-telegram-proxy/manifest.json

- **Creator:** Nick K's Projects
- **Category:** Other
- **Total deploys:** 1

## Template content

### MTProxy https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/telegram.svg

- **Image:** telegrammessenger/proxy:1.4

## Documentation

# Deploy and Host Telegram MTProxy on Railway

Telegram MTProxy is the official MTProto proxy server from Telegram. It lets you run your own private Telegram proxy so you and your users can connect to Telegram reliably from networks where it is throttled or blocked. This template deploys the official `telegrammessenger/proxy` image with a persistent secret, so your `tg://proxy` link keeps working across restarts and redeploys.

## About Hosting Telegram MTProxy

Hosting an MTProto proxy normally means renting a VPS, opening a port, generating a secret, and keeping the process alive. On Railway this template does it in one click: the proxy listens on port 443 behind a Railway TCP proxy, a 32-character hex `SECRET` is generated once and stored on a volume at `/data`, and the container auto-restarts on failure. After deploy, open the service → Settings → Networking to read your public TCP proxy host and port, then share `tg://proxy?server=&amp;port=&amp;secret=`. No SSH, no firewall rules, no config files. Typical usage runs on a few MB of RAM, so it fits comfortably in Railway's Hobby plan.

## Common Use Cases

- Give friends, family or a community a private, fast Telegram proxy that you control
- Bypass ISP throttling or regional blocks on Telegram without a third-party VPN
- Run a proxy for a Telegram bot or channel audience in a restricted region
- Promote a channel via the proxy's optional sponsored-channel tag (see docs)

## Dependencies for Telegram MTProxy Hosting

- Official Docker image `telegrammessenger/proxy:1.4`
- A Railway volume mounted at `/data` (keeps the secret and Telegram config cache)
- A Railway TCP proxy on port 443 (created automatically by this template)

### Implementation Details

Build your share link from the TCP proxy values on the service's Networking tab:

```text
tg://proxy?server=&amp;port=&amp;secret=
```

To use a fake-TLS / "dd" secret in newer clients, prefix the secret with `dd`. To rotate the secret, change the `SECRET` variable and redeploy — all previously shared links will stop working.

## Why Deploy Telegram MTProxy on Railway?


Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Telegram MTProxy on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.


## Similar templates

- [Rocky Linux](https://railway.com/deploy/rocky-linux) — Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀
- [Foundry Virtual Tabletop](https://railway.com/deploy/X5tR6G) — A Self-Hosted & Modern Roleplaying Platform
- [Letta Code Remote](https://railway.com/deploy/letta-code-remote) — Run a Letta Code agent 24/7. No inbound ports, just deploy.

Open this page in a browser: https://railway.com/deploy/telegram-mtproxy-private-telegram-proxy
