NomisCode
Mon, 24 Oct 2022 20:58:56 GMT
Tried restarting service, but looks like it throws same error.
Looks like this has been fixed in new release.
Yes. We addressed (or tried to) this issue in 5.1.3. Thanks for our report.