Open kstawiski opened 7 years ago
Which version of Apache are you using? Did you enable all required Apache modules ($ a2enmod proxy proxy_http proxy_wstunnel headers
)?
Thank you very much for your interest. The version is up to date and modules are enabled.
konrad@gen:~$ apache2 -v
Server version: Apache/2.4.18 (Ubuntu)
Server built: 2016-07-14T12:32:26
konrad@gen:~$ a2enmod proxy proxy_http proxy_wstunnel headers
Module proxy already enabled
Considering dependency proxy for proxy_http:
Module proxy already enabled
Module proxy_http already enabled
Considering dependency proxy for proxy_wstunnel:
Module proxy already enabled
Module proxy_wstunnel already enabled
Module headers already enabled
I have also noticed that there are no icons shown.
I tried to change ws://
to wss://
and therefore reconfigured server config. However no change occured. I'm able to chat but not to send files and one can pick up a call but it gets diconnected just after picking up.
Any ideas why?
Cheers, Konrad
Please check the developer console of your browser:
Same problem here, chat works, app works, I can call myself from 2 different pcs with 2 different accounts fine (same ip), but calling a friend to test it with will just hang up instantly.
Error while reading 20 websocket: close 1001 (going away)
No error in apache logs.
I have Nginx configured as a reverse-proxy, same issue of @coolmodi. I can call myself from the same IP flawlessly but I have Error while reading 2 websocket: close 1001 (going away)
in the spreed server logs when trying to communicate from different addresses.
Any news on this problem?
Same here. I have installed spreed as a Docker Container. Videocalls work fine when using Spreed with two devices which are in the same private network (LAN).
Did anybody solve the problem?
Console in the browser gives me following warning/error when using the ?debug
parameter:
onaddstream is deprecated! Use peerConnection.ontrack instead.
RTCSessionDescription's members are readonly! Writing to them is deprecated and will break soon!
ICE failed, add a STUN server and see about:webrtc for more details (unbekannt)
I also tried to enable debugging in about:webrtc
(Firefox 53.0 on Kubuntu 16.04) but the generated file /tmp/WebRTC.log
stays empty after the call fails.
Got the same error here. Tried from different machines, different operating systems, different browsers even different nextcloud servers. Same result. Call got hung up 2sec after it is established. Firebug shows nothing. Seems to be a bigger problem, no?
Seems i got it working by adding:
stunURIs = stun:stun.spreed.me:443
to the spreed-webrtc config.
@himbeere in which file did you add the line stunURIs = stun:stun.spreed.me:443
Doesn't that mean that you are connecting to a different server (a server which is operated by spreed.me)?
This makes it useless somehow to install Spreed on your own server, or am I missing something here?
@tarator This options goes to the spreed-webrtc config file under [app]. As for your other question. You can run your own stun server. For example stuntman: http://www.stunprotocol.org/. What an stun server does is explained in the RFC: http://www.ietf.org/rfc/rfc3489.txt
@himbeere thanks for clarification. It worked for me with adding the following stun-server to my spreed-me.conf
[app]
....
stunURIs = stun:stun.stunprotocol.org:3478
....
Maybe I will try to set up my own stun server another time.
Hi! I have encountered strange error with spreed-webrtc and owncloud. I have ssl-protected apache2 webhost with setup reverse proxy to webrtc like this:
Chat and app in general seems to work, but calls disconnects after picking up and one cannot for example send a file in chat (the file is uploaded but cannot be downloaded by recipent). It seems like a problem with websocket forwarding but I cannot diagnose one.
Log in console is looking like this:
Best wishes, Konrad