Closed ValentinVinagre closed 5 years ago
That's a problem in the module code, not in doodba. It's probably not respecting the right proxy protocol parameters.
You can see in the logs the real IP, and that's thanks to that we fixed https://github.com/Tecnativa/doodba/issues/19 long ago in Doodba, but Odoo has a problem with proxies and it must be fixed there, sorry. :man_shrugging:
Is it maybe this problem: https://github.com/odoo/odoo/pull/36212 ?
Hmm it seems so.
I wouldn't think so, the fix is only to forward the host and proto (scheme), the remote address (x-forwarded-for) should always have been forwarded / converted when enabling proxy mode.
Thanks for the clarification!
Looking at #19 maybe werkzeug 0.15 regressed again on logging REMOTE_ADDR?
edit: though odoo/odoo#32914 seems to say that it does work for the regular workers and not for gevent.
I haven't tested werkezeug 0.15 yet, but let me do a quick test and I'll tell you.
Tested in an odoo 11 instance, with werkzeug 0.15.5.
I see this question in stackoverflow:
I don't know if changing the 'REMOTE_ADDR' parameter by 'HTTP_X_REAL_IP' in odoo base will fix the issue...
I followed this conversation but I didn't understand how to solve the problem.
Thanks.
No, that can't be the fix because not always you have a proxy before odoo.
True...
Hi, I have one question. In the option "Settings/technical/tracking email", the "User IP" is always the same, this is an example, but in all models/fields where we need the external IP, the value is the same(the internal IP of docker). Other example is filter the connection user by one ip, i can't do this because the external IP is always changing to the internal IP(docker).
How can I change the *.yml file so that it does not transform external IPs into internal?
Thanks.