This has been fixed in 1.2.9.9.1.
@owynter, I’ll await your access details to address issues that are specifically happening on your installation(s).
Cheers,