Nextcloud Talk Signaling Server - now automated installation

enoch85 · September 2, 2020, 10:51am

Just spread the word about the VM and I’m happy

nomad · September 2, 2020, 3:22pm

I will!

Just installed the Signaling Server as well, worked without any issues. Still only 300 MB RAM in use! Maybe you can lower the minimum requirements to 1GB in the install script?

enoch85 · September 2, 2020, 3:38pm

Wow!

Problem is that people will complain when it’s slow, and there might be complications in a production environment as PHP-FPM is optimized for minimum use with 2 GB RAM.

I run the mirror (https://mirror.hanssonit.se) on 1 GB, and it works, but it’s sloooooow.

Django43 · September 2, 2020, 5:50pm

@all

Even if I’m not sure whether it really fits into the post.

I am looking for a working Docker version Nextcloud HPB (Talk Signaling Server).

I would not really like to install a VM because it represents another system and I already have more to do with my containers than I wanted.

Maybe someone from you can tell me if necessary. give a reference to a Docker compilation.

Many thanks

Django43

nomad · September 2, 2020, 8:03pm

I understand. My installation is very fast, actually, but only a few apps are installed.

Anyway, I was not so lucky with my second try on a more powerful VPS. Maybe it has something to do with the hostname not been changed before running the script, I don’t know. Or that only Ubuntu 18.04 minimal was available and I had to make a manual update?

The problem is with Talk. It works without the signaling server, but after installing it, I cannot start a call, I just get a spinning wheel. I always get 403 forbidden error:

GuzzleHttp\Exception\ClientException: Client error: POST https://talk.SIGNALING.DOMAIN.COM/api/v1/room/fj2yqbejresulted in a403 Forbidden response: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>403 Forbidden</title> </head><body> <h1>Forbidden (truncated...)

When I visit https://talk.SIGNALING.DOMAIN.COM/api/v1/room/fj2yqbej I get the friendly response

Hi there! :) If you see this page, the Apache2 proxy for Talk Signaling Server is up and running.

Reiner_Nippes · September 2, 2020, 8:23pm

Django43 · September 2, 2020, 9:16pm

@Reiner_Nippes

Thank you for your tip. I have already tried to install the Talk Signaling Server several times in the past and unfortunately failed.

If I read the package correctly, only the Talk Signaling Server is included. Unfortunately there is no description of the additional required packages and the installation. My hope was an “all-in” Docker image to make installation easier.

I think a step by step description would be a real help for many. Given the restrictions that still exist, a working video conferencing system - which could have at least 10-15 people participating - would be great.

Maybe there will still be someone who provides a tutorial and a corresponding Docker image.

Best wishes

Django43

enoch85 · September 3, 2020, 7:46am

Maybe you have to add the domain to /etc/hosts like in previous errors in this thread?

I actually have no idea right now, all the tests we did was working well. We tested on an UpCloud VPS with Ubuntu 20.04. I think it was 4 GB RAM and 4 CPU.

nomad · September 3, 2020, 8:49am

Thanks. That seemed to be the case. It was not necessary with the other installation, though. Anyway, it is working now, and with full text search installed it only uses 1.2 GB RAM. Great work, thanks a lot!

Reiner_Nippes · September 3, 2020, 12:10pm

the problem is that each container runs its own service. and that’s how it should work. of course you can can combine all the Dockerfiles below. and write a start script to start all service in that container.

https://github.com/strukturag/nextcloud-spreed-signaling/blob/master/Dockerfile
https://github.com/strukturag/nextcloud-spreed-signaling/blob/master/docker/coturn/Dockerfile

github.com

strukturag/nextcloud-spreed-signaling/blob/master/docker/janus/Dockerfile

# Modified from https://gitlab.com/powerpaul17/nc_talk_backend/-/blob/dcbb918d8716dad1eb72a889d1e6aa1e3a543641/docker/janus/Dockerfile
FROM alpine:3.18

RUN apk add --no-cache curl autoconf automake libtool pkgconf build-base \
  glib-dev libconfig-dev libnice-dev jansson-dev openssl-dev zlib libsrtp-dev \
  gengetopt libwebsockets-dev git curl-dev libogg-dev

# usrsctp
# 08 Oct 2021
ARG USRSCTP_VERSION=7c31bd35c79ba67084ce029511193a19ceb97447

RUN cd /tmp && \
    git clone https://github.com/sctplab/usrsctp && \
    cd usrsctp && \
    git checkout $USRSCTP_VERSION && \
    ./bootstrap && \
    ./configure --prefix=/usr && \
    make && make install

# libsrtp

This file has been truncated. show original

https://github.com/nats-io/nats-server/blob/master/docker/Dockerfile.alpine

but i guess you are better of with the docker-compose file
https://github.com/strukturag/nextcloud-spreed-signaling/blob/master/docker-compose.yml

f9fjd · September 24, 2020, 10:16am

is there any news when this comes to snap-version?

szaimen · September 24, 2020, 10:54am

@f9fjd sry to say but I doubt that this is possible with the snap. The snap is just too limited for that.

rakekniven · September 24, 2020, 1:33pm

Hello @kyrofa ,

you are the snap man, can you give a comment?

Thanks.

kyrofa · September 25, 2020, 3:44pm

I’d be happy to comment on how well (or not) this will run with the snap, but the signaling server isn’t a project with which I’m terribly familiar. Can someone point me at docs instead of shell scripts?

szaimen · September 25, 2020, 3:59pm

Maybe this helps?

enoch85 · September 25, 2020, 4:07pm

@kyrofaI I would consider this docs: https://github.com/strukturag/nextcloud-spreed-signaling

Otherwise, just read the scripts.

kyrofa · September 25, 2020, 4:26pm

Thank you @szaimen, that was helpful indeed. So it sounds like the interface between Nextcloud and the server is only network based. In that case, I see no reason you can’t point the Talk app from within the snap to your own server.

Note that the snap is not a VM, it’s just an application. You don’t need to somehow access it and install this server in there, you can install it on the same host running the snap (or even another, unrelated host), perhaps using the blog post @szaimen provided . The only difficulty you need to consider is confinement, because the application only has permission to do certain things. Thankfully, “talk on the network” is one of them, and it seems that’s all this would require.

enoch85 · September 25, 2020, 5:00pm

So it couldn’t be included in the snap itself?

In other words, you would need to install it separately from the snap which hosts Nextcloud, and then connect it with the snap?

kyrofa · September 25, 2020, 5:17pm

Sure it could be, in the same way that the snap could include openHAB if you also wanted smart home functionality out of it, but that doesn’t seem to be a proper separation of concerns . It seems better suited to be its own snap, or just traditionally installed.

onflow · November 11, 2020, 5:12pm

@enoch85 Thank you for all the work you do. I am co-hosting a medium-sized gathering (25-50 individuals) of folks coming up in 1.5 weeks and searching for a videoconference solution. I am wondering if you have had a chance to test the Nextcloud Talk Signaling Server script that you provide with groups of this size? Have you heard any discussion of anyone who has had a chance to test your script out in the wild?

I’ve got your script running beautifully presently and use it primarily as an individual user for the basic storage functions, but have all your other scripts installed and running behind a separate Nginx reverse proxy, but with also the necessary non-standard ports opened in my router firewall for the circumstances where the reverse proxy causes complications with my connection.

With gratitude. I very much appreciate all your contributions.