Frp: Neo
Frp Neo: The Next Generation of Fast Reverse Proxy
In the ever-evolving landscape of network penetration and internal network exposure, one tool has stood out for years: FRP (Fast Reverse Proxy). However, as cloud-native architectures and edge computing become mainstream, the limitations of the original FRP have become apparent. Enter Frp Neo—the community-driven, performance-optimized fork designed to address modern networking challenges.
But what exactly is Frp Neo? How does it differ from the classic FRP, and should you migrate your infrastructure to support it? This comprehensive article dives deep into its architecture, core features, installation process, and real-world use cases. Frp Neo
4. What “Neo” gives you (vs classic FRP)
session_sticky: keep a session pinned to the same backend.multi_user: onefrpshandles multiple clients with isolated tokens.reconnectimprovements: less chatty, more resilient.- Web dashboard shows active sessions per user.
Example extended client config (Neo‑style): Frp Neo: The Next Generation of Fast Reverse
[web]
type = http
local_port = 3000
custom_domains = app.example.com
# Neo extras:
session_sticky = true
health_check_type = tcp
health_check_timeout_s = 3
2. Multi-User Isolation (Tenancy)
Running a public FRP server for a team or clients was risky in original FRP due to the flat user model. Frp Neo introduces virtual proxies. session_sticky : keep a session pinned to the same backend
- User A can only see proxies under
user-a.neo.example.com. - User B cannot probe User A's ports.
- Each user gets a dedicated TOML config chunk with their own traffic quota.
What frp is
- frp is an open-source, high-performance reverse proxy that allows you to expose local network services (HTTP, SSH, RDP, WebSocket, etc.) to the internet through a public server. It uses a client–server model: frps (server) runs on a public host; frpc (client) runs inside a private network and establishes outbound connections to frps to create tunnels.
Case 1: Exposing a Local LLM (Ollama/LM Studio)
You run a private Large Language Model on your gaming PC without a public IP. Use Frp Neo to expose Ollama’s API (localhost:11434) with TLS:
[[proxies]]
name = "llm-api"
type = "https"
local_port = 11434
custom_domains = ["llm.yourdomain.com"]
# Neo automatically adds CORS headers for web UIs
plugin.cors.enabled = true
Now access https://llm.yourdomain.com from your phone anywhere.
What “FRP Neo” tools claim to do
- Bypass FRP locks or otherwise allow technicians to regain access to devices without the original account credentials.
- Provide device-specific exploits, use ADB/OTG methods, or leverage vulnerabilities in certain firmware.
8. Common troubleshooting
| Symptom | Fix |
|--------|------|
| login failed | token mismatch / wrong server port |
| connection refused | firewall on VPS (open 7000, 8080, 2222) |
| custom domain not working | set vhost_http_port and correct DNS |
| client reconnects loop | increase heartbeat_timeout = 90 in client config |