I'd be surprised if that worked? Boulder has account reuse, but that's for reusing an account created on v1 account with v2, not the converse. My initial test of just putting in the old server URL doesn't seem to be working, anyway. (Note that you have to add a server URL to the top section of the renewal config, since this fix is specifically for the older configs where we saved it there automatically; we don't save it there anymore. The `server` line under `[renewalparams]` is something different.) We certainly relied on testing with an actual, old account when we first implemented this. Alex might have set up some sort of manual local Boulder config for testing, but I'm not sure exactly what he did; he mentions it here: https://github.com/certbot/certbot/issues/7979#issuecomment-635010077. To test with that we'd also probably have to go in and manually change the URLs being switched, since the URL being replaced is hard-coded.
** Bug watch added: github.com/certbot/certbot/issues #7979 https://github.com/certbot/certbot/issues/7979 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893274 Title: Certbot will stop working for 23,847 users with upcoming Let's Encrypt deprecation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1893274/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
