Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
When deploying odoo behind Amazon's Elastic Load Balancers with SSL termination only... odoo redirects some requests to http. For example, logging out is always redirected to http instead of https.
I've tried everything from passing in --proxy-mode to the daemon, to hardcoding the web.base.url parameter to use https as well as setting the web.base.url.freeze parameter.
Is there anything I can do to deploy odoo behind Amazon's ELBs without having to use nginx or open it up over http?
When deploying Odoo behind a reverse proxy there are some headers that you need to pass to your Odoo instance from the reverse proxy itself. This works for me on nginx:
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forward-For $proxy_add_x_forwarded_for;
# Let the OpenERP web service know that we're using HTTPS, otherwise
# it will generate URL using http:// and not https://
proxy_set_header X-Forwarded-Proto https;
# by default, do not forward anything
proxy_redirect http:// https://;
This settings on nginx location made Odoo behave ok behind a reverse proxy, in your case the last two are very important, find what nginx is doing with those settings and replicate to Amazon ELB
can you post the complete sites-aviable/default file ?
Given the design architecture of the Odoo web app, you cannot efficiently rely on AWS ELB to handle SSL certificate nor does the Odoo uWSGi service serve you well in this regard, run it on a Nginx and save your mind.
Does anyone have a way to do it, im trying to mount odoo 15 behind a load balancer but I wont pass the login page
According to Amazon's documentation:
http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/x-forwarded-headers.html
They do send the X-Forwarded-For, and X-Forwarded-Proto headers through.
Host should be passed through with the request automatically, and I'm not sure what X-Real-IP does.
I think the part that works for you, but I can't get to work for me because AWS ELB doesn't support it is the redirect of http to https. There are only a few places that don't support the automatic changing of the URL.. such as logging out, and the mass mailing campaign email editor.
I would think that these should be updated so that they work regardless of what type of load balancer the system is behind.
Alternatively I could setup an nginx docker image to simply redirect http to https, but this seems like a workaround and not a very good use of resources.
Does anyone else have any additional thoughts?
Stuck on this as well. Did you manage to set up Nginx behind ELB?
Stwórz konto dzisiaj, aby cieszyć się ekskluzywnymi funkcjami i wchodzić w interakcje z naszą wspaniałą społecznością!
Zarejestruj się| Powiązane posty | Odpowiedzi | Widoki | Czynność | |
|---|---|---|---|---|
|
0
cze 15
|
5346 | ||
|
0
sie 22
|
2510 | ||
|
3
cze 25
|
2916 | ||
|
2
wrz 23
|
8001 | ||
|
how to make my website https?
Rozwiązane
|
|
1
lut 25
|
4464 |
1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.
