wulabing/xray_onekey

Xray 基于 Nginx 的 VLESS + XTLS 一键安装脚本

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 11 minutes ago
Added to GitGenius on September 7th, 2026
Created on December 5th, 2017
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 3,465
Total Stargazers: 9,252 (+0)
Total Subscribers: 206 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.5 days
Mean response time: 367.6 days
90th percentile: 1112.9 days
Tracked items: 18

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 9% of issues opened in the past year have been closed. Three people close 94% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Fix (1)

Most active issues this week

Detailed Description

xray_onekey is a shell script that automates the installation and configuration of Xray with VLESS and XTLS protocols using Nginx as a reverse proxy.

The script addresses the need to quickly deploy Xray proxy infrastructure by automating server setup and configuration. It supports multiple protocol combinations including VLESS with TCP, TLS, and Nginx, with optional WebSocket fallback modes. The tool handles the integration of Nginx in front of Xray and provides flow control options through xtls-rprx-vision. Users must prepare a domain name with an A record and have wget installed before running the installation.

The script is intended for users with Linux fundamentals, networking knowledge, and hands-on server administration experience. It suits projects requiring privacy-focused proxy infrastructure with modern protocol support. The README notes that nested TLS caused by Nginx placement may lead to connection blocking and recommends REALITY as an alternative approach, directing users to a separate Docker-based implementation for that use case.

Development activity shows the project maintains active community engagement through Telegram discussion and announcement channels. The maintainer acknowledges providing only limited direct support, instead encouraging users to seek help from community members in the group. The project has received sponsorship recognition, indicating ongoing interest in its maintenance and development.