Closed hugho-ad closed 7 years ago
FYI @moylop260, the issue persists
Regards!
I think It is a missing configuration for nginx:
Because using the host:port
directly works well, but using subomain.host
is not working.
@ruiztulio this issue is reproduced from testing instances too. Could you (something your team) to fix it for production, testing and runbot, please?
@hugho-ad Could you upload image where testing is working using port but failing using subdomain?
@moylop260 we install this configuration by default in the servers (look here) but the runbot is different because we have a global rule to redirect all traffic to the runbot nginx:
Then that nginx is supposed to redirect the LP traffic to the appropiate port, so as far as I can see the configuration seems to be done, but we are still missing something.
@hugho-ad can you tell me which test instance is not working properly?
@ruiztulio for example in https://v10.abastotal.com and http://test.imeqmo.com/ and runbot build like http://39472-10-0-cb4dff.runbot.vauxoo.com/shop or http://39422-10-0-0419ee.runbot.vauxoo.com/shop
@moylop260 you rigth, when I acces to the build by the url host:port
, live chat is displayed
@hugho-ad test.imeqmo.com had 0 workers:
Changed to 3:
Restart the instance and the chat is working:
Abastotal 10.0:
I didn't change it because I have to restart the instance, but it should work after that.
Most of the issue we had with the chat are because of this. I have to check the runbot ones
Very Thanks @ruiztulio
Regards!
Or wait... we can't use the extra port because we are using it for ssh connection feature. It can't fix it for runbot
Live chat is not displayed because the im_status is not updated https://github.com/Vauxoo/odoo/blob/10.0/addons/bus/models/res_users.py#L12-L29
Talking wit @moylop260 , this bug is related with the requirements installed in docker containers