Skip to Content
Menu
This question has been flagged

I'm on Odoo v16 community via docker deployment with nginx reverse proxy. 


I have 2 issues. 

1. First is that I can't get my websocket working and suspect this is the reason my livechat via Discussions isn't working. the port 8069 is the only port listening in my docker even though I exposed ports 8071 and 8072 for longpolling and websocket respectively. I have configured forwarding in nginx for both cases on these ports but that doesn't make much difference if I have no listeners in my docker instance. 

  • proxy_mode = True
  • xmlrpc_port = 8069
  • xmlrpcs_port = 8071
  • longpolling_port 8072
  • Workers = 3
  • xmlrpcs_interface =   
  • workers =3
  • max_cront_threads = 2

Nginx: 

                location /websocket {

                        #ssi off;

                        proxy_redirect off;

                        proxy_pass http://odoo-rpcs ;

                        proxy_set_header Upgrade $http_upgrade;

                        proxy_set_header Connection $connection_upgrade;

                        proxy_set_header X-Forwarded-Host $host;

                        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

                        proxy_set_header X-Forwarded-Proto $scheme;

                        proxy_set_header X-Real-IP $remote_addr;

                 }


               location /longpolling {

                       proxy_connect_timeout   3600;

                       proxy_read_timeout      3600;

                       proxy_send_timeout      3600;

                       send_timeout            3600;

                       proxy_pass http://odoo-chat;

                 }


Docker run command: 

docker run -v /odoo/data:/var/lib/odoo -d -p 127.0.0.1:8069:8069 -p 8069:8069 -p 8072:8072 -e PASSWORD=odoo -e HOST=odoodb --name odootest --restart unless-stopped --network odoo -t odoo16


Error Log: 


INFO werkzeug: 10.89.1.1 - - [02/Feb/2024 01:04:35] "GET /websocket HTTP/1.0" 400 - 2 

ERROR odoodb odoo.addons.bus.websocket: 400 Bad Request: Empty or missing header(s): upgrade



Problem 2.

   is tagged on all my site pages preventing bot SEO scans. 


tag in html is preventing Google Search Console scanning. Robots.txt and Sitemap.xml are working and are reachable.  Although the robots.txt update is NOT working via the Website-->Config-->Edit robots.txt.   I have to manually update from Dev view --> technical --> Views --> Robots.txt



Robots:

User-agent: *
Allow: /
Allow: *

User-agent: Googlebot-news
Allow: /

User-agent: Googlebot
Allow: /


I've searched and have tried various addons but nothing working to remove this! 





Avatar
Discard
Author Best Answer

Go to Homepage:  Site--> HTML/CSS --> dropdown MainLayout with XML(HTML)


Search in website.layout   for robots

Edit the Robots URL Checks or remove line entirely.....

       
"""   

 ##   ///    meta t-if(main_object and 'website_indexed' in main_object and not main_object.website_indexed) or (website.domain and not website._is_indexable_url(request.httprequest.url_root))" name="robots" content="noindex" ////

"""



       




Avatar
Discard
Best Answer

Thanks Drew !

Avatar
Discard
Best Answer

Thanks Drew, I just changed mine form noindex, to index. Google likes it now. It took me longer to find than fix.

Avatar
Discard
Related Posts Replies Views Activity
1
Dec 24
2565
1
Apr 23
3078
1
Apr 24
2774
0
Jul 24
747
1
Feb 25
458