Postman: SSL Error: Certificate has expired - PLESK

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: xxxx

I ran this command: https://xxx/rest/V1/custom/bestsellers

It produced this output: SSL Error: Certificate has expired

My web server is (include version): Ubuntu16, PLESK 18, PHP 7.4

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is: Hetzner

I can login to a root shell on my machine (yes or no, or I don't know):
Yes, the server works fine in all areas.

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
PLESK 18.0.34
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
Any

The error is that when clicking any links like this:
https://xxxx/rest/V1/custom/bestsellers
https://xxxx/rest/V1/custom/brandFilterTags?face_area=Eyes

from a browser it works fine.

When I click it from inside of postman and from a flutter developer app it generates an error SSL Error: Certificate has expired.

I have tested this with SSL Server Test (Powered by Qualys SSL Labs)
it says the SSL certificate is expiring in 2months and 28 days.
I updated the certificate as late as today.

We can not find out what is wrong with the certificate and why it is reacting like this.

Any ideas?

Generally, it's a client problem. Are you using fullchain.pem in the configuration for your server?

1 Like

Hello , we have exactly the same problem today.

Same question - are you using 'fulchain.pem' on your server? If not, you need to do that and restart whatever service is failing. If it's Windows, that might require a reboot or addiontal work. On Unix/Mac OS, changing to fullchain.pem should fix it after restart of apache/ngnx/dovecot, etc.

this seems to be the problem.

I have not a new installation, but an old project that has been working for a long time. Today the specified error appeared for the first time when the perl script was running. Postman has the same problem. Curl is working fine.

For example my perl script have error: MESSAGE: Can't connect to [*******:443](certificate verify failed) and i check all in my fullchain.pem certificates(all ok)

  • Fixed an issue where Postman showed 'Certificate has expired' error for Let's Encrypt certificates - GitHub #10338

I check my cloudlinux system with perl script and have update:
cpanel-letsencrypt-v2
ca-certificates

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.