Talk HPB on debian 13

ℹ️ Support
,
1

Hello all,

Debian 13 was released a bit more than month ago, so I wanted to prepare my migration to a new system together with it.

So far so good, only I realised reasonably quickly that the janus package was not available in the repos of debian 13.

So I am wondering what solution people who already migrated to 13 have solve this hickup.

I am not using the aio container, but a classic system install.

2

Well, maybe you should consider doing that, as it would make your life a lot easier.

Other than that, I wouldn’t know what else to do either. Basically, you have the following options:

  • Build it yourself
  • Use the package from forky/testing, with all the risks that a FrankenDebian can bring (not recommended, especially if the HPB is running on the same server as Nextcloud)
  • There might be a chance it lands in Trixie backports at some point, but I guess, you’d have to ask the Debian maintainers about that: janus - Debian Package Tracker

Personally, I would at least try the AIO Docker image. If that doesn’t work out for you, hold off on upgrading your production server to Trixie. Instead, test the HPB and Trixie on a separate server (if you don’t already have the HPB on a separate server, which is recommended for optimal performance).

Oh, and by the way, in case you’re also running MariaDB directly on the same server, that’s yet another reason to hold off on the upgrade — until Nextcloud officially supports MariaDB 11.8.

3

you could try this:

4

Yes, but if I understand it correctly, this uses the exact Nextcloud AIO Talk HPB image that the OP said they are not using. :wink:

ghcr.io/nextcloud-releases/aio-talk:latest
1 Like
5

its too early to read carefully :zany_face: sorry… thanks for pointing that out. It’ll get better after the first three cups of coffee, promise :rofl:

6

Well, I have to admit, that after reading it again, it’s not entierly clear, whether OP actually meant AIO as such or just the AIO Talk container, so they may indeed not know that the AIO Talk container can also be used with a bare-metal Nextcloud.

Anyway, using the container image for the Talk HPB would definitely be the easiest solution, and if OP decides to give it a try, the link to the instructions would of course be useful. :slight_smile:

2 Likes
7

Thanks for the answers.

I am definitely happier to not have to build it myself. So using a container is likely the route this will take.

I’ll have a look at the talk image from the aio. (have to remove the turn server from it, because I already have one doing this job elsewhere)

I am not using the aio simply because my nextcloud instance is following me since about 10 years and back then, it was not a thing … and I never migrated to it. (never even lookep-up how it should be done).

8

After looking a bit further at the docker image and what/how all is configured in there, I think I can change it a bit to adapt it to what I have (turn server is already running elsewhere).
I’ll hopefully update later this week if I manage to get to it.

Update: After spending a bit of time on it, I got it to work. the main points:

  • remove eturnal from supervisord because it is already running elsewhere on a different port
  • add the stun server and port with sed in the config of janus (janus was complaining about this in the logs).

I edit this post since topics get closed a bit too fast here.

So, it works using the something based on the Dockerfile of the aio image!

9

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.