novnc/websockify

Websockify is a WebSocket to TCP proxy/bridge. This allows a browser to connect to any application/server/service.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 39 minutes ago
Added to GitGenius on September 15th, 2026
Created on January 12th, 2011
Open Issues & Pull Requests: 47 (+0)
GitHub issues: Enabled
Number of forks: 836
Total Stargazers: 4,458 (+0)
Total Subscribers: 133 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 20.6 hours
Mean response time: 11.1 days
90th percentile: 30.7 days
Tracked items: 33

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 15
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 331 days
Stale 30+ days: 13
Stale 90+ days: 12

Recent activity

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

Top labels

  • bug (4)
  • feature (3)
  • documentation (2)
  • duplicate (1)
  • question (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Websockify is a WebSocket to TCP proxy that enables browsers to connect to any application or server by translating WebSocket traffic to normal socket traffic. The tool accepts WebSocket handshakes, parses them, and forwards traffic bidirectionally between clients and target services.

The core problem websockify solves is the inability of web browsers to establish direct TCP connections to arbitrary services. Browsers can only communicate via WebSocket or HTTP protocols. Websockify bridges this gap by running as a proxy that accepts incoming WebSocket connections from browsers and translates them into standard TCP socket connections to backend services. This allows any networked application to be accessed through a web interface without modifying the application itself.

Websockify suits projects where you need to expose non-web services to browser clients, such as remote desktop applications, terminal emulators, or legacy services. It is particularly useful when you want to avoid modifying the target application or when the application already has a working TCP interface. The tool supports encrypted connections via the wss:// URI scheme using SSL certificates, with options for both self-signed and commercial certificates. It also provides daemonization support for running as a background process and automatic SSL detection by examining the first byte of client data.

The project maintains clear documentation on certificate configuration and connection handling, including specific guidance for browser certificate trust scenarios across multiple ports.