Technical Details on LobbyCentral Push Notifications & Browser Refresh Issues

Below is a technical overview of how LobbyCentral’s push notification service operates. This should assist IT in identifying why a subset of users may experience issues with the queue list not refreshing, when check‑in or check‑out events occur.

How LobbyCentral Push Notifications Work
When a user logs into LobbyCentral, the browser establishes a persistent listener connection via JavaScript to:
Once connected, the browser subscribes to a specific channel. The channel name is displayed on the main page under the In‑Servicelist as:
Connected to /(channel name)
LobbyCentral uses the Comet method to maintain this connection. With Comet:
  • The connection remains open until it times out.
  • When a timeout occurs, the browser automatically re-establishes the connection.
  • When a customer is checked in or checked out, a message is pushed to the subscribed channel.
  • All clients listening on that channel receive the message and refresh their Waiting and In‑Service lists.
Known Causes of Refresh Failures
1. Group Policy Restrictions: If https://websync.lobbycentral.com is blocked, the browser cannot maintain the listener connection.
  • Ensure*.lobbycentral.comis trusted and allowed through network policy.
2. Security Software Blocking Persistent Connections: Because Comet keeps an open connection, some security tools may flag this behavior as suspicious and terminate it.
3. Sleeping / Suspended Browser Tabs: If a tab goes into a “sleeping” or “suspended” state, it disconnects from the push notification service and does not reconnect.
  • Add an exception forapp.lobbycentral.comto prevent sleeping.
Important Note
Refresh issues are typically all‑or‑nothing—either all users refresh correctly or none do. When only a subset of users is affected, it almost always indicates alocal configuration issue, such as:
  • Group policy differences
  • Browser restrictions
  • Security software behavior
  • Network filtering applied inconsistently across user machines
LobbyCentral Chat (Messenger)
LobbyCentral messenger also uses the same push notification server but uses a different URL:  
LobbyCentral Push Notification Troubleshooting Checklist
1. Verify Network Access
  • Confirm that https://websync.lobbycentral.com is reachable from affected machines.
    • Test via browser and command-line tools (curl, ping won’t work because it’s HTTPS, but curl will).
  • Ensure*.lobbycentral.comis allowed through:
    • Firewall
    • Web filters
    • SSL inspection tools
    • Proxy servers
  • Check whether affected users are on a different VLAN, subnet, or Wi-Fi network than unaffected users.
2. Check Group Policy & Browser Restrictions
  • Review GPOs applied to affected users:
    • Are there policies blocking long‑lived connections or specific domains?
    • Are there restrictions on background JavaScript execution?
    • Are there policies forcing aggressive tab suspension or memory-saving modes?
  • Compare GPOs between users who can refresh and users who cannot.
3. Inspect Security Software Behavior
  • Determine whether endpoint security tools (CrowdStrike, Carbon Black, Defender ATP, etc.) are:
    • Blocking persistent Comet connections
    • Flagging LobbyCentral’s listener as suspicious
    • Terminating idle or long-running browser processes
  • Check logs for blocked or quarantined network events related to LobbyCentral.
4. Browser Configuration & Extensions
  • Confirm users are running a supported browser (Chrome, Edge, Firefox).
  • Check for extensions that may interfere with real-time connections:
    • Script blockers
    • Privacy filters
    • Ad blockers
    • Enterprise security extensions
  • Ensure the browser is not set to:
    • Auto-sleep inactive tabs
    • Restrict background activity
    • Disable third-party scripts
5. Test Channel Subscription
  • Have affected users log in and verify the channel indicator shows: Connected to /(channel name)
  • If the channel does not appear:
    • The listener connection is not being established.
    • This points to network or browser blocking.
6. Compare Behavior Across Browsers
  • Test LobbyCentral in:
    • Chrome
    • Edge
    • Firefox
  • If one browser works and another doesn’t, the issue is local configuration or extensions.
7. Check for Sleeping / Suspended Tabs
  • Ensure app.lobbycentral.com is added to the browser’s “never sleep” or “always active” list.
  • Confirm OS-level power-saving features aren’t suspending browser processes.
8. Validate Reconnection Behavior
  • After a timeout, the listener should automatically reconnect.
  • If affected users never reconnect:
    • A policy or security tool is blocking the reconnection attempt.
9. Review Network Logs
  • Look for:
    • Dropped connections to websync.lobbycentral.com
    • SSL inspection failures
    • Proxy authentication interruptions
    • Timeouts or resets on long-lived connections
10. Identify Patterns Among Affected Users
Check whether the non-refreshing users share any common traits:
  • Same department
  • Same device model
  • Same browser version
  • Same GPO
  • Same security profile
  • Same network segment

Subset failures almost always indicate a configuration difference.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us