Siirry sisältöön
Menu
Sinun on rekisteröidyttävä, jotta voit olla vuorovaikutuksessa yhteisön kanssa.
Tämä kysymys on merkitty
2 Vastaukset
612 Näkymät

When opening Editor, the page doesn't load (or you could call it loading forever), and this error is given in browser console:

  • Mixed Content: The page at [redacted] was loaded over HTTPS, but requested an insecure frame [redacted] This request has been blocked; the content must be served over HTTPS.

I see some other threads on this issue but everyone was using AWS ALB.

Have a workaround in place for now - staff needing to edit website can do so via the public IP address, bypassing SSL. But this is not a permanent solution.

Is the way to solve this to set X-Forwarded-Proto in my load balancer? There doesn't seem to be a feature for that. I have tried to use an LLM to troubleshoot this but it starts going in circles with the same suggestions:

  • Set web.base.url and web.base.url.freeze, done this
  • Set the website's domain address in Website -> Settings, done this
  • add ?debug=asset parameter to the URL, done this
  • at one point, suggest I delete the filestore folder to empty cache, which seemed like a really bad idea, so I did not do that, lol


Avatar
Hylkää
Paras vastaus

Did you find any permanent fix for this?

Avatar
Hylkää
Tekijä

Yes, I switched from AWS Application Load Balancer to Nginx for SSL termination. In my case, nginx is running on the same server as the Odoo server, because we do not expect to need multiple servers yet.

so your use-case is different, i need multiple servers in load balancer.

Tekijä

You can still switch to nginx as SSL termination and likely solve this problem. From nginx docs:

> NGINX Open Source supports four load balancing methods: Round Robin, Least Connections, IP Hash, and Generic Hash

Tekijä

* nginx as SSL termination /and load balancer/

And how to manage the user sessions in case of multiple servers with nginx load balancing?

Tekijä

That goes outside my area of expertise but I have heard of ways of doing this. At a glance, it looks like you could achieve this with open source nginx by using IP hashing, and the paid tier of nginx offers more sophisticated sticky session support.

Tekijä Paras vastaus

I solved this problem by switching to Nginx for SSL termination. It didn't take long and immediately cleared up the issue.

Avatar
Hylkää
Aiheeseen liittyviä artikkeleita Vastaukset Näkymät Toimenpide
2
syysk. 25
4028
1
heinäk. 25
1472
2
kesäk. 25
2985
3
huhtik. 25
3053
1
huhtik. 25
3834