Hi Rainer, Peeble has changes its error message in v2.9 regarding missing terms-of-service agreement. If fixed this in mod_md v2.6.9 and backport that to 2.4.x. Should be fine now, otherwise let me know.
Thanks, Stefan > Am 10.04.2026 um 08:50 schrieb Rainer Jung <[email protected]>: > > Using the current head of 2.4.x plus voted on mod_md backport and pebble > 2.10.0, I get a consistent failure for all MPMs, OpenSSL versions and > platforms: > > _________________________ TestAcmeAcc.test_md_202_000b > _________________________ > > self = <md.test_202_acmev2_regs.TestAcmeAcc object at 0x7f201e3703d0> > env = <md.md_env.MDTestEnv object at 0x7f201e1da7a0> > > def test_md_202_000b(self, env): > r = env.a2md(["acme", "newreg", "[email protected]"], raw=True) > assert r.exit_code == 1 > m = re.match(".*must agree to terms of service.*", r.stderr) > if m is None: > # the pebble variant > m = re.match(".*account did not agree to the terms of service.*", > r.stderr) > > assert m, "did not match: {0}".format(r.stderr) > E AssertionError: did not match: [md_cmd_acme.c:71 err][11(Resource > temporarily unavailabl)] register new account > E > E assert None > > modules/md/test_202_acmev2_regs.py:50: AssertionError > =========================== short test summary info > ============================ > FAILED modules/md/test_202_acmev2_regs.py::TestAcmeAcc::test_md_202_000b - > As... > > > I think it is likely just a failure in the test due to the mod_md and pebble > updates or test suite changes, and not in mod_md itself. But I could not find > out what exactly needs to change. > > Best regards, > > Rainer >
