TranNAP Phase 3
Careful polishing, striving for excellence. In this phase, we have completed a total of 73 issues. TranNAP has made significant progress in protocol capabilities, node management, and user experience.
HTTP and SSH Tunneling
The most important achievement of this phase is support for HTTP and SSH protocol tunneling. Prior to this, TranNAP only supported TCP tunneling. Now, users can directly expose local web services and SSH services through TranNAP without additional configuration. HTTP tunneling is independently implemented, decoupled from TCP tunneling, with accompanying API and console support.
Protocol and Connection Stability
We made extensive improvements to the transport protocol layer. We resolved the issue of permanent blocking after disconnection and fixed the problem where NAT table aging caused both sides to be unaware of disconnection, preventing automatic reconnection. Various timeout parameters are now configurable instead of using hardcoded defaults. The data synchronization mode was adjusted to NSQ-based incremental synchronization, with node changes written to message queues, significantly improving system responsiveness and reliability.
Domain and DNS Automation
The domain binding experience has been comprehensively optimized. After a node binds an HTTP domain, the system automatically sets DNS records without manual operation. Domain binding now includes uniqueness validation, and bound domains are automatically cleared when switching nodes. Users are informed that DNS resolution takes time to take effect. Additionally, the Caddy configuration now automatically redirects root domain access to the official website.
Node Adjustments
We adjusted our global node infrastructure: added a South Korea node, decommissioned the unstable Hong Kong node, and took down the Las Vegas node. Nodes now start normally even if API requests fail, with added capabilities for checking certificate issuance status and reporting on startup.
CLI and Management Tools
CLI-side issues including log persistence, startup errors, and runtime errors have all been resolved, along with a deadlock that prevented subsequent handles from reaching the server. The installation and auto-update functionality was reimplemented using the updatekit library. trannapctl has been unified with trannap, providing stop, start, restart, and other management commands.
User Console
The console homepage now displays real data with traffic statistics and connection count features. Nodes appear greyed out when offline, and device online status is displayed in real time. Credits support is now live. Additionally, we fixed mobile display misalignment, link redirect copy issues, and optimized request logic.
API Backend
The backend was migrated from the Gin framework to go-fuego. System configuration support was added, along with daily summary email sending and supplementary statistics chart APIs. Expired data is now automatically cleaned up when uploading CLI versions, and Credits support has been completed at the API level.
Website
The website completed multi-language support and SEO optimization. User agreement, acknowledgments page, and command reference documentation were added. We fixed issues including oversized first-screen text on mobile, incorrect menus, images not supporting click-to-zoom, and System color mode flashing on first load. The download page mobile display was also optimized. The deployment script was changed to upload compressed archives instead of individual files, improving deployment efficiency.