Skip to content
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

Open
dingguijin opened this issue Dec 9, 2022 · 8 comments
Open

[BUG] [master] DIscuss totally not worked #107587

dingguijin opened this issue Dec 9, 2022 · 8 comments
Labels
16.0 Discuss Discuss, mail, chatter, livechat, attachments

Comments

@dingguijin
Copy link

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).

@Feyensv Feyensv added Discuss Discuss, mail, chatter, livechat, attachments 16.0 labels Dec 12, 2022
@JacooRe
Copy link

JacooRe commented Dec 14, 2022

We have the same issue after clean installation of odoo 16 on docker
the pressence bubbles (online/away/offline) doesnt work - always show offline
messages will appear in chat box after 5minutes, you can refresh page to make them show faster
video chat doesnt work at all, you cant see or hear each other

what kind of configuration are we missing ?
we use Traefik proxy

@dingguijin
Copy link
Author

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:

  1. secruriy restrict?
  2. boot.js is not correct?
  3. SharedWorker not loaded complete?

Need more investigation.

@dingguijin
Copy link
Author

dingguijin commented Dec 28, 2022

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)

@bosaeed
Copy link
Contributor

bosaeed commented Jan 2, 2023

anything new about this issue

@JacooRe
Copy link

JacooRe commented Jan 5, 2023

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"
@dingguijin
did you find anything further ?
tho we use traefik as proxy, not nginx

@piemar1
Copy link
Contributor

piemar1 commented May 29, 2023

Locally works quite good, without nginx / proxy.
May by connected to installation of Werkzeug==0.16.1

@mschulz-asphericon
Copy link

@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.

@mschulz-asphericon
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
16.0 Discuss Discuss, mail, chatter, livechat, attachments
Projects
None yet
Development

No branches or pull requests

6 participants