Hi everyone,
I’m hitting a persistent “heartbeat check failed” on stt_whisper2 2.5.0
when I deploy it on a remote HaRP daemon, on a fresh Nextcloud 32.0.14
(upgraded from 31.0.14 last week). Both the ExApp container and HaRP are
healthy, the FRP tunnel establishes cleanly on every restart, and from
inside the ExApp I can reach http://<nextcloud-lan-ip>/status.php
with niquests (three back-to-back → 200/200/200). Yet
occ app_api:app:enable returns “Failed to enable ExApp stt_whisper2”
and no provider is registered — the Assistant’s “Work with audio” tab
only shows TTS.
I’ve eliminated the usual suspects (NC 32 upgrade artifacts, the
documentserver_community boot fatal, wrong NC_INSTANCE_URL, HTTP/2
races, DSP-vs-HaRP confusion, storage-driver issues) — I’ve put all the
details below to save a round-trip.
What I’m hoping for: the exact HTTP flow that constitutes the
“heartbeat check” during an enable on a remote HaRP daemon — HaRP shows
no incoming request at that moment, which puzzles me. Any pointer on
where to tcpdump or which log/loglevel to raise would be much
appreciated. Full report follows.
Thanks a lot!