Skip to content

lalaous/g2ray

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

11 Commits
 
 
 
 
 
 
 
 

Repository files navigation

@Kakoolnews

Automated VLESS proxy setup via GitHub Codespaces — works anywhere Codespaces is available.

Warning

Use a secondary GitHub account (not your main account) when forking and running this project. Running proxy servers may trigger GitHub's automated security systems or account restrictions.

Features

  • Fixed UUID — consistent identity across all sessions (no hardcoded credentials)
  • Latest Xray — automatically fetches the newest stable Xray-core release at build time
  • Multi-architecture — supports amd64, arm64, and armv7
  • Traffic sniffing — detects HTTP/TLS for smarter routing
  • BitTorrent blocking — prevents accidental P2P traffic through the proxy
  • Health checks — built-in Docker health monitoring
  • Custom UUID — optionally set VLESS_UUID env var to use your own UUID

Quick Start

  1. Fork this repository (use a secondary account)
  2. Click Code > Codespaces > Create codespace on main
  3. Wait 2–5 minutes for setup to complete
  4. Copy the VLESS link printed in the terminal

Import the Link

Use the generated VLESS link in any compatible proxy client:

Configuration

Custom UUID

Set the VLESS_UUID environment variable in your Codespace to use a specific UUID instead of an auto-generated one:

VLESS_UUID=your-custom-uuid-here

Xray Config

The proxy configuration is in .devcontainer/config.json. Key settings:

Setting Value Description
Port 443 Inbound VLESS port
Protocol VLESS Proxy protocol
Transport WebSocket Stream transport type
Path / WebSocket path
Sniffing enabled HTTP/TLS traffic detection

Codespace Quota

GitHub provides 120 free core-hours/month:

Cores Hours/Month
2 60
4 30
8 15

Stop your Codespace when not in use to conserve hours.

Compatible Networks

Tested with Shecan (free plan). If these IPs are reachable from your network, the proxy should work:

  • 94.130.13.19

Troubleshooting

Problem Solution
Codespace fails to start Delete it and create a new one
No VLESS link shown Check the terminal output for errors
Connection timeout Try a different datacenter or ISP
Port not accessible Ensure port 443 is set to public visibility

Project Structure

.devcontainer/
  Dockerfile          # Container image definition
  config.json         # Xray configuration template (UUID injected at runtime)
  devcontainer.json   # Codespace settings and lifecycle hooks
  entrypoint.sh       # Startup script: generates UUID, configures Xray, prints VLESS link
  install.sh          # Downloads and installs the latest Xray binary
docs/
  screenshot.png      # Terminal screenshot for reference

Support

Disclaimer

This tool is for educational and legitimate use only. Users are responsible for complying with local laws and regulations regarding proxy usage. The author is not responsible for any misuse.

License

This project is open-source. See the LICENSE file for details.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages

  • Shell 62.4%
  • Dockerfile 37.6%