HPB invalid version as unreleased

Dear all,

I am trying to set up the HPB environment t ouse TALK for my first demo Nextcloud environment. The UBUNTU Server is established and the web interface already running.

My issue is to establish the HPB to the cloud environment.
The failure message in German:
Fehler: Aktuelle Version: unreleased; Server muss aktualisiert werden, um mit dieser Version von Talk kompatibel zu sein.

I tried to establish the version within the conf - File:

[app]
debug = false
version = 1.1.0

[log]
level = debug

[http]
enabled = true
listen = 127.0.0.1:8080

[server]
listen = 127.0.0.1:8080
version = 1.1.0

[sessions]

hashkey = xxx
blockkey = xxx

[clients]
internalsecret = xxx

[backend]
backends = maincloud

[backend-maincloud]
url = https://demo.wics-forensics.de
secret = xxx
sessionlimit = 0

[nats]
url = nats://127.0.0.1:4222

And the output here:

root@ubuntu:/etc/apache2/sites-enabled# curl -i http://127.0.0.1:8080/api/v1/welcome

HTTP/1.1 200 OK

Content-Type: application/json; charset=utf-8

Server: nextcloud-spreed-signaling/unreleased

X-Spreed-Signaling-Features: audio-video-permissions, dialout, hello-v2, incall-all, switchto, transient-data, welcome

Date: Fri, 06 Mar 2026 15:28:47 GMT

Content-Length: 64

Any idea to fix the issue, so that the web admin interface will be able to connect to the HPB?

Many thanks for your help.

BR

Support intro

Sorry to hear you’re facing problems :slightly_frowning_face:

help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.

In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:

example

Or for longer, use three backticks above and below the code snippet:

longer
example
here

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can :heart:

Some useful links to gather information about your Nextcloud Talk installation:
Information about Signaling server: /index.php/index.php/settings/admin/talk#signaling_server
Information about TURN server: /index.php/settings/admin/talk#turn_server
Information about STUN server: /index.php/settings/admin/talk#stun_server

Nextcloud version (eg, 24.0.1): replace me
Talk Server version (eg, 14.0.2): replace me
Custom Signaling server configured: yes/no and version
Custom TURN server configured: yes/no
Custom STUN server configured: yes/no

In case the web version of Nextcloud Talk is involved:
Operating system (eg, Windows/Ubuntu/…): replace me
Browser name and version (eg, Chrome v101): replace me

In case mobile Nextcloud Talk apps are involved:
Talk iOS version (eg, 14.0.2): replace me
Talk Android version (eg, 14.0.2): replace me

The issue you are facing:

Is this the first time you’ve seen this error? (Y/N):

Steps to replicate it:

The output of your Nextcloud log in Admin > Logging or errors in nextcloud.log in /var/www/:

PASTE HERE

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

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

PASTE HERE

What version? How did you install it?

e.g., Quick install - Nextcloud Talk API documentation

Your version is being reported as unreleased and lacks federation in the feature list from what I see.

The installation was quite easy. It is an Ubuntu Server with apache2.

I just downloaded the zip und unzipped it. The cloud itself is well working, only Talk is struggling at the moment.

Nextcloud version 33.0.0

Talk version is 23.0.1

I just downloaded the zip und unzipped it.

The zip of what?

Of Nextcloud Spreed Signaling?

Keep in mind you left all the requested info blank so we have no idea what you have/did.

I used this link to download the full package for installation


# Download lastest nextcloud version

cd /tmp && wget https://download.nextcloud.com/server/releases/latest.zip

unzip latest.zip

mv nextcloud /var/www/

I don’t have a Docker container in use. The server is only hosting the cloud environment with the versions above.

That’s just for Nextcloud Server itself.

You installed the HPB somehow right?

@WICS-Forensics the ubuntu packages of HPB are deprecated. you have to build the packages from source. see: Nextcloud Talk-/Signaling - Server v. 2.x mit Nextcloud Recording-Backend - Carsten Rieger

@all: if someone knows a .deb source for janus and nextcloud-spreed-signaling plz let me know.

1 Like

nextcloud-spreed-signaling is in the Debian and Ubuntu repositories:

https://packages.debian.org/search?searchon=sourcenames&keywords=nextcloud-spreed-signaling

https://launchpad.net/ubuntu/+source/nextcloud-spreed-signaling

The same goes for janus. However, for some reason, in Deban, it is only included in Bookworm, Forky (testing), and Sid and not Trixie.

https://packages.debian.org/search?searchon=sourcenames&keywords=janus

https://launchpad.net/ubuntu/+source/janus

Ubuntu Launchpad says: Last Upload v2.0.2 - Actual version in git is v2.1.0 Feb 03
So maybe v33 of nextcloud might not be supported. Or?

Not sure, tbh. as I don’t really use Talk myself, so I haven’t installed the HPB.

But yes, that’s the general problem with distribution packages for distributions with fixed release cycles. You never get the latest version or specific versions of most packages. That’s why I use third-party repos for almost everything relevant to Nextcloud (PHP, Apache, MariaDB, Redis). For PHP and Apache, I use Sury (which is semi-official, as Sury is the maintainer of these packages at Debian) and the official repositories from mariadb.org and redis.

Unfortunately, afaik, there are no official deb packages or repositories for Janus and the signaling server, and I would always be cautious with unofficial ones (I’m not aware of any, by the way).

So, in the end, if you want to be up to date, the only options, I’m aware of, are to compile it yourself or use Docker: GitHub - strukturag/nextcloud-spreed-signaling: Standalone signaling server for Nextcloud Talk. · GitHub.

If you’re going to use Docker, though, you might as well try the AIO-Talk-HPB container. It’s probably the easiest way to get the Talk-HPB up and running: Quick install - Nextcloud Talk API documentation.

A third option in this case might also be to use Debian Unstable (Sid). If you run the HPB on a separate server and are familiar with Debian, this could actually be a viable option. If Nextcloud also runs on this server, definitely not, because then other things would be too new again, e.g., MariaDB or PHP. :wink:

However, if it is more than a home instance, i.e., if it is used productively and commercially, I would not recommend either the Stable/LTS distro packages or Debian SID, and for a smaller instance, I would probably just go with the AIO container. For larger instances >50 or 100? users, or if you need to scale or distribute components across multiple servers, I’m not sure, but then you’re already in the realm of the Nextcloud Enterprise subscription anyways :wink:

that includes a prebuild and supported version of spreed and janus?

btw: in my case it’s more to renovate and complete my playbooks. the talk part i started with c. riegers howto but wanted to replace the build-yourself binaries with standard packages in “official” repos. as you would do. just to learn that they - kind of - don’t exist. now i ended up with a role to build it from source. (not yet released. still testing.)