Docker + TURN not working about server HOT 6 CLOSED

Yeah, I've thought of this too. I'll probably give the issue a shot, and implement the address generator for port ranges.

from server.

I just tested the changes in the new release. Gave the turn server 1000 ports and it works great! Thank you 👍

(Not using docker, but needed this setting to open the correct ports in my firewall)

from server.

Ahh, I think the turn server allocates random ports relay connections. For now network_mode: host should be enough. I've adjusted the docker examples in https://screego.net/#/install?id=docker

from server.

Ah thanks, makes sense.

The amount of ports needed also seems to be a problem for other TURN servers in docker: https://hub.docker.com/r/instrumentisto/coturn

In this case, they added options min-port and max-port to mitigate the problem. Would this also be possible here?

I'm not sure if pion/turn supports this, though. There is a GitHub issue saying it's possible, but I'm not sure the solution is actually feasible: pion/turn#129

from server.

I've spent quite some time testing v1.1.1 in a Docker environment according to the "Port Range" section of the installation guide. I think with the current version it's (nearly?) impossible to get Screego to work outside of a local network with port mappings such as:

    ports:
      - 5050:5050
      - 3478:3478
      - 50000-50100:50000-50100/udp

Locally it work's fine, but behind a NAT both STUN as well as TURN fail and the stream remains black.
The only solution I found to get it working with Docker was to use the network_mode: host syntax.
(Other potential solutions approaches might involve additional firewall rules or explicitly specifying every in ports: with the - mode: host syntax since docker-compose does not support ranges here, but I didn't check these.)

I'm not really sure why the issue was closed but at least for me it's not working.

Further, I've tested Screego with STUN in various scenarios, all except one worked well. However, app.screego.net didn't work at all as soon as at least one NAT was in-between the connection path. If the demo instance is hosted using via Docker this might be caused by the same issue.

from server.

@ThelloD, please create a new issue for your problem.

from server.