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. https://crt.sh/?q=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: www.example.com
I ran this command: $le_path/certbot certonly --standalone --preferred-challenges http --agree-tos --renew-by-default --config $config_file -d $domain --non-interactive --http-01-port $http_01_port
It produced this output: certs are renewed but linking to old
My web server is (include version): haproxy
The operating system my web server runs on is (include version): debian 10
My hosting provider, if applicable, is: virtual machine
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): none
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you’re using Certbot): certbot 0.31.0
I have a script which renews certs automatically on my HAPROXY server.
It gives output after each renew:
"Congratulations! Your certificate and chain have been saved at /etc/letsencrypt/live/www.example.com/fullchain.pem and /etc/letsencrypt/live/www.example.com/privkey.pem
But when I go to folder “/etc/letsencrypt/live/www.example.com” and list files “ls -la” there is a sumbolic links to old versions: “cert.pem -> …/…/archive/www.example.com/cert3.pem”
Why there are symbolic links, why it can’t work without them? and how can I fix this?