BotService Cannot mount bot "test". Make sure it exists on the filesytem or the database

Hi,
I have installed Botpress rencently, when I’m going to do a test I have this error I don’t know why!!
15:17:25.188 BotService Cannot mount bot “test”. Make sure it exists on the filesytem or the database.
HTTP (get) URL http://localhost:3001/api/v1/bots/test/mod/nlu/intents
Received "<!DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Transitional//EN” “http://www.w3.org/TR/xhtml1/DTD/xhtm (…)”
Request failed with status code 502
STACK TRACE
Error: Request failed with status code 502
at createError (/opt/botpress/modules/.cache/module__8045dde14b29ea6dba7102e7d69c7b4734e629202378b049ccd2f3696eedee87/node_production_modules/axios/lib/core/createError.js:16:15)
at settle (/opt/botpress/modules/.cache/module__8045dde14b29ea6dba7102e7d69c7b4734e629202378b049ccd2f3696eedee87/node_production_modules/axios/lib/core/settle.js:18:12)
at IncomingMessage.handleStreamEnd (/opt/botpress/modules/.cache/module__8045dde14b29ea6dba7102e7d69c7b4734e629202378b049ccd2f3696eedee87/node_production_modules/axios/lib/adapters/http.js:202:11)
at IncomingMessage.emit (events.js:187:15)
at IncomingMessage.EventEmitter.emit (domain.js:442:20)
at endReadableNT (_stream_readable.js:1081:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
I try it in Santa 7.3 can you help me please :slight_smile:

i try it in Cenos 7.3* sorry :slight_smile:

Hi,

Have you used the admin panel to create your bot? The admin panel is located at URL:

/admin/workspace/bots

If not, make you sure, you see the name of your bot in the configuration file:

/out/bp/data/global/workspaces.json

[
{
“id”: “default”,
“name”: “Default”,
“bots”: [ “YOUR_BOT_NAME_HERE”, …

Hope this information helps you!

François

Hi,

actually as far as the fileworksoace.json is concerned, I already wrote the name of the n=bot in bot [ test ], but the problem is still there.
What I find strange is that I installed Botpress in a CentOS 7.2 and the error was no longer there
I may think the mistake is not from botpress but from my centos 7.3
you have any ideas where it might come from.