Guardian Services
Operational risk explained
Realtime Failures
Odoo Discuss and realtime features rely on a connection path that crosses the browser, HTTPS proxy, WebSocket route, gevent worker and ICE infrastructure.
Warning signs
What customers may notice
- Calls remain in connecting state
- One participant cannot hear or see another
- WebSocket requests return errors
- Calls work on one network but fail on another
Business impact
Why the risk matters
- Meetings become unreliable
- Users abandon Odoo collaboration features
- Remote teams lose time troubleshooting
- Customer-facing sessions feel unprofessional
Common causes
Where the failure can begin
- WebSocket traffic routed to the wrong Odoo port
- Inactive gevent listener
- Missing proxy headers
- Browser permission failures
- Insufficient STUN or TURN coverage
DPIO approach
What we verify
- Odoo worker and gevent configuration
- Listening realtime port
- Nginx WebSocket routing
- Public handshake behavior
- Browser permission state
- ICE credential and relay path
Related service
Discuss Reliability Sprint
Open the complete scope, deliverables, boundaries, process and frequently asked questions.
Explore This Service