explaingit

hiifeng/v2ray-for-doprax

8,347DockerfileAudience · generalComplexity · 3/5Setup · moderate

TLDR

A ready-to-deploy Docker configuration for running a free V2ray proxy server on Doprax.com, using Nginx and WebSocket over HTTPS to route traffic through a server and bypass network restrictions at no cost.

Mindmap

mindmap
  root((v2ray-for-doprax))
    What it does
      V2ray proxy server
      Free cloud hosting
    Setup
      Fork on GitHub
      Edit UUID
      Import to Doprax
    Tech
      Nginx
      WebSocket TLS
      VMess or VLess
    Client setup
      V2ray client app
      Custom config
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Deploy a free V2ray proxy server on Doprax.com by forking the repo, editing one UUID in the Dockerfile, and importing it into your Doprax account.

USE CASE 2

Bypass network restrictions at no cost using the Doprax free tier and a V2ray client app on your device.

USE CASE 3

Set up a VMess or VLess proxy endpoint disguised as normal HTTPS web traffic using the Nginx WebSocket setup.

USE CASE 4

Get a continuously running proxy server without managing your own VPS or paying for hosting.

Tech stack

DockerfileNginxV2ray

Getting it running

Difficulty · moderate Time to first run · 30min

Requires a free Doprax.com account and a V2ray client app on your device, the documentation is primarily in Chinese.

In plain English

This project provides a ready-to-deploy configuration for running V2ray on the free tier of Doprax.com, a cloud hosting platform. V2ray is a proxy tool that routes internet traffic through an intermediary server to bypass network restrictions or access blocked content. The project is primarily documented in Chinese and targets users who want a no-cost way to run such a proxy without managing their own server infrastructure. The setup uses Nginx as the front-facing web server, with WebSocket connections and either VMess or VLess protocols for the proxy traffic, all wrapped in TLS encryption. The combination is designed to make the proxy traffic look like ordinary HTTPS web traffic from the outside. Deployment follows a fork-then-import pattern: you fork the repository to your own GitHub account, then import it into Doprax.com. From there, you edit a Dockerfile to replace a placeholder UUID with a newly generated one (the UUID acts as an access credential) and set a custom URL path for the proxy endpoints. Once deployed, you configure a V2ray client application on your own device using the server address and the credentials you set. The README notes that the service on Doprax is advertised by the platform as having no bandwidth cap and staying running continuously, though it acknowledges speed may be slower compared to other free hosting options. The author asks users not to abuse the service, noting that account bans are the user's own responsibility. Support is via Telegram.

Copy-paste prompts

Prompt 1
Walk me through forking v2ray-for-doprax, generating a new UUID, editing the Dockerfile, importing into Doprax, and connecting my V2ray client, step by step.
Prompt 2
Generate a V2ray client configuration JSON for a VMess endpoint on a Doprax-hosted server, I will fill in the UUID and hostname.
Prompt 3
Explain in plain English how Nginx plus WebSocket plus TLS makes proxy traffic look like normal HTTPS to outside observers.
Prompt 4
I deployed v2ray-for-doprax on Doprax but my V2ray client can't connect, what are the most common configuration mistakes and how do I debug them?
Open on GitHub → Explain another repo

← hiifeng on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.