<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
<title>503 certificate has expired</title>
<h1>Error 503 certificate has expired</h1>
<p>certificate has expired</p>
<p>Details: cache-lon4269-LON 1578748724 3864572170</p>
<p>Varnish cache server</p>
Note: it’s not the certificate of the direct public endpoint of
dl.eff.org, it’s some kind of internal certificate.
Kinda amateurish if you’d ask me
Perhaps we should ping
@bmw and @lestaff again.
May I suggest a long term solution and/or a better monitoring service?
I would encourage people to follow the normal instructions when possible, but as a temporary workaround, you can download certbot-auto from GitHub.
This file has been truncated.
# Download and run the latest release version of the Certbot client.
# NOTE: THIS SCRIPT IS AUTO-GENERATED AND SELF-UPDATING
# IF YOU WANT TO EDIT IT LOCALLY, *ALWAYS* RUN YOUR COPY WITH THE
# "--no-self-upgrade" FLAG
# IF YOU WANT TO SEND PULL REQUESTS, THE REAL SOURCE FOR THIS FILE IS
# letsencrypt-auto-source/letsencrypt-auto.template AND
set -e # Work even if somebody does "sh thisscript.sh".
# Note: you can set XDG_DATA_HOME or VENV_PATH before running this script,
# if you want to change where the virtual environment will be installed
# HOME might not be defined when being run through something like systemd
if [ -z "$HOME" ]; then
Depending on your OS, you could use one of the other Certbot installation methods as well.
It seems to be OK again now. (Thanks for the reports.)
Any idea of a more permanent solution was enabled?
So automated certificate client didn’t automated their certificate?
It worked for me now. Sadly I am automating an install on Centos 8 so I have to download the program from
dl.eff.org. I don’t understand why it’s not in the standard repo this far into the 21st century.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.