Spreed.me 0.3.6 on nginx 1.11.8 reports 502 Bad Gateway

Need a little bit help for setting up my Spreed.ME Server on Nginx 1.11.8 under ubuntu 16.04.1

What i did:

NGinx and Nextcloud (11.0.1) are running properly with redis-server and PHP 7.0.15

To install Spreed.ME I installed the spreed-webrtc-server by using this tutorial
https://github.com/strukturag/nextcloud-spreedme/blob/master/README.md#installation--setup-of-a-spreed-webrtc-server

-> sudo apt-add-repository ppa:strukturag/spreed-webrtc-unstable
-> sudo apt-get update
-> sudo apt-get install spreed-webrtc

After that I edited my nginx configuration

/etc/nginx/nginx.conf
-> added

map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

/etc/nginx/conf.d
-> added

# Spreed WebRTC
location ^~ /webrtc {
    proxy_pass http://127.0.0.1:8080;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $connection_upgrade;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header Host $http_host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

    proxy_buffering             on;
    proxy_ignore_client_abort   off;
    proxy_redirect              off;
    proxy_connect_timeout       90;
    proxy_send_timeout          90;
    proxy_read_timeout          90;
    proxy_buffer_size           4k;
    proxy_buffers               4 32k;
    proxy_busy_buffers_size     64k;
    proxy_temp_file_write_size  64k;
    proxy_next_upstream         error timeout invalid_header http_502 http_503 http_504;
}

into my nextcloud.conf (where all settings for the nextcloud-server are)

After that I installed the spreed.me app under nextcloud -> Apps -> Tools -> Spreed.ME -> enable

Then I changed to the Administration and created a new config by using

“Generate Spreed WebRTC config”

Under /etc/spreed i made a copy of the existig webrtc.conf -> webrtc.bak and touched a new one of webrtc.conf

I pasted all settings of the generated WebRTC config to that webrtc.conf and restartet the server

sudo service spreed-webrtc restart

I saved my config under nextcloud, so that in my oc_appconfig table contents my settings

Under /etc/spreed/webrtc.conf i added the following line

stunURIs = stun:stun.spreed.me:443

because i don’t have an own stun or turn server running!

Now i restarted the server

After everything seems to be fine i tried to connect my spreed.ME app by clicking the icon

-> then nginx reports error 502 Bad Gateway

in my log-file i’ve read

Error PHP file_get_contents(): php_network_getaddresses: getaddrinfo failed: Name or service not known at /var/www/nextcloud/apps/spreedme/helper/helper.php#186

and

Error PHP file_get_contents(https://api/v1/config): failed to open stream: php_network_getaddresses: getaddrinfo failed: Name or service not known at /var/www/nextcloud/apps/spreedme/helper/helper.php#186

The file and folder permissions under /var/www/nextcloud/apps/spreedme are the same like for all other apps

www-data:www-data drwxr-xr-x

Any ideas?

As tutorials i’ve used

https://www.c-rieger.de/enable-spreed-me-in-nextcloud/

my syslog is full of errors:

Jan 21 08:26:53 cloud systemd[1]: Started Spreed WebRTC server.
Jan 21 08:26:55 cloud systemd[1]: spreed-webrtc.service: Main process exited, code=exited, status=255/n/a
Jan 21 08:26:55 cloud systemd[1]: spreed-webrtc.service: Unit entered failed state.
Jan 21 08:26:55 cloud systemd[1]: spreed-webrtc.service: Failed with result ‘exit-code’.
Jan 21 08:26:56 cloud systemd[1]: spreed-webrtc.service: Service hold-off time over, scheduling restart.
Jan 21 08:26:56 cloud systemd[1]: Stopped Spreed WebRTC server.
Jan 21 08:26:56 cloud systemd[1]: Started Spreed WebRTC server.
Jan 21 08:26:56 cloud systemd[1]: spreed-webrtc.service: Main process exited, code=exited, status=255/n/a
Jan 21 08:26:56 cloud systemd[1]: spreed-webrtc.service: Unit entered failed state.
Jan 21 08:26:56 cloud systemd[1]: spreed-webrtc.service: Failed with result ‘exit-code’.
Jan 21 08:26:56 cloud systemd[1]: spreed-webrtc.service: Service hold-off time over, scheduling restart.
Jan 21 08:26:56 cloud systemd[1]: Stopped Spreed WebRTC server.
Jan 21 08:26:56 cloud systemd[1]: Started Spreed WebRTC server.
Jan 21 08:26:56 cloud systemd[1]: spreed-webrtc.service: Main process exited, code=exited, status=255/n/a
Jan 21 08:26:56 cloud systemd[1]: spreed-webrtc.service: Unit entered failed state.
Jan 21 08:26:56 cloud systemd[1]: spreed-webrtc.service: Failed with result ‘exit-code’.
Jan 21 08:26:57 cloud systemd[1]: spreed-webrtc.service: Service hold-off time over, scheduling restart.
Jan 21 08:26:57 cloud systemd[1]: Stopped Spreed WebRTC server.
Jan 21 08:26:57 cloud systemd[1]: Started Spreed WebRTC server.
Jan 21 08:26:57 cloud systemd[1]: spreed-webrtc.service: Main process exited, code=exited, status=255/n/a
Jan 21 08:26:57 cloud systemd[1]: spreed-webrtc.service: Unit entered failed state.
Jan 21 08:26:57 cloud systemd[1]: spreed-webrtc.service: Failed with result ‘exit-code’.
Jan 21 08:26:57 cloud systemd[1]: spreed-webrtc.service: Service hold-off time over, scheduling restart.
Jan 21 08:26:57 cloud systemd[1]: Stopped Spreed WebRTC server.
Jan 21 08:26:57 cloud systemd[1]: Started Spreed WebRTC server.
Jan 21 08:26:57 cloud systemd[1]: spreed-webrtc.service: Main process exited, code=exited, status=255/n/a
Jan 21 08:26:57 cloud systemd[1]: spreed-webrtc.service: Unit entered failed state.
Jan 21 08:26:57 cloud systemd[1]: spreed-webrtc.service: Failed with result ‘exit-code’.
Jan 21 08:26:57 cloud systemd[1]: spreed-webrtc.service: Service hold-off time over, scheduling restart.
Jan 21 08:26:57 cloud systemd[1]: Stopped Spreed WebRTC server.
Jan 21 08:26:57 cloud systemd[1]: spreed-webrtc.service: Start request repeated too quickly.
Jan 21 08:26:57 cloud systemd[1]: Failed to start Spreed WebRTC server.

my /etc/spreed/webrtc.conf looks like

; Minimal Spreed WebRTC configuration for Nextcloud

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

[app]
sessionSecret = my.secrets
encryptionSecret = my.secrets
authorizeRoomJoin = true
serverToken = my.token
serverRealm = local
extra = /var/www/nextcloud/apps/spreedme/extra
plugin = extra/static/owncloud.js
stunURIs = stun:stun.spreed.me:443

[users]
enabled = true
mode = sharedsecret
sharedsecret_secret = my.secrets

but
The command

sudo service spreed-webrtc restart

reports no errors in terminal!

After some checks i restarted the webrtc manually but errors in syslog resists:

Jan 21 09:20:26 cloud systemd[1]: Started Spreed WebRTC server.
Jan 21 09:20:26 cloud systemd[1]: spreed-webrtc.service: Main process exited, code=exited, status=255/n/a
Jan 21 09:20:26 cloud systemd[1]: spreed-webrtc.service: Unit entered failed state.
Jan 21 09:20:26 cloud systemd[1]: spreed-webrtc.service: Failed with result ‘exit-code’.
Jan 21 09:20:26 cloud systemd[1]: spreed-webrtc.service: Service hold-off time over, scheduling restart.
Jan 21 09:20:26 cloud systemd[1]: Stopped Spreed WebRTC server.
Jan 21 09:20:26 cloud systemd[1]: Started Spreed WebRTC server.
Jan 21 09:20:26 cloud systemd[1]: spreed-webrtc.service: Main process exited, code=exited, status=255/n/a
Jan 21 09:20:26 cloud systemd[1]: spreed-webrtc.service: Unit entered failed state.
Jan 21 09:20:26 cloud systemd[1]: spreed-webrtc.service: Failed with result ‘exit-code’.
Jan 21 09:20:27 cloud systemd[1]: spreed-webrtc.service: Service hold-off time over, scheduling restart.
Jan 21 09:20:27 cloud systemd[1]: Stopped Spreed WebRTC server.
Jan 21 09:20:27 cloud systemd[1]: Started Spreed WebRTC server.
Jan 21 09:20:27 cloud systemd[1]: spreed-webrtc.service: Main process exited, code=exited, status=255/n/a
Jan 21 09:20:27 cloud systemd[1]: spreed-webrtc.service: Unit entered failed state.
Jan 21 09:20:27 cloud systemd[1]: spreed-webrtc.service: Failed with result ‘exit-code’.
Jan 21 09:20:27 cloud systemd[1]: spreed-webrtc.service: Service hold-off time over, scheduling restart.
Jan 21 09:20:27 cloud systemd[1]: Stopped Spreed WebRTC server.
Jan 21 09:20:27 cloud systemd[1]: spreed-webrtc.service: Start request repeated too quickly.
Jan 21 09:20:27 cloud systemd[1]: Failed to start Spreed WebRTC server.

Sorry folks!

I should have read this posting before:

"…

In /etc/spreed/webrtc.conf I had to add this to http section:

root = /usr/share/spreed-webrtc-server/www/

If installed from repositories for Ubuntu seems to be mandatory.

…"

To uncomment the line in webrtc.conf did the trick :slight_smile:

Again - sorry for double post :frowning:

1 Like