▶ Why does spreedbackend still refuse to start its HTTPS listener even though valid cert/key files are mounted and readable at /config/fullchain.pem and /config/privkey.pem? tup: Running Nextcloud Talk with the High Performance Backend (HPB) using Docker Compose. Services: spreedbackend, nats, j…

Hello, how is the docker container configured? Did you bridge the host port to the port of the container or what network is the container using? Seems like you are proxying to the host port without any connection to the container which is running the service. And why are you running the signaling se…

Thanks for the pointers. To clarify how I’ve got things set up: Networking: I originally used network_mode: host, but I’ve now switched to an explicit port mapping (8080:8080). I can see docker-proxy listening on the host, so Apache can reach the container. SSL termination: You’re right — the …

Hello, did you use the nextcloud/aio-talk image for your configuration? If so, I can share my compose parameters with you for reference; everything is working fine for me now.

thanks for offering! I don’t think we used the nextcloud/aio-talk image in our setup, but I’m definitely open to trying it if it makes things smoother. To be honest, I’ve been leaning on AI guidance to get this working, but it hasn’t quite solved the puzzle yet. I’d really appreciate seeing your com…

Okay, first, the compose parameters: Use the high-performance backend image from aio, NC_DOMAIN = Your Nextcloud domain TALK_HOST = Your Talk domain compose👇 nextcloud-talk-hpb: image: nextcloud/aio-talk:20251128_084214 container_name: nextcloud-talk-hpb restart: always environment: NC_DOMAI…

Then, for the reverse proxy parameters: Since my Nginx container and Nextcloud container are on the same Docker network, I entered the Docker IP address, which is 172.18.0.10. I then configured Talk to be accessible through Nextcloud; for example, if my Nextcloud domain is ne.nextcloud.com:8888 , t…

[image] Enter the SIGNALING_SECRET parameter here

@crimsoncomputers you may want to take a look at the community how-to as well: [image] High Performance Backend for Talk on Nextcloud with Docker 📑 How to High Performance Backend for Talk on Nextcloud with Docker Talk:HPB Nextcloud Talk documentation How to i…

[QQ20251211-224548] For STUN servers, enter your domain name followed by +3478. Remember to map port 3478. For TURN servers, enter “turn and turns” followed by your domain name. Do not include +3478 port here. The key is - TURN_SECRET UDP and TCP.

Hi scubamuc. I think you’re a very meticulous person. Could you perhaps offer some feedback on my entire NextCloud Compose configuration, specifically the parameters I’ll upload them later.:star_struck: