Skip to content
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.

History route not actually enabled #45

Open
mkilp opened this issue Jul 18, 2018 · 3 comments
Open

History route not actually enabled #45

mkilp opened this issue Jul 18, 2018 · 3 comments

Comments

@mkilp
Copy link

mkilp commented Jul 18, 2018

Hey there!

I booted up my bot with a Mongo URI and according to the docs this should be enough to enable the message history.

The Bot tries to make a call to my localhost for the history. Sadly that returns with a 404:
client.js:77 POST http://localhost/botkit/history 404 (Not Found)

Any ideas what the problem could be?

Thanks alot,

Marvin

@peterswimm
Copy link

When your app spins up with the new mongo URI in place, does the console specify any error?

@Schaitel
Copy link

Hello @Nop0x!

Can you solve this?

@kareemgdiab
Copy link

When your app spins up with the new mongo URI in place, does the console specify any error?

no errors from mongodb, just deprecation warning
(node:4848) DeprecationWarning: current Server Discovery and Monitoring engine is deprecated, and will be removed in a future version. To use the new Server Discover and Monitoring engine, pass option { useUnifiedTopology: true } to the MongoClient constructor. (Use node --trace-deprecation ... to show where the warning was created)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants