Thank you for the update, I can confirm that this error is now gone in my Directadmin.Pre-release binaries going up now. Will be pushing 1.61.2 with all changes in about 50 minutes.
If anyone has a moment to confirm it (I already have, but best to know for sure), let us know that it's working prior to the full release