meetergo Connect: network requirements (for IT departments)

If video calls with meetergo Connect fail on your company network but work on a phone or home network, your firewall or web proxy is most likely blocking part of the connection. This page lists exactly what to allow. Send it to your IT department as-is.

What to allow

Required — with these two rules, calls work:

Destination	Protocol / port	Purpose
`connect.erg.ooo`	TCP 443 (WSS)	Call signalling (WebSocket)
`connect-turn.meetergo.com`	TCP 443 (TURN over TLS)	Media relay fallback

Recommended for best quality — lets media flow directly instead of over the TLS relay:

Destination	Protocol / port	Purpose
`connect-turn.meetergo.com`	UDP 3478	Direct video/audio media
`connect-turn.meetergo.com`	TCP 7881	Media fallback when UDP is blocked

The app itself runs on my.meetergo.com and api.meetergo.com (ordinary HTTPS, TCP 443).

Direct media (UDP 3478 / TCP 7881) is sent to the IP address connect-turn.meetergo.com resolves to, not to the hostname. If your firewall supports FQDN rules, use the hostname. Otherwise allow the resolved IP — and prefer re-resolving over hardcoding, since the address can change during maintenance.

The two required port-443 entries are not ordinary HTTPS. The signalling connection is a WebSocket, and the relay connection is TURN over TLS. TLS-inspecting proxies must exempt connect.erg.ooo and connect-turn.meetergo.com from interception — an intercepting proxy that re-writes these connections breaks calls even though port 443 is open.

How the fallbacks work

meetergo Connect tries the best path first and falls back automatically:

UDP 3478 direct to the media server. This is the standard real-time media port (the same one Microsoft Teams uses). Allowing it gives the best call quality.
TCP 7881 if UDP is blocked.
TURN over TLS on port 443 as the last resort. Calls work on networks that only allow outbound HTTPS, but quality can be lower, since TCP is not ideal for real-time media.

If none of these paths work, participants cannot join with video at all. That typically means a proxy is intercepting TLS (see above) or a VPN client is dropping the media packets.

Quick self-test

Open your meeting link on the affected network. The join screen runs a connection test in the background and warns you if your network blocks video calls. As a cross-check, join once over a mobile hotspot: if that works and the company network does not, the firewall or proxy is the cause.