when accessing our Jitsi instance from the local network, the DNS resolves the URL to the LAN IP address instead of the public IP address, which leads to issues for participants in LAN. Setting DOCKER_HOST_ADDRESS to the LAN address seems to enable communication between LAN participants but excludes public participants.
Is there a way to make Jitsi available both from LAN and public IP?
A few hours and dozens of forum/github-posts later I still didn’t find a solution. It seems jvb is using the docker container IP for org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS instead of the LAN IP.
Setting it directly to the docker host IP along with org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS doesn’t work.
My problem is best described in the links below. The guys found some workarounds but there must be a better way than hairpin NAT or network_mode: host for the jvb container.
On client side the logs show:
2021-04-13T13:15:51.069Z [JitsiMeetJS.js] <getGlobalOnErrorHandler>: UnhandledError: RTCPeerConnection is gone (did you enter Offline mode?) Script: null Line: null Column: null StackTrace: J/e.RTCPeerConnection.prototype.getStats@https://*DOMAIN*/libs/lib-jitsi-meet.min.js?v=4628:25:52388
2021-04-13T13:15:51.070Z [modules/statistics/RTPStatsCollector.js] <m.prototype.errorCallback>: Get stats error DOMException: RTCPeerConnection is gone (did you enter Offline mode?) Logger.js:154:22
2021-04-13T13:15:57.012Z [modules/xmpp/JingleSessionPC.js] <doInitialize/this.peerconnection.oniceconnectionstatechange>: (TIME) ICE failed P2P? false: 46135 Logger.js:154:22
WebRTC: ICE failed, add a STUN server and see about:webrtc for more details