SSL Problem

Configuration
1

Hello everyone,

I have a Duck DNS domain. It’s been working for weeks, and since today I’ve been getting SSL. When I try to log in with https://xxx.duckdns.org:8123, I get the following error: “An SSL error has occurred. A secure connection to the X server could not be established.”

Could someone please tell me what’s wrong? Thanks in advance!

2

Is that the only error you are getting?
Normally there is more information available.
Check if your SSL certificat is still valid (not expired)

3

Thanks for your response. How do I check those certificates?

4

When surfing to the page, take a screenshot of the error + check if there is a button to click that says something of the kind 'more information ’

Edit: if you post a screenshot, obfuscate your URL

5

I’m trying this with my iPhone, but it doesn’t work on my PC either, and I get this message. Yesterday, everything was still working.

error
error462×483 5.9 KB

6

And at the top of the screen it says this?
error2

7

If you are using Duckdns, it is probably because you do not have a fixed IP address at home. Can you check if that is still the same? Every once in a while your public IP might change and you’ll have to have a script update your ddns provider

8

Yes, the red icon specifies that it can not trust the SSL cert. Click on it and check what the error messages are.

9

Dangerous site
Attackers on the site you tried to visit could trick you…

10

Can you confirm the following:

11

yes, is the same

I can’t find the first one.

12

cer
cer530×642 33.2 KB

13

cer2
cer2539×580 45.2 KB

14

I’ve now deleted ‘http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem’ in the configuration.yaml, and http://xxx.duckdns.org is also unreachable!?
And on my phone, it keeps saying there’s an SSL problem!

15

I am experiencing this exact same issue. It’s been working fine for years. I’ve exhausted all avenues. I might try deleting duckdns and reinstall it but that is the only thing I can think of to do. It’s an ssl problem somewhere.

16

Thanks for your reply. I created a new duckdns domain, and now my problem is solved. But I can’t remove the old duckdns domain. Very strange.

17

Your ISP have listed the duckDNS domain as dangerous and they are now blocking access.
When you try to visit duckDNS your are redirected to an info page at your ISP telling you about the blocking.
The redirection keeps the url in the address bar, but info page does not have the right certificate for duckDNS, so you get the error you see.

18

Thanks for your reply. How can I fix this?

19

Talk to your ISP and hope they will listen or find another dynhost service.
I would probably go for the latter, because once they have added the domain the first it will happen again and again from then on.

Remember! If you are connecting over another ISP than what your HA server use, then it is that other ISPbthat is blocking.

20

it’s a common issue with duckdns, i used it before and gikk down often. very short time, but many times a day. its free and you get what you get. change to cloudflare, buy your own domain and setup cloudflare tunnel, safets with right WAF rules and never goes down. you will never go back. if you dont have domain, you can buy straight cheap from cloudflare and setup tunnel very easy