Yeah, I agree. In the previous error stack, it says it rolled back the changes, which would explain why it’s the same.
Can we try stop the webserver? This would help narrow down why Certbot can’t restart it.
sudo service apache2 stop
and then verify nothing’s running on port 80:
sudo ss -tlnp | grep ":80"