Nextcloud version (eg, 18.0.5):
Operating system and version (eg, Ubuntu 18.04):
Apache or nginx version (eg, Apache 2.4.25):
PHP version (eg, 7.2):
i wanted to install the new opensource part of Nextcloudtalk the HP-Backend from Struktur AG. I followed the Setup guide over github and used this tutorial: https://morph027.gitlab.io/blog/nextcloud-spreed-signaling/
For testing purposes all parts of the HPB are on the same machine where the nc is located which shouldnt matter(public IP). I’m running nats, janus and coturn with the signalserver in front of it.
When i do:
curl -i https://myserver.domain.invalid/standalone-signaling/api/v1/welcome
i get the expected answer from the server. http 200: OK
I put in the servername/standalone-signaling:port in the nextcloud app of the admin panel.
From my main PC i can login as User X and being called through NC talk App by my smartphone.(Wifi-connected, Android). When i change over to my notebook, sitting on the same network as the main pc and smartphone using the same user i get the the error message “failed to establish signal connection”. When i login via webbrowser on my smartphone and try to start a call i get the same message, still wifi connected. All in all i could only achieve a connection from the main pc to the nc talk smartphone app. Whats wrong here?
Btw: I’ve added the coturn server in the turnserver section of the adminpanel. The buildin test says its answering as expected.
Is this the first time you’ve seen this error? (Y/N): y
Steps to replicate it:
- Install NC stable Channel with NC talk 8.0.9
- Follow github and https://morph027.gitlab.io/blog/nextcloud-spreed-signaling/
- try to call
The output of your Nextcloud log in Admin > Logging:
Nothing to see, related to spreed or talk
Thanks for your advice and help!
After more testing time i can be a little bit more precise: It is possible to call someone on the NC over my Firefox on the main PC, wether private mode or not. It is not possible to call someone over google chrome from the main pc or other enddevices. The person which i’m calling can only answer or call over the Nextcloud Android App. Everything es doesnt work so far…
For all interrested, it was a problem with my nginx Proxy configuration. I’ve used a selfsigned certificate while pointing on a dns name with a lets encrypt cert. That confused the system
The NextcloudTalk app showed me the cert at the beginning an i accpeted it, while believing it was setup correctly. The same must happen in the firefox browser in one of the steps so the cert was known. So if youre running your Tests with HPB and the NC on the same DNS/Host be sure to point to the right cert !