I was given an expired certificate

Is standard UTC time so Apr5 at 20:05:55

4 Likes

The whole appeal of YYYY-MM-DD is that no one uses YYYY-DD-MM, making it the only unambiguous date format. :sunglasses:

5 Likes

The only idiotic date format known to mankind is the mm-dd-yyyy notation (mostly) used by the US.

All other formats use a variant of the correct order (small to big, big to small) instead of the weird mixed up format.

3 Likes

Small to big sorts incorrectly and is just as bad a format as the one that most in the US prefer.

ISO 8601 or nothing at all. :wink:

5 Likes

I made update certbot --apache and get this error
...
[root@ligalc ~]# certbot --apache
Saving debug log to /var/log/letsencrypt/letsencrypt.log

Which names would you like to activate HTTPS for?
We recommend selecting either all domains, or all domains in a VirtualHost/server block.


1: ligalc.ru
2: www.ligalc.ru


Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel): 1
Requesting a certificate for ligalc.ru

Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/ligalc.ru/fullchain.pem
Key is saved at: /etc/letsencrypt/live/ligalc.ru/privkey.pem
This certificate expires on 2024-07-04.
These files will be updated when the certificate renews.
Certbot has set up a scheduled task to automatically renew this certificate in the background.

Deploying certificate
Successfully deployed certificate for ligalc.ru to /etc/httpd/conf.d/vhosts-le-ssl.conf
Error while running apachectl graceful.

Job for httpd.service invalid.

Unable to restart apache using ['apachectl', 'graceful']
Congratulations! You have successfully enabled HTTPS on https://ligalc.ru


If you like Certbot, please consider supporting our work by:


[root@ligalc ~]#
...

The site is loading, the certificate is now until July 4th, but for some reason it says that it is not protected

from another browser it says that the certificate is available and https:// is not crossed out

You got a couple of resources loaded over http:

2 Likes

I did everything as it was written there, but still https:// is crossed out..

![rootligalc~23|690x439](upload:// dALeDUVipodFUvTz8RxeJOAdsrC.png)
LiGaLC - Google C1212hrome
:man_shrugging:

Looks like whynopadlock website doesn't check everything. You can open Network tab of Web Tools of your web browser and see which resources are still loaded over http.

2 Likes

Thanks everyone for the answers! Indeed, I found some more mentions of http:// on my site using the command [root@ligalc ~]# grep -rl 'http://' /var/www/html, without hesitation I forwarded it to https:// and ... finally it worked as it should :slight_smile: learned a few lessons))

3 Likes

Learn this one: You don't really need to specify HTTP or HTTPS within the same site.

As a very basic example, instead of replacing: "http://my.example.com/folder/picture.jpg"
with: "https://my.example.com/folder/picture.jpg"
try using just: "/folder/picture.jpg"

4 Likes

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