SSL Cert not recognized by custom domain

Support
1

When I try to access my custom domain, I get notified that it’s not secure. As is shown in the following screenshot:

Screenshot from 2019-12-23 12-30-39
Screenshot from 2019-12-23 12-30-39880×638 52 KB

But when I check the Domains from within netlify app, it seems okay:

Screenshot of HTTPS Domain segment

Whether I use my custom domain, or default netlify app link it won’t go to the adequate port.
When I check Name Servers with dig, this is the output:

dig kaynetik.com ns 

; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> kaynetik.com ns
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14187
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;kaynetik.com.			IN	NS

;; ANSWER SECTION:
kaynetik.com.		3600	IN	NS	dns4.p07.nsone.net.
kaynetik.com.		3600	IN	NS	dns2.p07.nsone.net.
kaynetik.com.		3600	IN	NS	dns1.p07.nsone.net.
kaynetik.com.		3600	IN	NS	dns3.p07.nsone.net.

;; Query time: 54 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Dec 23 12:36:41 CET 2019
;; MSG SIZE  rcvd: 130

Hopefully, someone will see where I messed up. Thanks in advance! :wink:

2

Your certificate seems to cover only *.netlify.com websites. Is kaynetik.com defined as your primary domain and is Let’s Encrypt covering that domain and its subdomains?

1 Like
3

@obax Yes, it’s defined as my primary domain.
How do I check what’s LE cert covering? In that screenshot I provided in my initial post it states that LE is covering my domain… I opted for the automated netlify provisioning, so I think I don’t have any control over that.

Capture
Capture918×669 27.2 KB

4

I found this article which states that DNS chain could be hanging on Netlify’s end.

Does anyone know what is the average response time of the support team?
Or even better, some pointers as to how could I solve this by myself?

5

To see the certificate it’s Settings > Domain Management > HTTPS at the bottom of the page.

6

@obax Maybe you missed my link in the first post.

certificate
certificate935×675 31.2 KB

On both sides, everything seems fine, but I’m still unable to use https.

7

This was resolved by @laura at in this thread. I owe her some gratitude :relaxed:

1 Like