Freezing splashscreen webrtc-server with nextcloud-spreedme-app

Hi

The nextcloud-app can’t connect to spreed-webrtc-server anymore.

Splashscreen (funny face) is freezing. IOS-Apps (Spreed.me) runs smoothly with chat, video-/audiocalls.

any idea ?

config.php

 <?php
    namespace OCA\SpreedME\Config;
    class Config {
    	const SPREED_WEBRTC_ORIGIN = 'https://webrtc.mydomain.com';
    	const SPREED_WEBRTC_BASEPATH = '/webrtc/';
    	const SPREED_WEBRTC_SHAREDSECRET = ***;
    	const SPREED_WEBRTC_IS_SHARED_INSTANCE = false;
    	const OWNCLOUD_TEMPORARY_PASSWORD_LOGIN_ENABLED = false;
    	const OWNCLOUD_TEMPORARY_PASSWORD_SIGNING_KEY = ***;
    	private function __construct() {
    	}
    }

server.conf

[http]
listen = 127.0.0.1:8080
basePath = /webrtc
root = /usr/local/share/spreed-webrtc-server/www

[app]
sessionSecret = ***
encryptionSecret = ***
authorizeRoomJoin = true
serverToken = ***
serverRealm = local
extra = /var/www/nextcloud/apps/spreedme/extra
plugin = extra/static/owncloud.js
turnURIs = turn:turn.mydomain.com:3478?transport=udp turn:turn.mydomain.com:3478?transport=tcp
turnSecret = ***
[users]
enabled = true
mode = sharedsecret
sharedsecret_secret = ***

/admin/debug:

Spreed.ME Version 0.3.4
Ran test #1 (testOwncloudPhpConfigFile):
   Passed without an error
Ran test #2 (testOwncloudJavascriptConfigFile):
   Passed without an error
Ran test #3 (testSpreedWebRTCAPI):
   Passed without an error
Passed all tests. Everything seems to be set up correctly! :) 

virtualhost from nextcloud-server (LXC)

<VirtualHost *:443>
	ServerName webrtc.mydomain.com
        SSLEngine on
        SSLCertificateFile …path/fullchain.pem
        SSLCertificateKeyFile …path/privkey.pem
	ServerAdmin webmaster@localhost
        DocumentRoot /var/www/html
	Header always add Strict-Transport-Security "max-age=15768000; includeSubDomains; preload"
	ErrorLog ${APACHE_LOG_DIR}/error.log
	CustomLog ${APACHE_LOG_DIR}/vhost_02_access.log combined

    <Location /webrtc>
        ProxyPass http://192.168.0.132:80/webrtc
        ProxyPassReverse /webrtc
    </Location>

    <Location /webrtc/ws>
        ProxyPass ws://192.168.0.132:80/webrtc/ws
    </Location>
    ProxyVia On
    ProxyPreserveHost On
    RequestHeader set X-Forwarded-Proto 'https' env=HTTPS
</VirtualHost>

virtualhost from spreed-webrtc-server (LXC - 192.168.0.132)

<VirtualHost *:80>
ServerAdmin webmaster@localhost
ServerName webrtc.mydomain.com
DocumentRoot /var/www/html
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
  <Location /webrtc>
  ProxyPass http://127.0.0.1:8080/webrtc
  ProxyPassReverse /webrtc
  </Location>
  <Location /webrtc/ws>
  ProxyPass ws://127.0.0.1:8080/webrtc/ws
  </Location>
  ProxyVia On
  ProxyPreserveHost On
  RequestHeader set X_FORWARDED_PROTO 'https' env=HTTPS
</VirtualHost>

Hi @bassano,

please take a look at your browser developer console, it almost certainly includes useful information:

  1. Open the Spreed.ME app in Nextcloud
  2. Append ?debug to the URL, e.g. https://domain.com/index.php/apps/spreedme/?debug
  3. Now open your browser’s dev console:
  4. Right click on the Nextcloud site
  5. Click “Inspect element” (very bottom)
  6. Check what it says in the console and paste it to https://pastebin.ubuntu.com/
  7. Post the link to your pastie here

https://pastebin.ubuntu.com/23559164/

main.js:47 Uncaught SyntaxError: Unexpected token m in JSON at position 1

Haven’t seen that one before. Definitely some strange things going on.
Where did you get Spreed WebRTC from? Did you install it from source or did you use the Ubuntu package? Which version are you running? (find out with $ spreed-webrtc-server -v)

Hi @leon

no user want to hear this from a developer … :scream:

get spreed-source from https://github.com/strukturag/spreed-webrtc
get go-source from https://github.com/golang/go

install it on a raspbian via

- git clone [URL]
- ./autgen.seh
- ./configure
- make
- make install

versions:

- nodejs v7.2.0
- go version devel +7e45516
- autoconf 2.69
- automake 1.14.1
- spreed: Version unreleased

because of the raspbian if have to build it from source … no arm-package available (but the RPI is great for this job :slight_smile: )

should i rebuild the ubuntu-package with apt against building it from source ?

greets !