DragonFly DB hosted on AWS ECS show (blocked:mixed-content) on js and css pages

[chakaz]

Discussed in #1925

^{Originally posted by kkalchuri-solutelabs September 25, 2023}
Hi Team,

I hosted DragonFly DB on my AWS ECS cluster and connected it to an ALB and added a CNAME to it.
While the Dragonfly Index page shows the attached image content only.

On further investigation I found that status_page.js and status_page.css shows (blocked:mixed-content) error.
Looks like these pages are being loaded from a http site.
i.e http://static.dragonflydb.io/data-plane/status_page.css and http://static.dragonflydb.io/data-plane/status_page.js

I am using a default DragonFly DB image in my ECS.
Is there a way to solve this error and shows the full content of DragonFly

[chakaz]

BTW @kkalchuri-solutelabs could you tell us how do you use Dragonfly's HTTP interface and for what purposes?
Is there anything you'd like to see added there that would be useful?

[chakaz]

I see this was already converted to an issue: #1926
Closing this one as a duplicate

[kkalchuri-solutelabs]

BTW @kkalchuri-solutelabs could you tell us how do you use Dragonfly's HTTP interface and for what purposes? Is there anything you'd like to see added there that would be useful?

@chakaz
I am new to DragonFly and want to do a testing of it, just to check if DEV team can replace it with Redis.
I followed this document to install DragonFly DB image on our ECS cluster and connected it to a HTTPS domain.
I tried visiting the dashboard page to confirm if installation is successfully and observed the (blocked:mixed-content) error.