Skip to Content
Menu
This question has been flagged

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
Discard
Related Posts Replies Views Activity
1
Jul 25
1074
2
Jun 25
2598
3
Apr 25
2733
1
Apr 25
2856
1
Feb 25
2046