'No stream available' on both sides.

[bielej]

First, my setup:
Downloaded and extracted https://github.com/screego/server/releases/download/v1.0.1/screego_1.0.1_linux_arm64.tar.gz
I've build my own image using Dockerfile from https://github.com/screego/server/blob/master/Dockerfile

Finally, my docker-compose.yaml

version: "3.7"
services:
  screego:
    container_name: screego
    image: bielej/screengo
    ports:
      - 5050:5050
      - 3478:3478
    environment:
      SCREEGO_EXTERNAL_IP: "0.0.0.0"
      SCREEGO_TRUST_PROXY_HEADERS: "true"
      SCREEGO_AUTH_MODE: "none"
      SCREEGO_LOG_LEVEL: "debug"

That gives:

$ docker exec -it screego /screego --version
screego version 1.0.1; screego/server@fa388f6e59401059530fae9d6d15da809fe2abb7
$ docker ps | grep screego
28f5f4500155        bielej/screengo         "/screego serve"         5 minutes ago       Up 5 minutes            0.0.0.0:3478->3478/tcp, 0.0.0.0:5050->5050/tcp                                                   screego

That runs behind Nginx with proper HTTPS (using the config from https://screego.net/#/proxy?id=at-root-path).
I've tried both STUN and TURN - same result. Filling SCREEGO_EXTERNAL_IP with a real, valid IP address does not help.

In that example I've tried sharing a sample window.
The screen/window does not get shared.

Logs:

screengo   | 2020-10-06T16:03:55Z DBG Logger initialized
screengo   | 2020-10-06T16:03:55Z INF SCREEGO_SECRET unset, user logins will be invalidated on restart
screengo   | 2020-10-06T16:03:55Z INF Users file not specified
screengo   | 2020-10-06T16:03:55Z INF Start TURN/STUN addr=0.0.0.0:3478
screengo   | 2020-10-06T16:03:55Z INF Start HTTP addr=0.0.0.0:5050
screengo   | 2020-10-06T16:04:36Z DBG WebSocket Close code=1001 reason=
screengo   | 2020-10-06T16:04:44Z DBG WebSocket error="websocket: close 1006 (abnormal closure): unexpected EOF" type=read
screengo   | 2020-10-06T16:07:04Z DBG WebSocket Close code=1001 reason=
screengo   | 2020-10-06T16:07:29Z DBG WebSocket Close code=1001 reason=
screengo   | 2020-10-06T16:07:43Z DBG WebSocket Close code=1001 reason=
screengo   | 2020-10-06T16:07:59Z DBG WebSocket Close code=1000 reason="room with id test does already existn"
screengo   | 2020-10-06T16:07:59Z DBG WebSocket error="read tcp 172.23.0.2:5050->192.168.0.128:63295: use of closed network connection" type=read
screengo   | 2020-10-06T16:08:16Z DBG WebSocket Close code=1000 reason="room with id test does already existn"
screengo   | 2020-10-06T16:08:16Z DBG WebSocket error="read tcp 172.23.0.2:5050->192.168.0.128:63298: use of closed network connection" type=read
screengo   | 2020-10-06T16:08:21Z DBG WebSocket Close code=1001 reason=
screengo   | 2020-10-06T16:08:23Z DBG WebSocket Close code=1001 reason=
screengo   | 2020-10-06T16:08:24Z DBG WebSocket Close code=1000 reason="room with id test does not exist"
screengo   | 2020-10-06T16:08:24Z DBG WebSocket error="read tcp 172.23.0.2:5050->192.168.0.128:63300: use of closed network connection" type=read
screengo   | 2020-10-06T16:08:37Z DBG WebSocket Close code=1001 reason=
screengo   | 2020-10-06T16:08:38Z DBG WebSocket Close code=1000 reason="room with id test does not exist"
screengo   | 2020-10-06T16:08:38Z DBG WebSocket error="read tcp 172.23.0.2:5050->192.168.0.128:63309: use of closed network connection" type=read

Also, the demo/public instance suffers from the same issue.

[jmattheis]

SCREEGO_EXTERNAL_IP must be the external ip of the server.

Could you recheck with TURN. Normally on TURN requests something like this should be logged:

DBG TURN authenticated addr=someip:49499 realm=screego

Can you check, that 3478 (tcp/udp) is whitelisted in your firewall?

[bielej]

My server is behind NAT - I have forwarded port 3478 (TCP+UDP) to the server and that did the trick.
The documentation did not include any recommendations regarding running the server behind NAT.
Now it works like a charm, thanks for the help :)