tobychui/zoraxy
Zoraxy
Zoraxy is a network administration tool centered on HTTP reverse proxy management. It provides a centralized graphical interface for routing web traffic from public domains to internal backend services, utilizing a Go-based proxy to intercept and forward requests.
The project extends beyond standard web routing by offering a browser-based SSH interface for remote server administration and command execution. It also supports transport-layer TCP and WebSocket forwarding to manage non-HTTP traffic between external clients and internal ports.
Broad capabilities include automated TLS certificate lifecycle management via ACME, network access control using CIDR-based filtering, and user authentication integration. The system further incorporates network infrastructure tools for IP and port scanning, service availability monitoring, and traffic statistics analysis.
Features
- HTTP Reverse Proxies - Provides a centralized graphical interface for managing HTTP reverse proxies to route public domains to internal services.
- Traffic Routing - Offers a centralized graphical interface for defining and managing web routing and traffic forwarding rules.
- Multi-Backend Routing - Maps public domain requests to specific internal IP addresses and ports for backend service delivery.
- Stateless Proxies - Utilizes a stateless proxy architecture to route traffic based on host headers and path patterns.
- HTTP Request Forwarders - Ships a Go-based proxy that intercepts and forwards incoming HTTP requests to internal backend servers.
- Proxy Traffic Management - Forwards HTTP, WebSocket, and TCP stream traffic from external clients to internal backend servers.
- Traffic Routing - Directs incoming web requests to internal backend services using flexible proxy configurations.
- SSL/TLS Certificate Management - Provides automated generation and renewal of SSL/TLS certificates via the ACME protocol for multiple domains.
- Remote Server Administration Tools - Offers tools for managing remote Linux systems through a browser-based shell interface.
- SSH Web Terminals - Provides a browser-based SSH interface for secure remote command execution and server administration.
- Dynamic Configuration Engines - Implements a control plane that updates proxy routing rules in real-time without requiring service restarts.
- Transport Layer Forwarding - Proxies non-HTTP network traffic at the transport layer between external clients and internal destination ports.
- Browser-Based - Allows administrators to open secure SSH sessions to remote servers directly within a web browser.
- Layer 4 TCP Routing - Directs raw TCP traffic at the transport layer, bypassing the HTTP layer for non-web services.
- TCP and UDP Forwarders - Forwards raw TCP and WebSocket streams between external clients and internal server ports.
- Network-Based Access Controls - Restricts network traffic access based on IP addresses, CIDR blocks, and country-level blacklists.
- External Authentication Integrations - Secures backend services via Basic Auth, OAuth2, reCAPTCHA, and external forward-authentication providers.
- HTTPS Enforcements - Automatically redirects incoming unencrypted HTTP requests on port 80 to secure HTTPS connections.
- Network Traffic Filtering - Provides network traffic filtering capabilities based on IP addresses and CIDR blocks to control access.
- SSL Certificate Automation - Automates the deployment and renewal of SSL/TLS certificates using ACME and DNS challenges.
- ACME Certificate Lifecycle Managers - Automates the full lifecycle of TLS certificates using the ACME protocol for secure domain routing.
- Infrastructure Health Monitors - Tracks service uptime and analyzes network infrastructure health to ensure backend availability.
- Service Uptime Monitors - Monitors the availability and uptime of backend services to notify administrators of outages.
- Remote Command Execution - Enables the execution of administrative shell commands on remote Linux systems through a web interface.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
