-
Notifications
You must be signed in to change notification settings - Fork 23.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] [master] DIscuss totally not worked #107587
Comments
We have the same issue after clean installation of odoo 16 on docker what kind of configuration are we missing ? |
I have done some research on this issue, still not get the root cause, but got some progress: bus.websocket_worker_assets is loaded in bus_service.js with SharedWorker but not run. Why not run, perhaps:
Need more investigation. |
Update: bus.websocket_worker_assets is loaded in bus_service.js run successfully. Inspect Chrome and check worker. But can not connect ws://localhost:8069/websocket because the websocket controller return 101 SWITCHING PROTOCOLS can not be understood by Chrome/Browser. (Even Nginx proxy) |
anything new about this issue |
So far I dont think Odoo support is recognizing this as an issue, I have raised a ticket with them so far with a reply only "we are looking into the issue" |
Locally works quite good, without nginx / proxy. |
@Feyensv @JacooRe @dingguijin We're currently facing the same issue. Is there anything we could look into? We're using nginx and Werkzeug 2.0.2, as suggested. |
Update: we managed to get it working after updating the nginx.conf to the recent state according to https://www.odoo.com/documentation/16.0/administration/install/deploy.html#https and exchanging longpolling_port by gevent_port in the odoo.conf |
Impacted versions:
[master]
Steps to reproduce:
Run Odoo behind nginx. (if not run nginx the discuss still not work)
Register a new user and use admin create direct channel chat with the new user.
Current behavior:
Can not see each other in real time and even the offline messages.
Expected behavior:
Video/Screenshot link (optional):
Support ticket number submitted via odoo.com/help (optional):
After Odoo 16, Odoo looks like not good as before. The bad thing may start from OWL compatible and legacy code. It is not clean any more. (I mean JS code).
The text was updated successfully, but these errors were encountered: