search

InQuest / omnibus

The OSINT Omnibus (beta release)
MIT License
316 stars 69 forks source link

connect error #34

Open bobdissel opened 4 years ago

bobdissel commented 4 years ago

Primary Question / Request

Do i need to setup a proxy?

[] Using configuration file (/home/obi/Downloads/omnibus-master/etc/omnibus.conf) ... [] Debug: False Welcome to the Omnibus shell! Type "session" to get started or "help" to view all commands. omnibus >> new inquest.net EXCEPTION of type 'ServerSelectionTimeoutError' occurred with message: '127.0.0.1:27017: [Errno 111] Connection refused' To enable full traceback, run the following command: 'set debug true' omnibus >>

What type of request is there?

Please explain the bug in a clear and concise manner

When i startup omnibus i get a error 111.

Steps to Recreate (If Applicable)

Is this preventing you from using the application?

If you selected Yes, please explain why fully

Do you have any screenshots, log output, tracebacks, or otherwise to support your requests?

deadbits commented 4 years ago

Hey @bobdissel, could you start Omnibus with the --debug argument and share the output here?

This will give a full Python trace-back, along with some version numbers and such that i'll be helpful to look into it

Thanks for reporting this :)

deadbits commented 4 years ago

The error EXCEPTION of type 'ServerSelectionTimeoutError' occurred with message: '127.0.0.1:27017: [Errno 111] Connection refused' is a MongoDB error. For Omnibus, you need a MongoDB instance somewhere reachable from the host your running Omnibus on. 127.0.0.1:27017 is the MongoDB defaults for a local instance but you can change this setting to any MongoDB server.

Also, just FYI - Redis running somewhere also reachable from your host is required for a few things, in case you don't have that setup already.