Based on the search results, HaRP (Nextcloud AppAPI HaProxy Reverse Proxy) is the modern, recommended way to deploy External Applications (ExApps) in Nextcloud 32+ to improve performance, security, and WebSocket support.
Here is a content plan for a blog post or technical guide on setting up HaRP.
🚀 Unlocking Real-Time Nextcloud: A Guide to HaRP (AppAPI Reverse Proxy) Introduction
Nextcloud has revolutionized self-hosted collaboration, but as apps get smarter (think AI agents and real-time chat), the standard way of connecting "External Apps" (ExApps) has become a bottleneck. Enter HaRP (Harp Reverse Proxy), the new standard for Nextcloud 32+.
What is it? A specialized reverse proxy for AppAPI that replaces Docker Socket Proxy.
Why use it? It offers better performance, supports WebSockets (essential for real-time), and secures connections to apps. Why Migrate to HaRP?
WebSocket Support: Enables truly real-time interaction for ExApps.
Improved Security: Direct HTTP/HTTPS communication bypassing the main PHP stack.
Scalability: Allows ExApps to run on separate hosts, perfect for offloading AI workloads.
No more docker.sock risks: Eliminates the need to map the Docker socket to your Nextcloud container. 🛠️ Step-by-Step Setup: HaRP in Docker This guide assumes you are using Docker to run Nextcloud. 1. Create a Network
Create a shared network so HaRP can talk to your Nextcloud instance. docker network create nextcloud-network Use code with caution. Copied to clipboard 2. Run the HaRP Container Pull and run the latest HaRP container. harp nextcloud
docker run -d \ --name appapi-harp \ --network nextcloud-network \ -e HP_SHARED_KEY="your-secure-password" \ -e NC_INSTANCE_URL="https://your-nextcloud.com" \ ghcr.io/nextcloud/nextcloud-appapi-harp:release Use code with caution. Copied to clipboard 3. Register Daemon in Nextcloud Go to your Nextcloud Admin Settings > AppAPI. Click + Register Daemon. Choose HaRP Proxy (Docker). Use appapi-harp:8780 for the Proxy Address. Enter the shared key you used in step 2. 💡 Best Practices & Troubleshooting
Shared Key: Ensure the HP_SHARED_KEY matches in your docker command and registration form.
Reverse Proxy: If you use Nginx Proxy Manager, set up a location block to route /exapps/ to http://appapi-harp:8780.
Heartbeat Issues: If tests fail, check that your main Nextcloud container can talk to appapi-harp on the Docker network. Conclusion
HaRP is the future of Nextcloud application deployment. By bridging the gap between ExApps and Nextcloud, you get a faster, more robust system. Source: GitHub nextcloud/HaRP , Nextcloud Dev Documentation To help you with this content further, tell me: Is this for a blog post, documentation, or social media? Do youyml examples) or a more beginner-friendly overview? Nextcloud AIO problems with HARP AIO AppApi
Understanding Nextcloud HaRP: The Future of External App Integration
Nextcloud HaRP (Nextcloud AppAPI HaProxy Reverse Proxy) is a reverse proxy system designed to simplify and optimize the deployment of external apps (ExApps) within the Nextcloud ecosystem. Introduced as the recommended solution for Nextcloud 32+, HaRP serves as a modern successor to the older Docker Socket Proxy (DSP) method, offering improved performance, better security, and support for real-time protocols like WebSockets. Core Functions and Architecture
HaRP sits behind your main reverse proxy and acts as a dedicated bridge for communication between the Nextcloud server, the client UI, and ExApps.
Bypassing the PHP Stack: Traditionally, requests to external apps had to pass through the Nextcloud PHP stack. HaRP allows the web UI to communicate directly with ExApps, significantly reducing resource consumption and improving responsiveness.
FRP-Based Tunneling: HaRP utilizes Fast Reverse Proxy (FRP) to create secure outbound tunnels from ExApps to the HaRP container. This means ExApps do not need to expose any ports to the host or be directly reachable by the Nextcloud server, which is ideal for restrictive firewall environments. Based on the search results, HaRP (Nextcloud AppAPI
WebSocket Support: One of the most significant upgrades in HaRP is its native support for WebSockets. This enables ExApps to provide real-time features that were previously difficult or impossible to implement under the old proxy system. Key Benefits over Docker Socket Proxy (DSP)
While DSP is still supported for the time being, it is slated for deprecation in Nextcloud 35. HaRP offers several advantages that make it the superior choice for modern deployments: Docker Socket Proxy (DSP) Nextcloud HaRP Performance High overhead (PHP proxied) Low overhead (Direct proxying) Connectivity Requires port exposure No ports need exposure (FRP Tunnel) Protocols Limited HTTP support Full HTTP/HTTPS & WebSockets Security Shared Docker socket risks Isolated FRP-based transport Deployment Local host only Local or Remote host support Deployment and Configuration
Deploying HaRP involves setting up a dedicated container and then registering it within the Nextcloud administrative interface. docs.nextcloud.comhttps://docs.nextcloud.com Adapting ExApps to HaRP - Nextcloud Documentation
HaRP (High-performance AppAPI Reverse Proxy) is the modern networking backbone for Nextcloud’s External Apps (ExApps) ecosystem. Introduced as the recommended deployment daemon starting with Nextcloud Hub 32, HaRP replaces the older Docker Socket Proxy (DSP) to provide better performance, easier remote deployments, and native support for real-time protocols like WebSockets. What is Nextcloud HaRP?
HaRP is a specialized reverse proxy system designed to sit between your main web server (like Nginx or Apache) and individual External Apps. While traditional Nextcloud apps are written in PHP and run within the core server process, ExApps are standalone microservices—often written in Python, Rust, or Go—that run in their own Docker containers. HaRP serves two primary functions:
Deployment Management: It communicates with the Docker Engine to create, start, and stop ExApp containers.
Traffic Routing: It routes client requests directly to these containers, bypassing the Nextcloud PHP stack entirely for improved efficiency. Key Benefits of HaRP over Docker Socket Proxy (DSP)
WebSocket Support: Unlike the legacy proxy, HaRP enables full end-to-end WebSocket communication, allowing ExApps to feature real-time collaborative editing and live dashboards.
NAT Traversal with FRP: 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.
Simplified Remote Deployment: HaRP makes it significantly easier to run ExApps on a different physical server than the main Nextcloud instance. Alternatives
Improved Security: By using a shared key and dedicated certificates, HaRP provides a more robust security model for managing external microservices. How to Install and Configure HaRP
For most users, especially those using Nextcloud All-in-One (AIO), HaRP is being integrated as the default option.
WebSockets in Nextcloud: creating real‑time apps via AppAPI
If you want, I can provide:
Prior works like Siyu et al. (2022) integrated blockchains with cloud storage for audit trails. Harp uses a lightweight, permissionless hash chain stored locally per user — no proof-of-work required.
Generating a proof for a 10‑version file takes 24 ms (client‑side verify: 31 ms). This is acceptable for periodic auditing.
Harp is not a standard, officially supported Nextcloud app or core component. Instead, it most likely refers to:
The most concrete public reference is the Harp Nextcloud client on GitHub (archived or experimental).
Note: As of the latest release, this requires Docker and experimental plugins. Always back up your config.php.