🐳 Nextcloud AIO – Fix “HaRP daemon not accessible” error

[minto3792]

Problem
You open the Nextcloud admin panel, go to AppAPI, and see these errors:

• ❌ AppAPI default deploy daemon “nextcloud-aio-harp” is not accessible.
• ❌ Could not retrieve HaRP version from daemon “nextcloud-aio-harp”.

The AI features (like the Nextcloud Assistant) might be broken, and the daemon seems dead.

Why it happens
Nextcloud AIO handles the nextcloud-aio-harp daemon automatically, but sometimes its internal authentication tokens get out of sync 🔐. When that happens, the harp container thinks Nextcloud’s health checks are brute‑force attacks and starts blocking them. The “Test deploy” also fails.

The fix that worked (and it’s super simple ✨)
You don’t need to edit any config files, rebuild containers, or understand how HaRP works under the hood. Just re‑register the daemon from scratch, using the AIO interface and the Nextcloud admin panel.

---

🔧 Step‑by‑Step fix

1. Delete the broken daemon registration

   • Log into your Nextcloud instance as an admin.
   • Go to Settings → Administration → AppAPI.
   • Find the daemon named nextcloud-aio-harp (it might show an error).
   • Click the 🗑️ trash icon to delete it.
     Don’t worry – the container itself is still there, we’re just removing the old, broken registration.

2. Re‑initialise the harp container via AIO

   • Open the AIO interface (usually https://your-server-ip:8443).
   • Go to the “Optional containers” section.
   • Find the “Harp” (or “Nextcloud AI”) switch and turn it OFF 🔴.
   • Click “Stop containers” and wait until everything stops.
   • Then click “Start containers” – the harp container will be removed.
   • Once everything is up, go back to the same switch and turn it ON again 🟢.
   • Click “Start containers” a second time (or just “Start” if prompted).

   🔁 What this does: AIO creates a fresh nextcloud-aio-harp container, generates brand‑new security tokens, and registers the daemon inside Nextcloud cleanly.

3. Check if it worked

   • Back in Nextcloud → AppAPI, you should now see nextcloud-aio-harp without errors.

   • Click “Test deploy – AIO HaRP” (or “Test connection”).

   • All 6 checks should turn green ✅:

     • Register ExApp in Nextcloud
     • Image pull (100%)
     • Container started
     • Heartbeat
     • Init step (100%)
     • Enabled

   • 🎉 Done! The HaRP version check will pass and any AI apps that depend on it will start working again.

---

🤔 Still seeing errors?

• Make sure your Nextcloud and harp containers are on the same Docker network (AIO does this by default – restarting with the toggle above fixes it).
• If the error persists, try a full AIO restart:
  • Stop all containers, then start them again, and repeat the toggle step.
  • That re‑syncs certificates and internal secrets across the whole stack.

---

📣 Shout‑out

This fix was discovered after a lot of log‑reading and trial‑and‑error. Big thanks to the Nextcloud community for pointing in the right direction. Hope it saves you some hours! ✌️

Works with: Nextcloud AIO v30+ (likely any version that uses the nextcloud-aio-harp container).