Skip to main content

Troubleshoot Your Connection to a Virtual Poster Session

Fourwaves Virtual Poster Sessions use Daily to provide live audio and video.

If you see a warning that your network connection may be unstable, or you're having trouble joining a session, using your camera or microphone, or experiencing poor audio or video quality, try the steps below.

Things to try first

Most connection issues can be resolved with a few simple steps.

1. Check your internet connection

Make sure you have a stable internet connection. If you're using Wi-Fi, try moving closer to your router. If possible, you can also try using a wired connection.

2. Try a different network

Some workplace, university, hospital, or institutional networks have security restrictions that can interfere with video calls.

If possible, try connecting from another Wi-Fi network or using a mobile hotspot.

3. Turn off your VPN

If you're connected to a VPN, temporarily disconnect from it and try joining the session again.

4. Try a different browser

Try using an up-to-date version of Chrome, Edge, Firefox, or Safari.

If you're already using one of these browsers, closing and reopening it may also help.

5. Check your camera and microphone permissions

Make sure your browser has permission to access your camera and microphone.

If you previously blocked access, you may need to change your browser permissions before joining the session again.

6. Close other applications using your internet connection

Video calls, streaming services, large downloads, cloud backups, or other applications using a significant amount of bandwidth can affect your connection quality.

Try closing anything you don't need during the session.

Still having trouble?

If you're connecting from a network managed by your workplace, university, hospital, or another organization, its security settings may be preventing Fourwaves from establishing a reliable video connection.

Try connecting from another network, such as your home Wi-Fi or a mobile hotspot.

If the session works on another network, your organization's firewall or network configuration may be causing the issue.

In this case, contact your IT team and share the technical information below with them.

Technical information for IT teams

Fourwaves Virtual Poster Sessions use Daily, a WebRTC-based audio and video platform.

Organizations using restrictive firewalls, proxies, VPNs, or network security tools may need to allow Daily's signaling and media traffic.

Domains to allow

If your organization filters network traffic by domain, please allow access to:

  • *.daily.co

  • *.dailywebrtc.com

  • *.dailywebrtc.net

  • *.wss.daily.co

  • b.daily.co

  • c.daily.co

  • gs.daily.co

  • prod-ks.pluot.blue

Daily may also use third-party STUN and TURN services to establish or relay audio and video connections. Depending on your network configuration, please also allow:

  • stun.cloudflare.com

  • turn.cloudflare.com

  • global.stun.twilio.com

  • *.turn.twilio.com

  • *.stun.twilio.com

  • *.twilio.com

  • *.xirsys.com

The dailywebrtc.com and dailywebrtc.net domains are used as fallback domains if daily.co cannot be reached.

Ports and protocols

For the best audio and video experience, the network should allow:

  • TCP 443 for HTTPS and secure WebSocket connections

  • UDP 40000–65534 for direct real-time audio and video

  • UDP/TCP 3478 for STUN and TURN connectivity

  • TCP 5349 for TURN over TLS when required

  • TCP 443 for TURN over TLS when required

Direct UDP connections generally provide the best call quality and lowest latency.

When direct UDP connections are unavailable, Daily may use STUN/TURN services or TCP/TLS as a fallback. More restrictive network configurations can result in increased latency, reduced audio or video quality, or difficulty joining a session.

Firewalls, proxies, VPNs, and network security tools

Firewalls, VPNs, proxies, and other network security tools can interfere with WebRTC connections.

In particular, security tools that inspect, decrypt, and re-encrypt WebRTC or HTTPS traffic may interfere with audio and video connections.

If participants can connect successfully from another network but not from your organization's network, review your firewall, proxy, VPN, SSL inspection, and traffic inspection policies.

Quick checklist for IT teams

Please confirm that:

  • HTTPS and secure WebSocket traffic over TCP 443 is allowed

  • Direct media traffic over UDP 40000–65534 is allowed when possible

  • UDP/TCP 3478 is available for STUN/TURN connectivity

  • TURN over TCP 443 and 5349 is permitted when required

  • The Daily and fallback domains listed above are not blocked

  • VPN, proxy, firewall, SSL inspection, or other traffic inspection policies are not interfering with WebRTC traffic

Allowing direct UDP media traffic provides the best experience. More restrictive networks may rely on fallback connections, which can result in increased latency or reduced audio and video quality.

Did this answer your question?