Talk Recording - 403 Forbidden error

Hi everyone,

I’m trying to get Talk Recording working with the nextcloud/aio-talk and nextcloud/talk-recording containers and I’m running into a 403 Forbidden error from the recorder.


Setup Overview

  • Nextcloud Server (Host B):
    Runs Nextcloud 31.0.6
    Spreed App is installed and working.
  • HPB & Recorder (Host A - 192.168.1.189):
    Running Docker containers talk_hpb (signaling + TURN) and talk_recorder.

Docker Compose Config for talk HPB

version: '3.8'

services:
  talk_hpb:
    container_name: talk_hpb
    image: nextcloud/aio-talk:latest
    init: true
    ports:
      - "3478:3478/tcp"
      - "3478:3478/udp"
      - "8181:8081/tcp"
    environment:
      - NC_DOMAIN=hub.mydomain.com
      - TALK_HOST=signaling.mydomain.com
      - TURN_SECRET=***REDACTED***
      - SIGNALING_SECRET=***REDACTED***
      - INTERNAL_SECRET=***REDACTED***
      - TALK_PORT=3478
      - TZ=America/New_York
    restart: unless-stopped

  talk_recorder:
    container_name: talk_recorder
    build:
      context: ../nextcloud-talk-recording
      dockerfile: docker-compose/Dockerfile
    volumes:
      - /mnt/TalkRecorderMedia:/mnt/TalkRecorderMedia
      - /home/user/nextcloud-talk-recording/recording-config.json:/app/config.json:ro
    depends_on:
      - talk_hpb
    environment:
      - TZ=America/New_York
    networks:
      - default

networks:
  default:

recording-config.json

{
  "storage": {
    "path": "/mnt/TalkRecorderMedia"
  },
  "signaling": {
    "internal_secret": "REDACTED",
    "url": "http://192.168.1.189:8081"
  },
  "recorder": {
    "name": "Recorder 1"
  }
}

Talk Admin Panel (Nextcloud)

In the Talk admin panel I’ve set the Recording Backend URL to:
http://192.168.1.189:8000
and the shared secret to match the internal_secret in the config.


Error

Whenever I try to start a recording, I get this in the Nextcloud log:

Client error: `POST http://192.168.1.189:8000/api/v1/room/ym7nu2gk` resulted in a `403 FORBIDDEN`

And:

Failed to send message to recording server

Any suggestions on debugging this ?