Skip to Content
Menu
Musisz się zarejestrować, aby móc wchodzić w interakcje z tą społecznością.
To pytanie dostało ostrzeżenie
1 Odpowiedz
7711 Widoki

Dears, 


Despite defining a system parameter with : 

 key : web.base.url 

And freezing it with another system parameter with : 

Key : web.base.url.freeze
Value : True

The following scenario happen with me :

I'm logged on with my account, I disconnect, and try to log on with another account, when pressing the connect button, I get the http://backend-odoo/web?

I can't explain this behavior. Is there any method that forces the backend-odoo URL ?

Note that I'm using nginx as reverse proxy, and I'm enabling proxy_mode on the odoo config file.
Awatar
Odrzuć
Najlepsza odpowiedź

Hi Teimi, 


i was getting same proble, you have to replace http://backend-odoo with your real domain in nginx configuration file:

upstream www.mywebsite.com {

        server 127.0.0.1:8069;

}


server {

        keepalive_timeout  120;

        client_max_body_size 25M;

        location / {

                proxy_pass http://www.mywebsite.com;

        }

}

Awatar
Odrzuć
Autor

Hi Mirco, On sites-availables I changed the proxy_pass parameter into my real domain name, I restarted nginx but now I'm getting bad gatway from nginx ... is there somthing I'm missing ?

Hi TEIMI, you have to do this in sites-enabled. Check my answer, i edited with my nginx config file.

Autor

I forgot to change backend-odoo on the upstream parameter also, works fine now. Thanks !

Powiązane posty Odpowiedzi Widoki Czynność
1
maj 25
736
0
lis 24
1387
0
mar 24
1384
1
gru 23
7142
1
lut 22
8433