Privacy settings

We use cookies in our shop. Some are necessary while others help us improve the shop and the visitor experience. Please select below which cookies may be set and confirm this with "Confirm selection" or accept all cookies with "Select all":

Cookies that are necessary for the basic functions of our shop (e.g. navigation, shopping cart, customer account).
Cookies that we use to collect information about how our shop is used. With their help, we can further optimize purchasing for you. Example application: Google Analytics.
Marketing cookies enable us to make the content on our website as well as advertising on third-party sites as relevant as possible for you. Please note that some of the data will be transferred to third parties for this purpose. Example applications: Criteo or Facebook.

Cookie DetailsCookie Details ausblenden

Privacy policy Terms & conditions

filter
Account
(Forgot Password?)
#ueb#eingel_bleiben#

Harp Nextcloud Install File

Before we type a single command, ensure you have the following:

To prevent brute-force attacks on your Harp API endpoint, add this to your Nextcloud .htaccess or Nginx config:

location ~ /harp/ 
    limit_req zone=music burst=5;

To follow this guide, you will need:

Installing and Configuring HaRP for Nextcloud AppAPI HaRP (High-performance AppAPI Reverse Proxy) is the next-generation deployment daemon for Nextcloud Hub 32+, replacing the older DockerSocketProxy (DSP). It acts as a dedicated bridge and proxy for External Apps (ExApps), enabling them to communicate directly with clients via WebSockets and bypass the standard PHP stack for improved performance. 1. Prerequisites Before beginning the installation, ensure you have:

Nextcloud 32 or higher (HaRP is the recommended standard for these versions). Docker and Docker Compose installed on your host. Administrative access to your Nextcloud instance. The AppAPI app installed from the Nextcloud App Store. 2. Deploying the HaRP Container

HaRP is typically deployed as a standalone Docker container. Use the following docker-compose.yml snippet to launch it:

services: appapi-harp: image: ghcr.io/nextcloud/nextcloud-appapi-harp:release container_name: appapi-harp restart: always environment: - HP_SHARED_KEY=your_very_secure_password # Minimum 12 characters - NC_INSTANCE_URL=https://your-nextcloud-domain.com volumes: - /var/run/docker.sock:/var/run/docker.sock:ro # Access to Docker engine - ./harp_certs:/certs # Persistent storage for FRP certificates networks: - nextcloud_network networks: nextcloud_network: external: true Use code with caution.

HP_SHARED_KEY: A secret key used to authenticate communication between Nextcloud and HaRP.

NC_INSTANCE_URL: The full URL of your Nextcloud installation.

Persistent Volume: Mounting /certs is critical. If these certificates are lost, existing ExApp tunnels will fail due to TLS mismatches. 3. Registering the HaRP Daemon in Nextcloud

Once the container is running, you must link it to Nextcloud through the web interface: Installing Harp for ExApps: Can't Connect from Nextcloud

The Basics. Nextcloud Server version (e.g., 29. x.x): 31.0. 4. Operating system and version (e.g., Ubuntu 24.04): Ubuntu 24.04. 2. Nextcloud community

nextcloud/HaRP: Fast Proxy for AppAPI(Nextcloud 32+) - GitHub harp nextcloud install

HaRP (High Performance Reverse Proxy) is a specialized system introduced for Nextcloud 32+ to manage and scale External Apps (ExApps) through the

. It acts as a fast proxy that allows ExApps to communicate directly with clients, bypassing the core Nextcloud instance to reduce overhead and latency. Installation Overview HaRP is primarily designed for Docker-based deployments and is not currently supported for bare-metal installs. Nextcloud community Setup Method

: You typically run HaRP as a separate Docker container alongside your Nextcloud instance or on a dedicated host. Key Configuration Environment Variables : You must set HP_SHARED_KEY (a secret for authentication) and NC_INSTANCE_URL (the address of your Nextcloud server). : It often requires a Docker Socket Proxy

or direct access to the Docker socket to orchestrate ExApp containers. External Access

: If using a reverse proxy (like NGINX or HAproxy), you must forward traffic for specifically to the HaRP container. The "Long Review": Critical Insights Based on community feedback and Nextcloud documentation , here is a breakdown of the current state of HaRP: Pros: Performance & Scalability

AIO and HARP for ExApp running remotely - the Nextcloud forums 2 Mar 2026 —

If you want to access your music collection outside your home network, you must secure the installation.

Traditional Nextcloud installation methods are riddled with edge cases. The Snap package is easy but limits customization. Docker Compose is flexible but requires understanding volumes, networks, and environment variables. Manual LAMP is educational but suicidal for production.

The harp nextcloud install method sits in the perfect middle ground. It gives you the robustness of a sysadmin (proper permissions, Redis caching, automatic HTTPS) with the simplicity of a PaaS (Platform as a Service).

By following this guide, you have transformed a raw Linux server into a production-ready, secure, and blazing-fast Nextcloud instance in under 10 minutes. You now own your data, free from Google Drive or Dropbox quotas.

Next steps: Install the Nextcloud desktop and mobile apps, sync your files, share folders with colleagues, and enjoy your private cloud.

Have questions about a specific Harp parameter? Check the official harp.json schema reference or join the community forum. Happy self-hosting! Before we type a single command, ensure you

Complete Guide to Installing HaRP for Nextcloud AppAPI HaRP (Nextcloud AppAPI HaProxy Reverse Proxy) is the next-generation proxy system designed to simplify the deployment of External Apps (ExApps) in Nextcloud 32 and later. It replaces the older Docker Socket Proxy (DSP) method, which is slated for deprecation in Nextcloud 35.

By using HaRP, ExApps can communicate directly with clients via WebSockets, bypassing the main Nextcloud PHP stack to significantly reduce latency and improve performance for real-time features like AI chats or document indexing. Prerequisites Before beginning the installation, ensure you have:

Nextcloud Version: 32 or newer is highly recommended for full HaRP support.

Docker Environment: A running Docker engine where you can deploy the HaRP container.

AppAPI: The AppAPI app must be installed and enabled on your Nextcloud instance. Step 1: Deploy the HaRP Container

The first step is to set up a Docker container called appapi-harp that will act as the bridge between Nextcloud and your external apps. Prepare Environment Variables: HP_SHARED_KEY: A secure secret token for authentication.

NC_INSTANCE_URL: Your public Nextcloud URL (e.g., https://cloud.example.com).

HP_TRUSTED_PROXY_IPS: The IP or CIDR range of your main reverse proxy (e.g., Nginx or Caddy).

Run the Container:You can deploy HaRP using a standard Docker command. Ensure you publish the necessary ports: Port 8780: Standard HTTP communication. Port 8782: FRP tunnel port for ExApps.

docker run -d \ --name appapi-harp \ --network host \ -e HP_SHARED_KEY="your_secure_password" \ -e NC_INSTANCE_URL="https://nextcloud.url" \ -e HP_TRUSTED_PROXY_IPS="172.18.0.0/16,127.0.0.1" \ -v /var/run/docker.sock:/var/run/docker.sock \ ghcr.io/nextcloud/harp:latest Use code with caution.

Note: Using --network host is the simplest way to ensure local reachability, but you can also use a dedicated Docker network if preferred. Step 2: Register the HaRP Daemon in Nextcloud

Once the container is running, you must tell Nextcloud how to find it. Navigate to Administration Settings > AppAPI. Click Register Daemon. To follow this guide, you will need: Installing

Choose the HaRP Proxy (Host) or HaRP Proxy (Docker) template. Fill in the details: Host: Use localhost:8780 if HaRP is on the same machine. FRP Server Address: Typically localhost:8782. Shared Key: Must match the HP_SHARED_KEY set in Step 1. Click Check Connection and then Register. Step 3: Configure Your Main Reverse Proxy

To enable direct routing (and WebSockets), your main reverse proxy (Nginx, Apache, or Caddy) needs a redirect for the /exapps/ path.

For Nginx, add a location block above your main Nextcloud route:

location /exapps/ proxy_pass http://127.0.0.1:8780; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; Use code with caution. Step 4: Connecting Remote Docker Engines (Optional)

If you want to run heavy ExApps (like AI models) on a separate machine with a GPU, you can use the built-in FRP (Fast Reverse Proxy) tunnel.

Retrieve Certs: Copy the generated certificates from the HaRP container to the remote machine. docker cp appapi-harp:/certs/frp/client.crt ./certs/frp/ Use code with caution.

Configure FRP Client: On the remote machine, create a frpc.toml file pointing to your HaRP server's address on port 8782.

Run FRP Client: Start the FRP client container on the remote machine to establish the secure tunnel. Troubleshooting and Verification

nextcloud/HaRP: Fast Proxy for AppAPI(Nextcloud 32+) - GitHub

In the left sidebar, you can either browse the "Multimedia" category or simply use the search bar. Type "Harp".

You will see an entry with a harp icon (a golden stringed instrument). Click the "Download and enable" button.

Upload a 2GB file via the web interface. Because Harp configured Nginx client max body size and PHP post max size, this should work immediately. If you are behind a reverse proxy (Cloudflare), you may need to tweak, but Harp's default Nginx template handles it.