HaRP is a high-performance reverse proxy that simplifies how Nextcloud communicates with apps running outside the main server (ExApps). It was introduced primarily to:
As the older Docker Socket Proxy approach faces deprecation, adopting HaRP ensures your Nextcloud instance is ready for future ExApp advancements. Setting Up HaRP: A Brief Overview
Keepalived uses the Virtual Router Redundancy Protocol (VRRP) to share a single Virtual IP (VIP) address between the two balancers. If the primary load balancer fails, the secondary balancer instantly claims the VIP. The Stateless Web Application Layer
Inside were not just audio files. There were version histories, side-by-side transcriptions, sonograms, and a sprawling, threaded chat. harp nextcloud
The main proxy routes this specialized request to HaRP.
Any user can request a proof that a current file version is the result of a legitimate sequence of operations. The server returns the hash chain segment and a signed timestamp from a threshold of other nodes (in federated mode). This enables proof of integrity without a blockchain.
The integration of Harp and Nextcloud has numerous real-world use cases: HaRP is a high-performance reverse proxy that simplifies
HaRP uses Fast Reverse Proxy (FRP) tunnels. This means ExApp containers do not need to expose any ports to the host or even be directly reachable by the Nextcloud server.
Instead of proxying application payloads through PHP, the client browser connects directly to HaRP. HaRP quickly validates the user's active login session with Nextcloud. Once authorized, it opens a low-latency, end-to-end WebSocket channel straight to the microservice. This mechanism lowers latency and allows Nextcloud instances to handle thousands of concurrent interactions. Secure FRP Tunneling
The official Nextcloud HaRP Repository serves as . Built on top of high-performance HAProxy and integrated with Fast Reverse Proxy (FRP) tunneling, HaRP provides a secure, stateful, and asynchronous gateway for external containers. The Core Architectural Change If the primary load balancer fails, the secondary
It communicates with the Docker Engine to create, start, and stop ExApp containers.
If you are running Docker on a remote host, the recommended setup involves the HaRP container on the local host managing the remote host's socket. HaRP vs. Docker Socket Proxy HaRP (Fast Proxy) Docker Socket Proxy (Old Method) Recommendation Recommended for Nextcloud 32+ Legacy/Alternative Traffic Routing Direct to App (Faster) Through Nextcloud (Slower) Setup Complexity Simple/Automated Complex/Manual Security High (Built-in Auth) Dependent on Configuration WebSockets Conclusion
Deploy a 3-node MariaDB Galera cluster. Once active, create a dedicated Nextcloud database and user with appropriate network permissions.
Unlike the legacy proxy, HaRP enables full end-to-end WebSocket communication, allowing ExApps to feature real-time collaborative editing and live dashboards.