Unsecure HTTPS connection problem

Configuration
, , ,
1

Hi all. I have a problem with https connection from duckdns address that I never had before.

I have duckdns and NGINX installed. In my modem I have forwarded the port 443 to 443, 1884 to 1884 and 8884 to 8884.

Everithing work fine. Chrome tells me that the connection is secure and the certificate is valid. But when I go to Zigbee2MQTT addon in the addons page and hit F5 to refresh page, a red screen comes up that says “the site ahead contains harmful program” and I really don’t know what to do…

The screen also comes up on other addons (not all): NGINX, Node-red, terminal-SSH, Studio code server. If I continue browsing I get “not secure” next to the address bar in Chrome. If I click on it it tells me “the connection to this site is not fully secured” or “this site is not secure.”
The certificate always remains valid. If I return to my main dashbord and hit F5 everithing is unsecure and unsafe. If I close and reopen chrome all return secure untill I go on addons page.

Same message on firefox or edge

Any ideas?

2

Are you doing this locally. Maybe you switch between local and WAN address

OR

Maybe cert is tied to HA but addons report as different name so it not match cert. in this case connection still secure but you get warning. Click on cert when message appear and check what it report on addon pages and confirm it is same as HA page

3

Thank you for your reply.

The problem occurs both when accessing from a PC via duckdns and when accessing from a smartphone remotely.

I’ve checked the certificate and it’s the same in main dashboard and in addons pages.

4

What is cert expiry date?

Clear cache and try again?

Are you sure addons not changing from https to http?

5

What is cert expiry date?

28 January 2023

Clear cache and try again?

Done. Still the problem

Are you sure addons not changing from https to http

Still httpS when I go on addons page

I don’t know if it’s something about my modem but I didn’t changed anything in the past month

6

Look at the url in your browser.
Your certificate is specific to the domain names and hosts listed in it, so majorhector.duckdns.org is not the same as www.majorhector.duckdns.org or mqtt.majorhector.duckdns.org.
You can also not use a certificate with IP addresses, since certificates certify domain names.

7

I’ll check. I generated the certificate via the Duckdns addon. If what you say turns out to be my problem, how do I generate the certificate correctly? I’m quite new to home assistant

8

If it is because the domain does not exactly fit, then you need to look at the documentation for DuckDNS and see what options you have for adding extra domains or aliases.

I have only shortly used DuckDNS, since I have a fixed public IP and my Let’s Encrypt certificates are generated on another system than my HA installation.

9

I’ll check the documentation.

If I want use fixed public IP (that I have) is a better choice or is better using a DDNS service? It’s equally secure?

10

If you have a fixed public IP, then using DuckDNS just means you get a DuckDNS domain name for your IP address. You do not get a dynamic IP address through DuckDNS. The dynamic or fixed IP address is set up through your ISP.

You need a domain name though, since certificates rely on that.
In some places domain names are extremely expensive to own and in other places they are pretty cheap.

And security has no meaning in this relation.

11

I’ve checked. Still same domain name (XXX.duckdns.org/something/). The following image explain the problem. I have it only with a couple of addons. And if I hit F5 to refresh, a red screen comes up

Immagine
Immagine765×270 15.9 KB

I’ve also done a fresh install with only duckdns and one of these addons. Still the problem

12

It looks like some of your addons provide elements in the web page that is delivered on a non-secure connection.
This can sometimes just be as simple as a logo linked to manufacturers homepage, but it can also sometimes be elements served on another port on the host, which is not secure by nginx.

You need to look at the elements in the webpage then

13

I’ve found the problem! there was a link in the information that pointed to http instead of httpS. Modified that one it didn’t give me any more problems. Thank you all for helping me