Certbot folder has broken symlinks

The reason no challenge file was created is that you removed --dry-run, which resulted in using the production server (instead of the staging server with --dry-run). The production server caches successful authorizations for 4 weeks, meaning that Let's Encrypt simply used an existing authorization for pmway.hopto.org rather than authorizing based on a new challenge file.

1 Like