# Installing Harp for ExApps: Can't Connect from Nextcloud

**URL:** <https://help.nextcloud.com/t/installing-harp-for-exapps-cant-connect-from-nextcloud/225904>\
**Category:** ℹ️ Support\
**Tags:** caddy, docker, app\_api, harp, nextcloud-infrastructure, nc31\
**Created:** [May 28, 2025, 7:39pm UTC](https://help.nextcloud.com/t/installing-harp-for-exapps-cant-connect-from-nextcloud/225904 "2025-05-28T19:39:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![That\_Dude](https://help.nextcloud.com/user_avatar/help.nextcloud.com/that_dude/32/32804_2.png) [@That\_Dude](https://help.nextcloud.com/u/That_Dude)\
**Post date:** [May 28, 2025, 7:39pm UTC](https://help.nextcloud.com/t/installing-harp-for-exapps-cant-connect-from-nextcloud/225904/1 "2025-05-28T19:39:11Z")

</div>

## 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

- Web server and version _(e.g, Apache 2.4.25)_:
  - nginx/1.27.5

- Reverse proxy and version \_(e.g. nginx 1.27.2)
  - Caddy 2.6.2

- PHP version _(e.g, 8.3)_:
  - 31.0.4.1

- Is this the first time you’ve seen this error? (Yes / No):
  - Yes

- When did this problem seem to first start?
  - I am installing 🙂

- Installation method _(e.g. AlO, NCP, Bare Metal/Archive, etc.)_
  - Docker

- Are you using CloudfIare, mod\_security, or similar? _(Yes / No)_
  - Yes but proxying is off

### Summary of the issue you are facing:

I am interested in installing ExApps and I have been following the [documentation from Nextcloud](https://docs.nextcloud.com/server/latest/admin_manual/exapps_management/AppAPIAndExternalApps.html#ai-app-api) as well as [the documenation on GitHub](https://github.com/nextcloud/HaRP?tab=readme-ov-file#how-to-install-it). I have a working docker container for appapi-harp that is bound to 127.0.0.1:8070. They can also communicate over a docker network (nextcloud\_network). When I try to add harp API to my nextcloud daemons, I get an error. When checking the logs it mentions that it cannot curl `appapi-harp:8070/v1.41/_ping`. My understanding is that harp is meant to serve this page, but instead I get a 404 error. When I look into the docker container logs, it is actually getting the request but says `Invalid request path`.

I am a bit of a newbie here and just trying to dive in the deep end. With that caveat, my understanding is that nextcloud expects the harp container to serve `/v1.41/_ping` but the harp container isn’t ready for it. Is there something I am missing here? I have looked around the internet and not really seen anything on this, and I am also not reallly sure what I could have misconfigured if the harp container isn’t serving a page it should be serving.

### Admin Console AppAPI Screen

 ![Screenshot 2025-05-28 133439](https://help.nextcloud.com/uploads/default/original/3X/4/4/448846a3bc552d92be3caf8eed31c3f387e2f9d2.png)

### Log entries

#### Nextcloud Admin Console Logs

So I looked to the admin console.

```auto
 ConnectException cURL error 7: Failed to connect to appapi-harp port 8070 after 0 ms: Couldn't connect to server (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://appapi-harp:8070/v1.41/_ping

```

#### nextcloud-app Docker Container

I can reach the appapi-harp container from inside of the nextcloud-app container (running nextcloud fpm). But it is getting back a 404.

```auto
root@8c03fc6ccbf4:/var/www/html# curl -v http://appapi-harp:8780/v1.41/_ping
* Trying 172.19.0.8:8780...
* Connected to appapi-harp (172.19.0.8) port 8780 (#0)
> GET /v1.41/_ping HTTP/1.1
> Host: appapi-harp:8780
> User-Agent: curl/7.88.1
> Accept: */*
>
< HTTP/1.1 404 Not Found
< content-length: 13
< content-type: text/plain
<
* Connection #0 to host appapi-harp left intact
404 Not Found

```

#### appapi-harp Docker Container Logs

So the appapi-harp container is seeing the request, but it isn’t formatted in such a way that it knows what to do with it? Or maybe somehow I have more configurations to do on the container so it can serve this page.

```auto
[2025-05-28T19:22:08+0000] [ERROR] Invalid request path, cannot find AppID: /v1.41/_ping

```

---

<div class="post-metadata">

**Author:** ![jtr](https://help.nextcloud.com/letter_avatar/jtr/32/5_5575768a8748004e209b776fc1b2916d.png) [@jtr](https://help.nextcloud.com/u/jtr)\
**Post date:** [May 28, 2025, 8:53pm UTC](https://help.nextcloud.com/t/installing-harp-for-exapps-cant-connect-from-nextcloud/225904/2 "2025-05-28T20:53:48Z")

</div>

To my knowledge you’d need to be running v32 (i.e. a development stack):

> <https://github.com/nextcloud/HaRP/issues/38>
>
> \### Steps to reproduce
> 1. Install harp docker container
> 2. Register daemon on ne…xtcloud appapi admin page with IP:8780 url (2375 does not even connect)
> 3. Check docker container logs
> 
> \### Expected behaviour
> Connection should be succesful
> 
> \### Actual behaviour
> On the docker container logs you can see:
> \[ERROR\] Invalid request path, cannot find AppID: /v1.41/\_ping

---

<div class="post-metadata">

**Author:** ![That\_Dude](https://help.nextcloud.com/user_avatar/help.nextcloud.com/that_dude/32/32804_2.png) [@That\_Dude](https://help.nextcloud.com/u/That_Dude)\
**Post date:** [May 28, 2025, 9:04pm UTC](https://help.nextcloud.com/t/installing-harp-for-exapps-cant-connect-from-nextcloud/225904/3 "2025-05-28T21:04:13Z")

</div>

@jtr  
Thank you 😃. I should have dug deeper on GitHub. Now I need to decide if playing with this is worth setting up a development stack…

---

<div class="post-metadata">

**Author:** ![system](https://help.nextcloud.com/user_avatar/help.nextcloud.com/system/32/29333_2.png) [@system](https://help.nextcloud.com/u/system)\
**Post date:** [June 5, 2025, 9:05pm UTC](https://help.nextcloud.com/t/installing-harp-for-exapps-cant-connect-from-nextcloud/225904/4 "2025-06-05T21:05:12Z")

</div>

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.