Connection Issues
DrillerDB requires a stable internet connection for real-time features, data synchronization, and cloud-based storage. This guide helps resolve common connectivity problems.
Quick Start: Fix Connection Issues
- Test your internet by visiting another website
- Restart your router for network problems
- Disable VPN temporarily to test
- Clear browser cache and refresh
- Try a different network (WiFi vs cellular)
The live connection (a WebSocket) uses port 443. The classic app and the Route Planner on the console map use it. The console notification bell does not: it checks for new notifications about every 30 seconds over the same connection that loads the page. If you're on a corporate network, ask your IT department to whitelist DrillerDB domains.
Connection Problems Quick Reference
| Symptom | Likely Cause | Solution |
|---|---|---|
| No connection | Internet down | Check router/modem |
| Intermittent | Weak WiFi signal | Move closer to router |
| Blocked | Firewall/VPN | Whitelist DrillerDB |
| Slow sync | Network congestion | Try off-peak hours |
| Mobile issues | Weak signal | Find better coverage |
Step-by-Step Workflow
- Test your internet by visiting another website
- Restart your router for network problems
- Disable VPN temporarily to test
- Clear browser cache and refresh
- Try a different network (WiFi vs cellular)
Network Connectivity Problems
Diagnosing and resolving basic connection issues:
No Internet Connection - If DrillerDB displays a connection error, first verify your device has internet access by visiting other websites. Check that your WiFi or cellular data is enabled and connected. If using WiFi, try disconnecting and reconnecting to refresh the connection. Consider restarting your router if other devices also have connectivity problems.
Intermittent Connection - If your connection drops frequently, you may be at the edge of WiFi range or experiencing cellular network congestion. Move closer to your WiFi router or switch to a location with better cellular signal. Disable power-saving features that may turn off WiFi or data connections during inactivity.
Firewall or Network Restrictions - If you're on a corporate or public network, firewall rules may block DrillerDB connections. WebSocket connections require port 443 to be open for secure communications. Contact your network administrator to ensure DrillerDB domains and ports are whitelisted.
VPN Interference - Some VPN configurations can interfere with WebSocket connections or slow response times. Try temporarily disabling your VPN to see if performance improves. If a VPN is required, contact support for recommended VPN settings that work best with DrillerDB.
Real-Time Feature Issues
Problems with live notifications and updates:
Notifications Not Arriving - In the console, the bell in the top bar asks for new notifications about every 30 seconds while the browser tab is visible. A tab in the background catches up when you switch back to it. Wait up to 30 seconds, then reload the page. Check that you have an active internet connection and are signed in to the correct company. If problems persist, clear your browser cache and reload DrillerDB completely. See Real-Time Features for what updates by itself.
Schedule Updates Not Syncing - The console Scheduling views do not update by themselves. Reload the page to see changes other people made. In the classic app, schedule changes arrive over the live connection, so check that your internet connection is stable and that both users are in the same company.
Chat Messages Delayed - If chat messages aren't updating quickly, check your internet connection and refresh the chat view. Some chat screens update on short polling intervals, so a manual refresh is the safest recovery step when message state looks stale.
Connection Monitoring - When the classic app's live connection drops, it tries to reconnect on its own. The wait between tries doubles each time, from 1 second up to 30 seconds, for 10 tries. After that it keeps trying once a minute until the connection comes back, so a long outage does not need a manual reload. The console map's Route Planner has no automatic reconnect: reload the page after a long outage. If problems persist, check your network configuration and make sure WebSocket traffic (port 443) is not blocked.
Synchronization Problems
Issues with data syncing between devices and sessions:
Data Out of Sync - If you're seeing different data on different devices, ensure all devices have active internet connections. Force a sync by refreshing the page or logging out and back in.
Changes Not Uploading - If a save or submission does not appear on other devices, confirm the action completed successfully, then refresh. Retry the action after connectivity is stable.
Sync Conflicts - If someone else saves a project or a Pump/Service job after you opened it, DrillerDB refuses your save and shows a notice. On a project it reads "Another user edited this project." On a Pump/Service job it reads "Another user edited this work order. Your last change was not saved." Both notices have three choices: Reload latest loads the saved version, Override saves your entries over it, and Dismiss closes the notice. Read what changed before you choose Override. Tell your team who is editing a shared record to avoid the conflict.
File Upload Synchronization - Large file uploads may fail on slow or unstable connections. If uploads fail repeatedly, try a wired ethernet connection instead of WiFi, or upload files during times of better connectivity. Consider compressing large files before uploading.
Browser-Specific Issues
Connection problems related to specific browsers:
Cookie and Storage Blocking - Some browsers block third-party cookies or local storage by default, which can interfere with authentication and real-time features. Add DrillerDB to your browser's allowed list for cookies and storage.
Extension Interference - Browser extensions like ad blockers, privacy tools, or security software can block WebSocket connections. Try disabling extensions one at a time to identify conflicts. Add DrillerDB to extension whitelists when possible.
Browser Cache Issues - Outdated cached resources can cause connection problems. Perform a hard refresh with Ctrl+F5 (Windows) or Cmd+Shift+R (Mac). If problems persist, clear your browser cache completely from browser settings.
Incognito or Private Mode - Private browsing modes restrict some features required for DrillerDB operation. For best results, use a standard browser window. If you must use private mode, ensure all cookie and storage exceptions are configured correctly.
Mobile Connection Issues
Connectivity problems specific to mobile devices:
Cellular Data Limitations - Some cellular plans restrict data usage or throttle connections after reaching data caps. Check your data usage and plan limits. Use WiFi when possible for better performance and to conserve cellular data.
Background Data Restrictions - Mobile devices may restrict background data to save battery or data usage. Ensure DrillerDB is allowed to use data in the background for notifications and real-time updates.
Signal Strength - Weak cellular signal causes slow performance and dropped connections. Move to a location with better signal strength, or wait until you're in a better coverage area for important operations.
If you work in areas with poor connectivity, do not assume offline edits will sync automatically. Recheck each critical update after reconnecting.
Related Topics
- Common Issues - General troubleshooting
- Contact Support - Get help
- Real-Time Features - WebSocket requirements
- Mobile Access - Mobile connectivity