Redirect breaks LetsEncrypt issue/renew
If you use the Redirect feature with setting "permanent" and a path configured, the pre-defined acme-challenge directory redirects to /usr/local/... are no longer working correctly as the acme-challenge gets redirected to something like
and thus will display 404 or 403 and not renew or issue the certificate correctly. If the redirect feature in the WebUI ist configured, that should also change the preconfigured "/.well-known/acme-challenge" config block to "/<redirect_path/.well-known/acme-challenge"
happened on ISPConfig latest stable (3.1.6) running with nginx web server. Had a software installed in a sub-path element () and configured the redirect as type "permanent" with path "" so calls to https:/// will auto-rewritten to .../app/
Just spotted today, that LE cert was broken as it was never renewed correctly.
Redirect feature with setting permanent is not intended for use with path setting. It is to redirect to URLs.
Sorry but that makes minor sense to me. You have a field redirect type and redirect path and you shouldn't use them together? So why does it not simply disable the path box if permanent isn't wanted to interact with it?
Besides, the code that is produced, clearly indicates, that some thought went into not breaking other things like "stats":
``rewrite ?!/\(app|stats)\b)/(.*)$ /app/$2 permanent;
and is valid nginx rewrite code, even if perhaps it isn't the most beautiful answer to the problem. But if I see those functionality boxes as a customer I'd use them. So if it isn't intended to be used that way that should perhaps be stated somewhere or made clearer? And what would be the intended way to make it right without breaking LE code?