SSL certificate problem on Self hosted server

🗃️ Hosting providers
1

Hello,

I have been running self-hosted NextCloud Instance on my RaspberryPi for more than 1 year. I run NextCloudPi version of NextCloud.

The SSL certificate is from Letsencrypt.

Recently, on my Linux Desktop (Lenovo Laptop) (where the NextCloud desktop AppImage also runs), I started seeing this pop up message:

Cannot connect securely to ‘myservername’ (I have replaced my original server name):
The host name did not match any of the valid hosts for this certificate
with Certificate mediarouter.home
Organization:
Unit:
Country: CN
Fingerprint (SHA1): 48:16:0b:dc:7e:84:d8:d7:0f:3a:86:1a:25:4f:c3:02:95:34:70:2f
Fingerprint (SHA-256): 35:ad:1a:02:e2:d5:3e:8c:92:cf:06:13:e7:72:f4:f5:6f:21:d1:fa:aa:86:16:fa:1a:5f:3f:8a:02:55:a3:67
Fingerprint (SHA-512): d5:83:27:66:eb:a4:63:4a:5d:59:86:07:71:5b:ee:fb:c9:eb:01:51:20:5d:2c:c9:2a:29:5e:2b:1f:b5:a1:f7:9f:0a:05:7d:cc:41:9b:c8:2b:f0:82:15:2a:75:18:f1:59:e3:3f:e2:07:2a:3c:a8:a6:c1:fc:48:73:f8:89:39

Effective Date: Tue Dec 2 00:00:01 2014 GMT
Expiration Date: Thu Nov 24 00:00:01 2044 GMT
Issuer: root.home
Organization:
Unit:
Country: CN

The root certificate of the certificate chain is self-signed, and untrusted
with Certificate root.home
Organization:
Unit:
Country: CN
Fingerprint (SHA1): f3:06:28:d6:42:1a:e3:c1:46:e5:02:cb:23:88:92:f6:20:46:38:85
Fingerprint (SHA-256): dc:42:88:2a:ee:6b:6d:b5:9f:ef:a9:f5:2e:f1:78:84:7c:84:c5:07:b5:f5:34:17:7d:64:de:72:3a:99:5c:76
Fingerprint (SHA-512): d0:50:7d:9e:fa:fe:7c:2a:f9:d0:7f:6e:35:03:58:03:4d:98:fa:06:30:c4:01:86:57:fc:4e:52:a3:04:0a:20:53:92:11:b9:60:9d:d9:c6:35:03:b0:c3:56:02:4b:1e:95:c0:c7:b5:f4:3d:b4:00:62:30:d8:eb:d3:3c:3c:16

Effective Date: Tue Dec 2 00:00:01 2014 GMT
Expiration Date: Thu Nov 24 00:00:01 2044 GMT
Issuer: root.home
Organization:
Unit:
Country: CN

I started wondering why it started popping up every now and then? I just cancel the request for trusting this certificate. On boot, the desktop app is connected to my NC server, but after I reject this message, it fails to do so.

My question is, why I am seeing this error message. This is certainly not a certificate from Letsencrypt. Is this an attack on my server or something like that?

P.S: Now thinking back, I believed this issue started after upgrading to NC 19.0.1. (if this information helps.)
Thanks for sharing your insight.

2

First of all, if you ise nextcloudpi you should not have updated to 19.0.1 at all, ncp provides curated updates for nextcloud, most of the time short after x.0.2 release of nextcloud. Use the ncp nc-autoupdate instead to stay on a working stable version of nextcloud.

Regarding the certificate, did you try to issue a new certificate through ncp pannel? Most likely you ran into an issue many of us experienced a while ago.

1 Like
3

Thanks for your response.

The problem seems to be resolved after I renewed the SSL certificate. Thanks!

Not relevant to the main post, but waiting for an update slower than the main release, isn’t a security threat in itself? Usually they say you should keep your system up to date?

Thanks again.

4

actually you get the point releases (we are now at 18.0.7) nearly instantly and are on a save version for sure. Just the major releases, which are feature releases, ncp waits to be reliably stable and tested with ncp.