Error setup Talk High Performance Backend

ā„¹ļø Support šŸ’¬ Talk (spreed)
, , , , ,
1

Nextcloud version (eg, 24.0.1): 31.0.7
Talk Server version (eg, 14.0.2): 21.1.2
Custom Signaling server configured: latest docker
Custom TURN server configured: inside docker
Custom STUN server configured: inside docker

In case the web version of Nextcloud Talk is involved:
Operating system (eg, Windows/Ubuntu/ā€¦): Linux 6.8.12-11-pve x86_64
Browser name and version (eg, Chrome v101): Chrome v138

The issue you are facing:

I have 2 Ubuntu containers inside Proxmox Virtual Environment machine.
Both containers are on same local network anche can access internet.

Inside fisrt container Iā€™ve installed Nextcloud (Apache2 + downloaded zip from nextcloud website).
Inside second container Iā€™ve put docker with HPB, but I canā€™t make them connectā€¦

Nextcloud_Talk_HPB
Nextcloud_Talk_HPB1121Ɨ264 16.1 KB

Nextcloud_Talk_HPB_2
Nextcloud_Talk_HPB_21553Ɨ472 23.2 KB

Is this the first time youā€™ve seen this error? (Y/N): First time I try to setup Nextcloud!

Steps to replicate it:
followed steps in the HPB docker guide

The output of your Nextcloud log in Admin > Logging or errors in nextcloud.log in /var/www/:
https://bin.disroot.org/?c4fbc5dd28304a0a#F7k6cVqdKox8VqP9crsNn54qURpjHe5AJB6ypPrET6GN

The output of your Apache/nginx/system log in /var/log/apache2/access.log:

Your browser log if relevant (javascript console log, network log, etc.):

Nextcloud_Talk_HPB_console1
Nextcloud_Talk_HPB_console11078Ɨ854 39.2 KB

Nextcloud_Talk_HPB_console2
Nextcloud_Talk_HPB_console21053Ɨ388 19.1 KB

What I tried so far on HPB container (outside docker shell):

compose.yaml

Apache2 configuration on HPB container:

ufw allow 3478/tcp
ufw allow 3478/udp

docker compose up -d
docker compose logs

https://bin.disroot.org/?1784fa6a670572f8#BJctbThRKJSCSAiCPftawsrXQe2vtxrGBddBVfUxAG6Q

curl http://localhost:8181/api/v1/welcome
{"nextcloud-spreed-signaling":"Welcome","version":"2.0.3~docker"}

curl -i http://172.17.0.2/standalone-signaling/api/v1/welcome
curl: (7) Failed to connect to 172.17.0.2 port 80 after 3102 ms: Could not connect to server

curl -i http://172.17.0.1/standalone-signaling/api/v1/welcome
HTTP/1.1 404 Not Found
Date: Wed, 23 Jul 2025 16:11:26 GMT
Server: Apache/2.4.63 (Ubuntu)
Content-Length: 272
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL was not found on this server.</p>
<hr>
<address>Apache/2.4.63 (Ubuntu) Server at 172.17.0.1 Port 80</address>
</body></html>
2

hey @LabRossiOffice welcome to the community :waving_hand:

weā€™re missing a reverse proxy, do you have one in place?

judging by your logs, neither your nextcloud instance, nor the signal service have a valid SSL certificate and need to be encryptedā€¦ see

3

A post was split to a new topic: Problem setting up talk

4

Hello, Iā€™ve left encryption out honestly because I thought about making it work first and then add it later on, didnā€™t read it was an hard requirement (my instance is just for test and is not publicly exposed).

About proxy isnā€™t these lines of HPB Apache2 config relevant?

ServerName signal.nuvoletta.succ

ProxyPass / http://192.168.2.140:8181/ upgrade=websocket

RequestHeader set X-Forwarded-Proto expr=%{REQUEST_SCHEME}
RequestHeader set X-Real-IP expr=%{REMOTE_ADDR}

If not, can it be achieved with Apache2 or should I install NGINX?

Thanks!

5

thatā€™s your issue, its clear in the docs that your cloud instance and signal need a valid certificates to work.

whichever you preferā€¦ while some folks use other proxies the docs below were created using NPM see

see developersā€™ docs

6

Hello, Iā€™ve changed my Apache2 config as foolows:

<VirtualHost *:443>
        ServerAdmin webmaster@localhost

        ServerName signal.nuvoletta.succ

        # Enable proxying Websocket requests to the standalone signaling server.
        ProxyPass "/standalone-signaling/"  "ws://127.0.0.1:8080/"

        RequestHeader set X-Real-IP %{REMOTE_ADDR}s

        RewriteEngine On
        # Websocket connections from the clients.
        RewriteRule ^/standalone-signaling/spreed/$ - [L]
        # Backend connections from Nextcloud.
        RewriteRule ^/standalone-signaling/api/(.*) http://127.0.0.1:8080/api/$1 [L,P]

        ErrorLog ${APACHE_LOG_DIR}/error.log
        CustomLog ${APACHE_LOG_DIR}/access.log combined

        SSLEngine on

        SSLCertificateFile      /etc/ssl/certs/ssl-cert-snakeoil.pem
        SSLCertificateKeyFile   /etc/ssl/private/ssl-cert-snakeoil.key
       ...

Now instead of previous error in Talk settings webpage, I get ā€œError: server response 404ā€.