(Found the hardware requirements… AMD64…)
Ok, with same host you mean physical same server in this case right?
Nothing I can do like with Collabora and a reverse proxy
It is talking about different origin, but with this in my nextcloud hosts file:
RequestHeader set X-Forwarded-Proto 'https' env=HTTPS
Installing the docker on my secondary server xxx.xxx.xxx.xx2
Having this pre generated server.conf in /srv/extra/
; Minimal Spreed WebRTC configuration for Nextcloud
listen = 0.0.0.0:8080
basePath = /webrtc/
;root = /usr/share/spreed-webrtc-server/www
sessionSecret = xxxxxxxxxxxxx
encryptionSecret = xxxxxxxxxxxxx
authorizeRoomJoin = true
serverToken = xxxxxxxxxxxxxxx
serverRealm = local
;extra = /home/share/public_html/apps/spreedme/extra
;plugin = extra/static/owncloud.js
enabled = true
mode = sharedsecret
sharedsecret_secret = xxxxxxxxxxxxxxx
Running docker as
docker run --rm --name my-spreed-webrtc -p 8080:8080 -p 8443:8443 -v /srv/extra:/srv/extra -i -t spreed/webrtc -c /srv/extra/server.conf
On my nextcloud server renamed both spreed app config/config.php.in and extra/static/config/OwnCloudConfig.js.to config.php and OwnCloudConfig.js (removed the in and set the shared secret.
In the server.conf I changed the ip to 0.0.0.0. Root is commented. Now the paths in ‘extra’ and ‘plugin’ have values that cannot match as they refer to the primary. Changing them to URLS does’nt work either. I get error messages starting the docker. When I comment them out, I do get Spreed visible in my nextcloud setup.
But the message says I need to sign in to create a room.
Do I need to set a serverRealm than local? What do I do with “extra” and “plugin”?
I feel I am close… I am missing something…