tootai
April 27, 2026, 1:34pm
1
“CustomMessage”: “cURL error 60: SSL: no alternative certificate subject name matches target hostname ‘github.com ’ (see libcurl - Error Codes ) for https://github.com/nextcloud-releases/notes/releases/download/v5.0.0/notes-v5.0.0.tar.gz”
“CustomMessage”: “cURL error 60: SSL: no alternative certificate subject name matches target hostname ‘github.com ’ (see libcurl - Error Codes ) for https://github.com/nextcloud-releases/contacts/releases/download/v8.4.4/contacts-v8.4.4.tar.gz”
Any clue?
Nextcloud Server version (e.g., 29.x.x) : => 33.0.2
Operating system and version (e.g., Ubuntu 24.04) : => Debian 13 trixie
Web server and version (e.g, Apache 2.4.25) : => Nginx 1.26.3
Reverse proxy and version _(e.g. nginx 1.27.2): => NA
PHP version (e.g, 8.3) : => 4.4.16
Is this the first time you’ve seen this error? => No
When did this problem seem to first start? => on last notes update
Installation method => VM
Are you using Cloudflare, mod_security, or similar? => No
What operating system and version are you using? I’ve seen something similar (but not 1:1 the same error) when the root CA used by GitHub were missing from the system because everything was too old. Another idea: MITM for network security on a corporate network.
What will be shown when you execute the following?
curl -Iv https://github.com/nextcloud-releases/notes/releases/download/v5.0.0/notes-v5.0.0.tar.gz
And please edit your post to use the support template .
tootai
April 27, 2026, 3:27pm
3
Debian 13, original message adapted.
Problem found: github.com doesn’t have ipv6(!), it was our tayga who did nat64 and used our certificate
Possibility to force update in ipv4?
With curl I could get it but not with occ …
