AppAPI Heartbeat test fails, also http strict-transport-security warning

ℹ️ Support
, , ,
1

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
  • Operating system and version (e.g., Ubuntu 24.04):
    • Debian - Docker image apache
  • Web server and version (e.g, Apache 2.4.25):
    • apache inside docker image
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • nginx
  • PHP version (e.g, 8.3):
    • 8.3.27
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • offical docker image nextcloud:32-apache
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • no

I’m running two debian server, on each one nextcloud instance. The configuration files are 99% identical, only the www addresse and passworts are different (I checked all config files many many times). Server 1 I’m setting up of roughly 3 years and server 2 for roughly a half year. Both nextcloud instance on the same version 32.0.1. Both nextcloud instance are running in the nextcloud:32-apache image.

I tryied to install AppAPI on both instances. For server 2 it works fine and server 1 the connection from nextcloud to Harp is fine. But the heartbeat test fails on server 1 and I do not know why! Warning message from nextcloud logging

{
  "reqId": "GHZEYlSg6KQyft3Gt1wi",
  "level": 2,
  "time": "2025-11-13T18:50:47+00:00",
  "remoteAddr": "",
  "user": "--",
  "app": "app_api",
  "method": "",
  "url": "--",
  "message": "Failed heartbeat on https://XXXX/exapps/test-deploy for 40 times. Most recent status=0, error: cURL error 7: Failed to connect to XXXX port 443 after 0 ms: Could not connect to server (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://XXXX/exapps/test-deploy/heartbeat",
  "userAgent": "--",
  "version": "32.0.1.2",
  "data": {
    "app": "app_api"
  },
  "id": "69163a0471317"
}

Server 1 does also produce a Warning message at Administrator→Overview. The http strict-transport-security is not set, but curl tells me, the strict-transport-security is set. In the nginx settings the strict-transport-security is set and works as aspected. Also checked with https check website.

So, I think the apache server inside the docker image does not work correctly. Is there a way to reset the apache server settings inside the docker image/container?

Is there a way to repair the nextcloud instance without lossing user data?

docker-compose.yml

services:
  db:
    image: postgres:17-alpine
    # ...

  redis:
    image: redis:alpine
    restart: unless-stopped

  appapi-harp:
    image: ghcr.io/nextcloud/nextcloud-appapi-harp:release
    ports:
      - 8780:8780
      - 8782:8782
    restart: unless-stopped
    volumes:
      - ./certs:/certs
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - HP_SHARED_KEY=XXXX
      - NC_INSTANCE_URL=https://XXXX

  nextcloud:
    image: nextcloud:32-apache
    depends_on:
      - redis
      - db
      - appapi-harp
    ports:
      - "127.0.0.1:XXXX:80"
    volumes:
      # ...
    environment:
      - APACHE_DISABLE_REWRITE_IP=1
      - TRUSTED_PROXIES=10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 127.0.0.0/8
      - OVERWRITEHOST=XXXX
      - OVERWRITEPROTOCOL=https
      # ...
      - REDIS_HOST=redis

volumes:
  # ...

networks:
  default:
    name: nextcloud-network