Docker-Jitsi-Meet runs quite nicely on a Synology DS218+. However we’re behind a DynDNS-Setup which is changing our external WAN IP address every day. What is a good configuration to let Jitsi know of a changed WAN IP address?
Currently we’ve solved it as follows:
.env: DOCKER_HOST_ADDRESS=meet.domain.tld (this seems to work stable)
JVB_STUN_SERVERS= (just leaving the list empty)
JVB_TCP_HARVESTER_DISABLED=false (with port UDP/10000 open)
docker-compose down / up -d every morning (usually the IP changes at night).
We’ve studied the various notes and hints regarding STUN/TURN, but could not figure out from the documentation what’s really the current best setup recommendation for a NAS behind DynDNS. (Additionally obviously, the docker setup complicates modifications that go beyond the capabilities of the
As a side note: Like others here in the forum, we’re also seeing individual clients permanently unable to join (no clear pattern; meet.jit.si works for them). They constantly experience what everybody else experiences only when Jitsi’s WAN IP is outdated: only users on the LAN can see and hear each other; all others see all sessions, but no streaming content. We suppose this issue is related to the underlying issue here – NAT traversal — hence we mention it here.