Server fails to start after using bleeding edge version of deepforge-keras

[brollb]

Starting the server results in it failing to start if using the latest version of deepforge-keras:

~/projektek/deepforge(master*) » npm start -- -N                                                                                                                                                   brian@szamitogep

> [email protected] start /home/brian/projektek/deepforge
> node ./bin/deepforge start "-N"

MongoDB is already running!
MongoDB is already running!
2021-01-06T14:17:27.178Z - info: [gme] Node version v12.18.3
2021-01-06T14:17:27.179Z - info: [gme] Logfile [ info ] : /home/brian/projektek/deepforge/server.log
2021-01-06T14:17:27.179Z - info: [gme] Logfile [ error ] : /home/brian/projektek/deepforge/server-error.log
2021-01-06T14:17:27.188Z - info: [gme:server:standalone] Valid addresses of gme web server:  https://127.0.0.1:8888  https://192.168.0.11:8888
(node:3769380) UnhandledPromiseRejectionWarning: #<Object>
(node:3769380) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:3769380) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(deepforge-server) --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
~/projektek/deepforge(master*) »