Skip to Content
เมนู
คุณต้องลงทะเบียนเพื่อโต้ตอบกับคอมมูนิตี้
คำถามนี้ถูกตั้งค่าสถานะ
203 มุมมอง

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


อวตาร
ละทิ้ง
Related Posts ตอบกลับ มุมมอง กิจกรรม
1
ก.ค. 25
1085
2
มิ.ย. 25
2612
3
เม.ย. 25
2737
1
เม.ย. 25
2887
1
ก.พ. 25
2072