Hi community,
I’m desperate and would really appreciate some help.
Initially, I configured access to Home Assistant via DuckDNS and Let’s Encrypt, and then installed and configured Grafana in HA.
Everything worked without issues, and I was able to view the Grafana graphics in the HA dashboard cards, regardless of whether I was on the local network or remotely accessing them via DuckDNS.
Then I signed up for the NabuCasa subscription.
Primarily not because I needed it, since everything was working perfectly, but rather to support the project 
.
Thinking that it might then make sense to configure my access via NabuCasa, this was my next step.
I configured access via the cloud, deleted the keys (fullchain.pem and privkey.pem) on HA (SSL folder), and deleted the Let’s Encrypt integration, as well as the corresponding entries in my configuration.yaml (http entries with the DuckDNS address, the SSL certificate and the SSL key).
Up until then, everything was fine, and I was happy to have successfully switched to NabuCasa and cleaned my system of the previous configuration.
But then…
Now I have a problem with the Grafana add-on.
At first, after switching to NabuCasa, the Grafana graphs were no longer displayed in the HA cards at all (locally and remotely). I quickly discovered that this was because the links were still being accessed over HTTPS, as I had just created with the old configuration, and had to change them to HTTP.
But that was only the solution for local access, because as soon as I access remotely via NabuCasa, the graphs are still not displayed.
Direct access to the Grafana add-on always works, whether locally or remotely. It’s only the graphics displayed via links in HA cards that are causing problems.
Depending on the settings I tested (I don’t even remember exactly what I tried, there were that many), I get the following message in the HA card:
“401: Unauthorized”
or
(translated from the German)
“iframes pointing to websites with HTTPS cannot be loaded when Home Assistant is served over HTTPS”
I’ve already read a lot about this topic and tried Chatgpt for help and solutions, but unfortunately, still without success.
Although I’ve read that when I use NabuCasa, access should be automatically redirected via HTTPS through the NabuCasa proxy, Ingres seems to be the magic word here, or perhaps better said, the cause of the problem 
:), because no matter what I’ve tried, it hasn’t worked.
I would prefer to accomplish that without the nead of DuckDNS and Let’s Encrypt (if possible), as I no longer need them for remote access, but the solutions I’ve found have always pointed in this direction…
Or I’ve found complicated solutions involving internal access proxies, or something involving local certificates or self-signed…
I’m lost and don’t know where to start 
I was hoping to find a good and up-to-date step-by-step guide online, but unfortunately haven’t found one yet.
So I would be very grateful if someone could help me get this up and running again.
I’m looking for the simplest solution possible, one that I can also repeat at a later date so that I can maintain my system myself 
What would be the best solution?
Many many thanks for your help 
.