The letsencrypt flavor served certbot's April-expired state to live IMAPS users within minutes of #90: autocert.Manager.HTTPHandler answers 404 itself for tokens it does not hold and never consults the fallback for challenge paths, so mailu's own ACME client cannot answer through its path-scoped route. Back to cert (valid to Nov 27) until route-proxy's handler actually falls through — that fix is mesh-controller's, in flight.
The letsencrypt flavor served certbot's April-expired state to live IMAPS users within minutes of #90: `autocert.Manager.HTTPHandler` answers 404 itself for tokens it does not hold and never consults the fallback for challenge paths, so mailu's own ACME client cannot answer through its path-scoped route. Back to `cert` (valid to Nov 27) until route-proxy's handler actually falls through — that fix is mesh-controller's, in flight.
The letsencrypt flavor served certbot's April-expired state to live IMAPS
users within minutes: autocert's HTTPHandler answers 404 itself for
tokens it does not hold and never consults the fallback for challenge
paths, so mailu's own client cannot answer through the path-scoped
route. cert flavor (valid to Nov 27) until route-proxy's handler
actually falls through.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The letsencrypt flavor served certbot's April-expired state to live IMAPS users within minutes of #90:
autocert.Manager.HTTPHandleranswers 404 itself for tokens it does not hold and never consults the fallback for challenge paths, so mailu's own ACME client cannot answer through its path-scoped route. Back tocert(valid to Nov 27) until route-proxy's handler actually falls through — that fix is mesh-controller's, in flight.