dashdot widget not showing (Nginx + CloudFlare)
I have an Unraid server that runs nginx as my reverse proxy. Everything within nginx is configured as http and cloudflare forces SSL. All my subdomains work as expected except for the dashdot widget in homarr. Homarr is setup behind an accesslist within nginx as it cannot be public like Jellyfin. When accessing homarr locally the widget works as expected. Please help me fix this widget when accessed through my reverse proxy
19 Replies
You must ensure that your Dash. and Homarr use the same protocol. The embed will fail if you try to embed http inside a https page.
You could proxy all requests (including Dash. and Homarr) with SSL or not proxy any.
I see. So if I wanted to force Dash to use https, how would I go about doing that?
Same as you do for all your other apps
Just to confirm: On what protocol is Homarr and Dash. running on?
within nginx, http. CloudFlare forces ssl
Okay. Then you have a problem, because it will work when you access it directly but not via Cloudflare.
correct
You need to decide, whether you want to use SSL strict or HTTP strict
You are not really allowed to mix them up.
Or I could setup another subdomain for dash, then setup the access list to have my home ip allow, everything else deny. Then reference my subdomain within homarr? Both would be https right?
This is not a restriction we set btw. All modern browsers do this to ensure that a website can be trusted and that you can't enter unencrypted stuff inside a SSL website
Yes, that should work.
ill try that and lyk if it works
thanks for the info
No problem. Please mark this post as resolved, when it worked. Otherwise, let me know
What ip would homarr be contacting dash from if the dash url in homarr? I guess one of cloudflare's right?
If it set dash's configuration to "Publicly Accessible" everything works over my reverse proxy. But I don't exactly want it to be publicly accessible. Do you know what I should setup within my access list in nginx to keep this secure? Or a way to force dash to use a certificate that I generate via command line
Homarr will contact from the external container IP
That depends on what your setup looks like. Usually, it's your WAN ip where the request will come from (so your internet connection).
In theory that would be the case but I'm using CloudFlare's Proxy setting. So my public IP isn't directly accessible and isn't the source of the traffic I don't think
The reason I say this is my access list didn't work and pinging my homarr's subdomain results in a different IP every so often. For example this is what you get if you try and access the resolved ip from a ping command
Sorry, but I can't really help you with that. I use Cloudflare myself too, but my setup is pretty minimal compared to yours.
I think you'll have to figure out an appropriate solution for your setup yourself. But if there's anything about Homarr you need help with, I'm happy to help
I think the solution is going to be to configure Dashdot to use ssl and to provide a certificate. The issue is it doesn't seem like that's been implemented yet?
That I don't know. But if it doesn't, you could try to use a reverse proxy and block direct access to it
I'll report back if I figure it out. Thanks for the assistance