Botium Webhook connection error to Kore.ai - webhooks

I want to integrate Botium Community Edition with our Kore.ai platform. I've created a Webhook channel and set the generated Webhook Url, Client ID and Client Secret in my testbot on Botium. When I select Live Chat and hit Connect I get a 'ChatBot Connected' message. However, when I try to chat with my bot I get the following error:
Failed sending to chatbot: rest request failed: { Error: tunneling socket could not be
established, cause=connect ECONNREFUSED 127.0.0.1:80 at ClientRequest.onError
(/app/server/node_modules/tunnel-agent/index.js:177:17) at Object.onceWrapper
(events.js:285:13) at ClientRequest.emit (events.js:197:13) at Socket.socketErrorListener
(_http_client.js:397:9) at Socket.emit (events.js:197:13) at emitErrorNT
(internal/streams/destroy.js:82:8) at emitErrorAndCloseNT (internal/streams/destroy.js:50:3) at
processTicksAndRejections (internal/process/next_tick.js:76:17) code: 'ECONNRESET' }
Please advice! Thanks!

Related

Cannot Log In Bixby Studio

Bixby Studio could not contact the authentication system at https://bixbydevelopers.com. Please check the URL url and your internet connection, and try again.
[error] [electron] Unable to fetch valid version from url: https://bixbydevelopers.com/dev/v2/valid-ide-version-range FetchError: request to https://bixbydevelopers.com/dev/v2/valid-ide-version-range failed, reason: unable to verify the first certificate
at ClientRequest. (C:\Users\hung.nv14\AppData\Local\Programs\BixbyStudio\resources\app.asar\node_modules\node-fetch\lib\index.js:1461:11)
at ClientRequest.emit (events.js:322:22)
at ClientRequest.EventEmitter.emit (domain.js:482:12)
at TLSSocket.socketErrorListener (_http_client.js:426:9)
at TLSSocket.emit (events.js:310:20)
at TLSSocket.EventEmitter.emit (domain.js:482:12)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
type: 'system',
errno: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE',
code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE'
}
Is it possible that you are routing all of your network traffic through a proxy or VPN? If so, can you try without going through them?

Timeout OrientDB Error in NodeJS Application

I have developed NodeJS application and using OrientDB database in our project. Everything works fine until we left the application idle for sometime. We are facing time out error in OrientDB.
Please find the error below:
Unhandled rejection OrientDB.ConnectionError [2]: read ETIMEDOUT
at Connection.handleSocketError (/home/myuser/sample_app/node_modules/orientjs/lib/transport/binary/connection.js:352:9)
at Socket.emit (events.js:315:20)
at Socket.EventEmitter.emit (domain.js:485:12)
at emitErrorNT (internal/streams/destroy.js:100:8)
at emitErrorCloseNT (internal/streams/destroy.js:68:3)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
Please advice

Problem with reason: connect ECONNREFUSED in Node.js

I'm a beginner in node.js.
I would like to connect with API for training.
I'm behind the company proxy.
I have an api-key: http://numbersapi.com/2000/math?json and I want to connect via node-fetch, but I get an error in console:
Error: { FetchError: request to http://numbersapi.com/2000/math failed, reason: connect ECONNREFUSED 107.170.248.47:80
at ClientRequest.<anonymous> (C:\user\training\Node.js\number_API\node_modules\node-fetch\lib\index.js:1455:11)
at ClientRequest.emit (events.js:193:13)
at Socket.socketErrorListener (_http_client.js:397:9)
at Socket.emit (events.js:193:13)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at processTicksAndRejections (internal/process/task_queues.js:81:17)
message:
'request to http://numbersapi.com/2000/math failed, reason: connect ECONNREFUSED 107.170.248.47:80',
type: 'system',
errno: 'ECONNREFUSED',
code: 'ECONNREFUSED' }
I have set properties in .npmrc:
proxy=http://xxx.xxx.com:8080
https-proxy=http://xxx.xxx.com:8080
registry=https://registry.npmjs.org
To the best of my knowledge node-fetch does does not honor the environment variables or anything defined in .npmrc. You need to explicitly define the proxy.

Why is my app deployed through App Engine not able to connect to Cloud SQL postgres database?

I attempted to follow the guide here https://cloud.google.com/appengine/docs/flexible/nodejs/using-cloud-sql-postgres
to integrate my app with the Cloud SQL postgres instance. However I keep getting an error:
Updating service [default] (this may take several minutes)...failed.
ERROR: (gcloud.app.deploy) Error Response: [9] Application startup
error:
testpostgres#1.0.0 start /app node app.js
Unhandled rejection SequelizeConnectionError: connect ENOENT
/cloudsql/test-postgress:us-central1:testpostgress/.s.PGSQL.5432 at
connection.connect.err
(/app/node_modules/sequelize/lib/dialects/postgres/connection-manager.js:128:24) at Connection.connectingErrorHandler
(/app/node_modules/pg/lib/client.js:123:14) at emitOne
(events.js:116:13) at Connection.emit (events.js:211:7) at
Socket.reportStreamError
(/app/node_modules/pg/lib/connection.js:71:10) at emitOne
(events.js:116:13) at Socket.emit (events.js:211:7) at emitErrorNT
(internal/streams/destroy.js:64:8) at _combinedTickCallback
(internal/process/next_tick.js:138:11) at process._tickCallback
(internal/process/next_tick.js:180:9)
It must be a problem with my configuration, but I have tried everything I can think of. You can see or clone my project here:
https://github.com/fractalfrenzy/GCS_postgres_test
I know nothing of Node.js, but have a long experience with Java/Python/Go runtime.
Have you opened your CloudSQL instance for connection?
Try this: Configuring IP Connectivity

connect my noSQL(mongoDB) database with my nodeJS project. But it is not working fine

I am trying to connect my nodejs with mongoDB but it is not working fine as the following result below.
**
(node:11776) DeprecationWarning: Mongoose: mpromise (mongoose's default promise library) is deprecated, plug in your o
wn promise library instead: http://mongoosejs.com/docs/promises.html
{ MongoError: failed to connect to server [localhost:27017] on first connect [MongoError: connect ECONNREFUSED 127.0.0
.1:27017]
at Pool.<anonymous> (D:\KIT\YEAR II\Project\Nodejs\Vidjot\node_modules\mongodb-core\lib\topologies\server.js:336:3
5)
at emitOne (events.js:116:13)
at Pool.emit (events.js:211:7)
at Connection.<anonymous> (D:\KIT\YEAR II\Project\Nodejs\Vidjot\node_modules\mongodb-core\lib\connection\pool.js:2
80:12)
at Object.onceWrapper (events.js:317:30)
at emitTwo (events.js:126:13)
at Connection.emit (events.js:214:7)
at Socket.<anonymous> (D:\KIT\YEAR II\Project\Nodejs\Vidjot\node_modules\mongodb-core\lib\connection\connection.js
:187:49)
at Object.onceWrapper (events.js:315:30)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at emitErrorNT (internal/streams/destroy.js:64:8)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
name: 'MongoError',
message: 'failed to connect to server [localhost:27017] on first connect [MongoError: connect ECONNREFUSED 127.0.0.1
:27017]' }
**
Here is my source code
Make sure your mongo server is running # localhost:27017 and you have directories created to store data.
start using this command:
>mongod --port 27017 --dbpath c:\data\db

Resources