Intermediate certificate Synology

[remycoopermusic]

My domain is: rcooper.myDS.me

I ran this command: SSL Checker

It produced this output:
Trusted: We were unable to verify this certificate
Chain Issues: The chain doesn't contain any intermediate certificates

My web server is (include version): Synology NAS

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): yes

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): Not sure. auto generating by control panel

Hi,

I get these errors on my synology nas's connected DDNS domain.

Trusted: We were unable to verify this certificate
Chain Issues: The chain doesn't contain any intermediate certificates

I'm trying to setup n8n in a docker container but the webhooks aren't secured (see the ssl errors). I'm doing some research and it seems like the ssl connection is the problem. I'm unsure how to fix this. Anyone has an idea? Thanks!

[Bruce5051]

Hello @remycoopermusic, welcome to the Let's Encrypt community.

@remycoopermusic

I ran this command: SSL Checker

Thank you for answering the question; but the question is more what command was run to obtain the certificate and deploy it.

I see this

Port 80 is filtered, thus the HTTP-01 challenge cannot succeed,
do you know which of the Challenge Types - Let's Encrypt is being used?

$ nmap -Pn -p80,443 rcooper.myds.me
Starting Nmap 7.80 ( https://nmap.org ) at 2024-12-04 16:16 UTC
Nmap scan report for rcooper.myds.me (82.151.171.109)
Host is up (0.20s latency).
Other addresses for rcooper.myds.me (not scanned): 2001:1c00:e17:9700:211:32ff:fe8e:3fc7
rDNS record for 82.151.171.109: 82-151-171-109.cable.dynamic.v4.ziggo.nl

PORT    STATE    SERVICE
80/tcp  filtered http
443/tcp open     https

Nmap done: 1 IP address (1 host up) scanned in 3.50 seconds

And is seems that the web server is reporting as nginx; server: nginx.
Probably more importantly is HTTP/2 502 - 502 Bad Gateway - HTTP | MDN

$ curl -Ii https://rcooper.myds.me
HTTP/2 502
server: nginx
date: Wed, 04 Dec 2024 16:15:59 GMT
content-type: text/html
content-length: 11939
etag: "62a83cc4-2ea3"

And here SSL Server Test: rcooper.myds.me (Powered by Qualys SSL Labs) is showing the intermediate certificate R11 is being sent twice. As does this https://decoder.link/sslchecker/rcooper.myds.me/443 and Hardenize Report: rcooper.myds.me

Using chrome shows

[Osiris]

Also, your IPv6 (address) seems to be malfunctioning. I can't connect to your hostname over IPv6 while IPv4 does work.