yeahwu/v2ray-wss

A proxy script with multiple protocols.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 18th, 2026
Created on July 15th, 2021
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 600
Total Stargazers: 3,743 (+0)
Total Subscribers: 27 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 16.4 hours
Mean response time: 5.2 days
90th percentile: 22.3 days
Tracked items: 7

Most active contributors

Sign in to see contributor activity.

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

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.

Detailed Description

v2ray-wss is a proxy installation script that supports multiple protocols including V2Ray, Shadowsocks, Reality, and Hysteria2.

The script automates the deployment of various proxy protocols on Linux servers. It addresses the need for flexible proxy setup by offering different options suited to different scenarios: users without a domain can deploy Reality and Hysteria2 proxies, while those with a domain can set up V2Ray with WebSocket over SSL and HTTPS forward proxies. The script handles the underlying configuration and installation complexity, storing client configuration files in standard locations for each protocol.

The tool targets users setting up proxy infrastructure on budget VPS providers. It supports Debian, Ubuntu, and CentOS distributions, including ARM platforms. The choice of protocol depends on user circumstances: Reality and Hysteria2 require no domain registration, while V2Ray with WSS and HTTPS forward proxies require a registered domain. The README emphasizes checking server firewall settings as a troubleshooting step for connection issues.

Development activity shows consistent maintenance with updates addressing user-reported issues and platform compatibility. The project includes uninstall documentation alongside installation guidance, indicating attention to the full lifecycle of deployments. Configuration is straightforward, with the script automatically generating and storing protocol-specific client configurations in predictable file locations for easy retrieval and client setup.