Skip to content
English
More support Sign in
Contact Us
  • There are no suggestions because the search field is empty.

User FAQ - Video Calling - Troubleshooting

Why Video Calling Sometimes Doesn’t Work

If you’re unable to connect to PushFar’s video calling, it’s usually due to company network restrictions, browser settings, or blocked permissions.

Some organisations block video calling tools unless they’ve been approved for internal use (for example, Zoom or Microsoft Teams). The same restrictions can apply to PushFar.

PushFar uses WebRTC, a widely adopted and secure video calling technology used by most webinar and video platforms. If WebRTC is blocked by your company network, browser, or a browser extension, your camera and microphone won’t work — and the call won’t connect.

 

For Users: Things You Can Try Yourself

1. Use Google Chrome (Recommended)

Chrome works best with PushFar video calling.

Make sure your browser is fully up to date.

 

2. Run a WebRTC Test

This helps confirm whether WebRTC is working in your browser at all.

  • Best option: Use an online WebRTC test page to check your camera, microphone, and connection status, such as:
    https://webcasts.com/webrtc/
  • Advanced checks (optional):
    • Chrome: chrome://webrtc-internals/
    • Firefox: about:webrtc

If the test page shows errors or fails to detect your camera or microphone, WebRTC may be blocked by your browser, network, VPN, or a browser extension.

 

3. Allow Camera & Microphone Access

Make sure PushFar is allowed to use your webcam and microphone.

  • Look for a camera icon in the browser address bar
  • Ensure permissions are set to Allow
  • Check your computer’s system privacy settings (especially on macOS and Windows)

Chrome help guide:
https://support.google.com/chrome/answer/2693767

 

4. Check Browser Extensions

Some extensions block video calling or WebRTC traffic.

Common examples:

  • Ad blockers (e.g. AdGuard, uBlock Origin)
  • Privacy extensions (e.g. Ghostery)
  • WebRTC tools (e.g. WebRTC Control, WebRTC Leak Prevent)

To test:

  1. Open Chrome
  2. Click the three dots → More tools → Extensions
  3. Temporarily disable WebRTC‑related or privacy extensions
  4. Refresh PushFar and try again

 

5. Try Incognito / Private Mode

Opening PushFar in an Incognito (Private) window disables most extensions automatically.

  • Windows/Linux: Ctrl + Shift + N
  • macOS: Cmd + Shift + N

If it works here, a browser extension is likely the cause.

 

6. Check VPN or Network Interference

  • Temporarily disable any VPN
  • Some VPNs intentionally block WebRTC to prevent IP leaks
  • Secure corporate networks may also block WebRTC traffic

 

7. Close Other Video Applications

Other apps can lock your camera or microphone. For Example Google Meet can take exclusive control of microphone and speaker permissions because browsers and operating systems allow applications to seize audio devices to ensure high-quality voice input, preventing interference from other apps. When this happens, Meet may lock the device, preventing apps PushFar, or other browser tabs from using the microphone.

To test this close tools such as:

  • Microsoft Teams
  • Zoom
  • Google Meet
  • Skype

Before joining a PushFar call.

Note: To prevent exclusive control of a microphone and speaker In Windows, go to Sound Settings > Recording > [Your Microphone] Properties > Advanced and uncheck "Allow applications to take exclusive control of this device

 

8. Check Your Camera & Hardware

  • Ensure the camera is physically connected
  • Test it in another app (Zoom or Teams)
  • Refresh the page or restart your browser
  • Restart your computer if the camera isn’t detected

 

9. Browser‑Specific Fixes

Firefox

  • Type about:config
  • Search for media.peerconnection.enabled
  • Ensure it is set to true

Chrome / Edge

  • Ensure the browser is fully updated
  • Make sure another application isn’t currently using the webcam

 

10. Clear Your Browser Cache

Clearing cached files can help resolve connection issues:

https://support.google.com/accounts/answer/32050

 

 

For IT / Network Administrators

Network Requirements for PushFar Video Calling

PushFar video calling relies on WebRTC, which requires both browser‑level and network‑level support.

Please ensure the following are allowed:

  • *.pushfar.app (and all subdomains)
  • Outbound access on ports 80 and 443
  • WebRTC enabled in the browser environment
  • UDP traffic enabled (required for audio/video streaming)
  • No inspection, blocking, or modification of WebRTC traffic

 

Common Causes of Failure in Managed Environments

  • Firewall rules blocking UDP traffic
  • Proxy servers interfering with WebRTC signalling
  • VPNs configured to block WebRTC to prevent IP leakage
  • Browser policies disabling media.peerconnection
  • Privacy or security extensions deployed via device management

 

Recommended Validation Steps

  • Test WebRTC connectivity using:
    https://webcasts.com/webrtc/
  • Confirm browser support on a clean Chrome profile
  • Test outside the corporate VPN or firewall where possible
  • Review any enterprise browser policies affecting media or WebRTC

 

Using Another Video Platform

If a different video platform is already approved internally (such as Teams or Zoom), you can still schedule the meeting in PushFar and select that platform instead.

This allows users to keep:

  • Meeting notes
  • Session details
  • Mentoring history

In one place, while hosting the call elsewhere.