Yeah, for me neither.

Maybe DNS does not work in your environment. These tests work fine for me.

Most of it seems plausible since we're testing when the domain is not ready, and the error is about not being ready. I'm not sure about the processState in all cases though, seems like it should be "done" and not "running" (but perhaps that's ok when combined with an error because it can't finish.).

Doesn't work for me anymore

Rebasing

• Use array shapes

• Rename

• Improved AuthController docs
• More API docs
• More API docs, fixed regressions

• Hide not implemented routes
• API docs

• API docs

• Introduce PlanResource, add 'plans' to device info response

• Fix regressions, more api docs for the SignupController

There's some regressions I'm working on fixing.

I think for Roundcube and most other services the startup hook is early enough. Of course, the logon phase is a separate problem, as we need an authenticated user to get the config from cockpit.

Something similar is probably required for imap and potentially other subsystems, so I'm wondering if there is a better approach to make sure this plugin is initialized first.

Current git version gives the full error: