Hmm, that's not an error message I've ever seen before. It's hard to pinpoint the exact cause without more information, but it could potentially be a bug in the oobabooga WebUI itself.
To troubleshoot this, I recommend first ensuring that you have the latest version of oobabooga installed. Additionally, make sure you're running the server with the
--extensions api option.
This should hopefully rectify the issue. If not, feel free to reach out for additional support.