Purpose

To explain why the VirtualCallboard mobile app may fail to load or log in when connected to public Wi-Fi, even though it works normally on mobile data or other private networks.

Overview

Some users report that the VirtualCallboard app:

• Works on cellular/mobile data

• Works on trusted Wi-Fi (home, school, workplace)

• Does NOT load, refresh, or log in on specific public Wi-Fi networks

Examples of public Wi-Fi: coffee shops, hotels, airports, conference centers, theatres, libraries, dorm common areas, etc.

If multiple people on the same public network experience the issue, the Wi-Fi itself is usually the cause.

Why the App Fails on Public Wi-Fi

Although the browser version may sometimes work, public Wi-Fi systems often block the app’s secure communication requirements.

Common causes include:

1. Public Wi-Fi Firewalls Block App Traffic

The VirtualCallboard app uses secure, real-time connections — including:

• HTTPS (port 443)

• Secure websockets (WSS)

• Encrypted API calls

Many public Wi-Fi systems block or throttle websocket traffic, which can stop the app from loading or logging in.

2. Captive Portals Are Not Completed

Public Wi-Fi normally requires you to:

• Accept Terms of Use

• Click a “Continue/Connect” button

If the captive-portal page is not completed, apps cannot reach the internet, even if the Wi-Fi icon shows “connected.”

3. Limited or Overloaded Public Wi-Fi

Public networks often:

• Restrict app-level traffic

• Drop encrypted connections

• Have unstable or slow bandwidth

The app requires a steady, secure connection and may fail easily on overloaded networks.

4. Public Wi-Fi Security Flags Encrypted App Traffic

Hotels, airports, and large venues sometimes use automated threat filters that block:

• High-frequency secure requests

• Unknown encrypted app traffic

This can stop the VirtualCallboard app from loading completely.

Troubleshooting Steps

1. Confirm You Completed the Captive Portal

Open a browser and visit:

• neverssl.com

• example.com

If a Terms/Agreement page appears, accept it, then reopen the app.

2. Toggle Wi-Fi Off and Use Mobile Data

If the app loads on mobile data:

→ The public Wi-Fi is blocking the app’s traffic.

3. Completely Close and Reopen the App

On iOS: swipe up to force quit
On Android: open app switcher and swipe away

Reconnect to Wi-Fi and relaunch the app.

4. Forget the Public Network and Reconnect

This forces the captive portal or security handshake to restart.

5. If Possible, Try Another Public Wi-Fi Network

If VCB works elsewhere, the issue is specific to that public network’s security settings.

6. If This Is a Theatre, Campus, or Event Facility

Share this information with the network administrator:

The VirtualCallboard app requires access to secure websocket traffic (WSS) over port 443 and standard HTTPS API traffic. Some public Wi-Fi systems block or throttle websocket connections, preventing the app from loading. Allowing secure app traffic resolves the issue.

If the Issue Continues

Please contact support with:

• Your device type (iOS or Android)

• Whether the issue happens on all public Wi-Fi or just one location

• Whether the mobile app works on other networks

• Date/time of the attempted app login

• Screenshots if available

This information helps us identify patterns across reports.

Related Articles

• VirtualCallboard App: Troubleshooting Login Issues