Botframework-emulator: Not ableto connect with any BotBuilder-Samples(Node.js Samples) using Bot botframework-emulator

Created on 20 Mar 2017  Â·  27Comments  Â·  Source: microsoft/BotFramework-Emulator

Bug P1 Pending

All 27 comments

Is your bot running locally or remotely?
Are you supplying MSA appId and password, or running without credentials?
What are you supplying for the bot endpoint?
What port is your bot listening on?

Hi Eric,

My Bot is running locally(I am using BotBuilder-Samples from https://github.com/Microsoft/BotBuilder-Samples).
I am running it without credentials.
My end point is http://localhost:3978/api/messages
Port is : 3978

Below error I got every time
[cid:[email protected]]

On more thing I would like to highlight here is, I am able to hit http://localhost:3978/api/messages from Advance Rest client but getting error “ERROR: ChatConnector: receive - no security token sent.“ so the concern is Node.js bot sample is listening on applied port properly but Bot emulator is not able to connect on that.

Regards,
Ravi Khatri

From: Eric Anderson [mailto:[email protected]]
Sent: Tuesday, March 21, 2017 1:29 AM
To: Microsoft/BotFramework-Emulator BotFramework-Emulator@noreply.github.com
Cc: Ravi Khatri Ravi.Khatri@kpit.com; Author author@noreply.github.com
Subject: Re: [Microsoft/BotFramework-Emulator] Not ableto connect with any BotBuilder-Samples(Node.js Samples) using Bot botframework-emulator (#132)

Is your bot running locally or remotely?
Are you supplying MSA appId and password, or running without credentials?
What are you supplying for the bot endpoint?
What port is your bot listening on?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/BotFramework-Emulator/issues/132#issuecomment-287879462, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AZQhVivjhzHPvORhQT11Jm6FY7LjJv5pks5rntqBgaJpZM4MifJl.

This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails.

Your screenshot of the error didn't come through via email. Can you repost it?

Please find attached error screenshot.

Regards,
Ravi Khatri

From: Eric Anderson [mailto:[email protected]]
Sent: Tuesday, March 21, 2017 10:49 PM
To: Microsoft/BotFramework-Emulator BotFramework-Emulator@noreply.github.com
Cc: Ravi Khatri Ravi.Khatri@kpit.com; Author author@noreply.github.com
Subject: Re: [Microsoft/BotFramework-Emulator] Not ableto connect with any BotBuilder-Samples(Node.js Samples) using Bot botframework-emulator (#132)

Your screenshot of the error didn't come through via email. Can you repost it?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/BotFramework-Emulator/issues/132#issuecomment-288152359, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AZQhVjtiwpNly4jdNpxFKLJVWC1NgxXdks5roAZ0gaJpZM4MifJl.

This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails.

Still didn't make it. I think you'll have to copy/paste it directly into github. I guess github has problems receiving images over email.

The message ERROR: ChatConnector: receive - no security token sent is expected when the bot is running without credentials and accepts a connection from something that doesn't appear to be the emulator, so it isn't unusual that you saw it when using Advance Rest client.

Can you describe the error you are getting in the emulator?

error_screenshot

even my bot is listening on 3978 port. please see below screenshot

code

Everything looks correct, I'm stumped. Maybe an invisible character in the appId or password field? You might try deleting your endpoint and re-adding it.

Yes Eric,
I tried all these but no luck.

From: Eric Anderson [mailto:[email protected]]
Sent: Wednesday, March 22, 2017 8:55 AM
To: Microsoft/BotFramework-Emulator BotFramework-Emulator@noreply.github.com
Cc: Ravi Khatri Ravi.Khatri@kpit.com; Author author@noreply.github.com
Subject: Re: [Microsoft/BotFramework-Emulator] Not ableto connect with any BotBuilder-Samples(Node.js Samples) using Bot botframework-emulator (#132)

Everything looks correct, I'm stumped. Maybe an invisible character in the appId or password field? You might try deleting your endpoint and re-adding it.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/BotFramework-Emulator/issues/132#issuecomment-288287790, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AZQhVtiy88Q_X0pX5tv8J0BxJ-kjUbwpks5roJR4gaJpZM4MifJl.

This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails.

I think the next step would be to run fiddler as a local proxy to capture more detail about the error and facts leading up to it.

Okay, Sorry but I am not aware about fiddler.
Could you please help me on that.
even I have installed fiddler on my machine.

From: Eric Anderson [mailto:[email protected]]
Sent: Wednesday, March 22, 2017 10:34 PM
To: Microsoft/BotFramework-Emulator BotFramework-Emulator@noreply.github.com
Cc: Ravi Khatri Ravi.Khatri@kpit.com; Author author@noreply.github.com
Subject: Re: [Microsoft/BotFramework-Emulator] Not ableto connect with any BotBuilder-Samples(Node.js Samples) using Bot botframework-emulator (#132)

I think the next step would be to run fiddlerhttps://www.telerik.com/download/fiddler as a local proxy to capture more detail about the error and facts leading up to it.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/BotFramework-Emulator/issues/132#issuecomment-288468287, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AZQhVnM61z5khL9qZJL4APcl782XjiMnks5roVRqgaJpZM4MifJl.

This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails.

I have the exact same issue, unable to use the bot framework emulator to connect to my local running bot.
When fiddler is running, I can see some details :
WARN: ChatConnector: receive - emulator running without security enabled. ChatConnector: message received. Error: Request to 'http://localhost:52672/v3/botstate/emulator/users/default-user' failed: [404] Not Found at Request._callback (c:\usr\botpoc\messages\node_modules\botbuilder\lib\bots\ChatConnector.js:452:46) at Request.init.self.callback (c:\usr\botpoc\messages\node_modules\request\request.js:188:22) at emitTwo (events.js:106:13) at Request.emit (events.js:191:7) at Request.<anonymous> (c:\usr\botpoc\messages\node_modules\request\request.js:1171:10) at emitOne (events.js:96:13) at Request.emit (events.js:188:7) at IncomingMessage.<anonymous> (c:\usr\botpoc\messages\node_modules\request\request.js:1091:12) at IncomingMessage.g (events.js:291:16) at emitNone (events.js:91:20)

@ravik12KPIT fiddler (downloadable from the link I provided earlier) is network inspection software. It lets you view all the network traffic sent and received from your computer. It can offer more detailed information about which network request is failing.

@sapson The emulator will return 404 from the state API if there's no active bot connection. Was the emulator connected to your bot?

@eanders-MS No the emulator is unable to connect to the bot, same symptoms as user @ravik12KPIT has reported. I can test the bot from the console, or after deployment to azure. But the emulator is unable to connect the bot running on localhost. Only when fiddler is active I get some more info (as shared).

@eanders-MS After running fiddler the Bot Emulator is able to connect to my node.js code but when I say Hi then I am getting below error.
error ocurred [Error: Request to 'http://localhost:53524/v3/conversations/kl4kd1jennea659mc/activities/ic80ehll62hg1fhac' fail
ed: [403] Access Denied]

and below are the screenshots

capture

capture1

From: Ronny De Lafaille [mailto:[email protected]]
Sent: Tuesday, March 28, 2017 10:40 PM
To: Microsoft/BotFramework-Emulator BotFramework-Emulator@noreply.github.com
Cc: Ravi Khatri Ravi.Khatri@kpit.com; Mention mention@noreply.github.com
Subject: Re: [Microsoft/BotFramework-Emulator] Not ableto connect with any BotBuilder-Samples(Node.js Samples) using Bot botframework-emulator (#132)

@eanders-MShttps://github.com/eanders-MS No the emulator is unable to connect to the bot, same symptoms as user @ravik12KPIThttps://github.com/ravik12KPIT has reported. I can test the bot from the console, or after deployment to azure. But the emulator is unable to connect the bot running on localhost. Only when fiddler is active I get some more info (as shared).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/BotFramework-Emulator/issues/132#issuecomment-289838803, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AZQhVi8AtacGsfpRvmVwG4BIjs8A_dZjks5rqT7VgaJpZM4MifJl.

This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails.

@ravik12KPIT With your bot and emulator running locally, could you send me:

  • the first few lines of your emulator log, I'd like to see the host & port your emulator is listening on.
  • the JSON content of a message sent from the emulator to your bot (copy/paste) from the emulator's detail view. I'd like to see what the serviceUrl is set to.
  • the JSON of a reply sent from the bot to the emulator (available from fiddler).

Thank you!

From: Eric Anderson [mailto:[email protected]]
Sent: Wednesday, April 5, 2017 9:21 PM
To: Microsoft/BotFramework-Emulator BotFramework-Emulator@noreply.github.com
Cc: Ravi Khatri Ravi.Khatri@kpit.com; Mention mention@noreply.github.com
Subject: Re: [Microsoft/BotFramework-Emulator] Not ableto connect with any BotBuilder-Samples(Node.js Samples) using Bot botframework-emulator (#132)

@ravik12KPIThttps://github.com/ravik12KPIT With your bot and emulator running locally, could you send me:

  • the first few lines of your emulator log, I'd like to see the host & port your emulator is listening on.

    • This is emulator Log
      [12:42:01] ngrok not configured (only needed when connecting to remotely hosted bots)
      [12:42:01] Howto: Network tunneling with ngrok
      [12:42:01] Configure ngrok
      [12:42:01] Checking for new version...
      [12:42:06] Application is up to date.
      [12:42:25] -> POST 202 [conversationUpdate]
      [12:42:25] -> POST 202 [conversationUpdate]
      - And below are node.js code log

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

D:\MS BotSetup\HRBotSample-master>node app.js
restify listening to http://[::]:3978
WARN: ChatConnector: receive - emulator running without security enabled.
ChatConnector: message received.
WARN: ChatConnector: receive - emulator running without security enabled.
ChatConnector: message received.
WARN: ChatConnector: receive - emulator running without security enabled.
ChatConnector: message received.
session.beginDialog(/)
/ - waterfall() step 1 of 2
/ - session.beginDialog(BotBuilder:Prompts)
.Prompts.choice - session.send()
.Prompts.choice - session.sendBatch() sending 1 messages
And error ocurred [Error: Request to 'http://localhost:59757/v3/conversations/3dcna28f49kamn077c/activities/3dd9b8ffn08i55fnf' fai
led: [403] Access Denied]

  • the JSON content of a message sent from the emulator to your bot (copy/paste) from the emulator's detail view. I'd like to see what the serviceUrl is set to.
    {
    "type": "message",
    "text": "Hi",
    "from": {
    "id": "default-user",
    "name": "User"
    },
    "locale": "en-US",
    "timestamp": "2017-04-06T07:15:01.565Z",
    "channelData": {
    "clientActivityId": "1491462744798.8264607637491557.0"
    },
    "id": "3dd9b8ffn08i55fnf",
    "channelId": "emulator",
    "localTimestamp": "2017-04-06T12:45:01+05:30",
    "recipient": {
    "id": "default-bot",
    "name": "Bot"
    },
    "conversation": {
    "id": "3dcna28f49kamn077c"
    },
    "serviceUrl": "http://localhost:59757"
    }

  • the JSON of a reply sent from the bot to the emulator (available from fiddler).

· -= Fiddler Event Log =-

· See http://fiddler2.com/r/?FiddlerLog for details.

·

· 12:30:10:7356 Fiddler Running...

· 12:30:10:8176 Windows 8+ AppContainer isolation feature detected.

· 12:30:13:7759 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance

· 12:35:48:7789 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance

· 12:35:52:5307 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance

· 12:35:53:1571 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance

· 12:37:00:8593 [Fiddler] No HTTP request was received from (firefox:11724) new client socket, port 50658.

· 12:37:00:8593 [Fiddler] No HTTP request was received from (firefox:11724) new client socket, port 50660.

· 12:37:00:8593 [Fiddler] No HTTP request was received from (firefox:11724) new client socket, port 50653.

· 12:37:00:8593 [Fiddler] No HTTP request was received from (firefox:11724) new client socket, port 50657.

· 12:39:58:7856 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance

· 12:45:03:2914 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance

Thank you!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/BotFramework-Emulator/issues/132#issuecomment-291905752, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AZQhVig7lRPzBxmxqDzVcl0F7ukvVNwHks5rs7hNgaJpZM4MifJl.

This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails.

@eanders-MShttps://github.com/eanders-MS Please go through below required data.
From: Ravi Khatri
Sent: Thursday, April 6, 2017 12:54 PM
To: 'Microsoft/BotFramework-Emulator' reply@reply.github.com; Microsoft/BotFramework-Emulator BotFramework-Emulator@noreply.github.com
Cc: Mention mention@noreply.github.com
Subject: RE: [Microsoft/BotFramework-Emulator] Not ableto connect with any BotBuilder-Samples(Node.js Samples) using Bot botframework-emulator (#132)

From: Eric Anderson [mailto:[email protected]]
Sent: Wednesday, April 5, 2017 9:21 PM
To: Microsoft/BotFramework-Emulator <[email protected]BotFramework-Emulator@noreply.github.com>
Cc: Ravi Khatri [email protected]Ravi.Khatri@kpit.com>; Mention <[email protected]mention@noreply.github.com>
Subject: Re: [Microsoft/BotFramework-Emulator] Not ableto connect with any BotBuilder-Samples(Node.js Samples) using Bot botframework-emulator (#132)

@ravik12KPIThttps://github.com/ravik12KPIT With your bot and emulator running locally, could you send me:

  • the first few lines of your emulator log, I'd like to see the host & port your emulator is listening on.

    • This is emulator Log
      [12:42:01] ngrok not configured (only needed when connecting to remotely hosted bots)
      [12:42:01] Howto: Network tunneling with ngrok
      [12:42:01] Configure ngrok
      [12:42:01] Checking for new version...
      [12:42:06] Application is up to date.
      [12:42:25] -> POST 202 [conversationUpdate]
      [12:42:25] -> POST 202 [conversationUpdate]
      - And below are node.js code log

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

D:\MS BotSetup\HRBotSample-master>node app.js
restify listening to http://[::]:3978
WARN: ChatConnector: receive - emulator running without security enabled.
ChatConnector: message received.
WARN: ChatConnector: receive - emulator running without security enabled.
ChatConnector: message received.
WARN: ChatConnector: receive - emulator running without security enabled.
ChatConnector: message received.
session.beginDialog(/)
/ - waterfall() step 1 of 2
/ - session.beginDialog(BotBuilder:Prompts)
.Prompts.choice - session.send()
.Prompts.choice - session.sendBatch() sending 1 messages
And error ocurred [Error: Request to 'http://localhost:59757/v3/conversations/3dcna28f49kamn077c/activities/3dd9b8ffn08i55fnf' fai
led: [403] Access Denied]

  • the JSON content of a message sent from the emulator to your bot (copy/paste) from the emulator's detail view. I'd like to see what the serviceUrl is set to.
    {
    "type": "message",
    "text": "Hi",
    "from": {
    "id": "default-user",
    "name": "User"
    },
    "locale": "en-US",
    "timestamp": "2017-04-06T07:15:01.565Z",
    "channelData": {
    "clientActivityId": "1491462744798.8264607637491557.0"
    },
    "id": "3dd9b8ffn08i55fnf",
    "channelId": "emulator",
    "localTimestamp": "2017-04-06T12:45:01+05:30",
    "recipient": {
    "id": "default-bot",
    "name": "Bot"
    },
    "conversation": {
    "id": "3dcna28f49kamn077c"
    },
    "serviceUrl": "http://localhost:59757"
    }

  • the JSON of a reply sent from the bot to the emulator (available from fiddler).

· -= Fiddler Event Log =-

· See http://fiddler2.com/r/?FiddlerLog for details.

·

· 12:30:10:7356 Fiddler Running...

· 12:30:10:8176 Windows 8+ AppContainer isolation feature detected.

· 12:30:13:7759 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance

· 12:35:48:7789 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance

· 12:35:52:5307 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance

· 12:35:53:1571 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance

· 12:37:00:8593 [Fiddler] No HTTP request was received from (firefox:11724) new client socket, port 50658.

· 12:37:00:8593 [Fiddler] No HTTP request was received from (firefox:11724) new client socket, port 50660.

· 12:37:00:8593 [Fiddler] No HTTP request was received from (firefox:11724) new client socket, port 50653.

· 12:37:00:8593 [Fiddler] No HTTP request was received from (firefox:11724) new client socket, port 50657.

· 12:39:58:7856 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance

· 12:45:03:2914 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance

Thank you!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/BotFramework-Emulator/issues/132#issuecomment-291905752, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AZQhVig7lRPzBxmxqDzVcl0F7ukvVNwHks5rs7hNgaJpZM4MifJl.

This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails.

@ravik12KPIT Are you running firewall or security software that is preventing the post back to the emulator? You may need to create a rule to allow emulator traffic.

Hi @ravik12KPIT, While we still don't have root cause for this issue, a workaround reported by another user is to change your endpoint protocol from http to https. YMMV. If it works, please let us know here.
https://localhost:3978/api/messages

Okay I will check it and let you know.

Sent from my Windows Phone


From: Eric Andersonnotifications@github.com
Sent: ‎30-‎05-‎2017 23:20
To: Microsoft/BotFramework-EmulatorBotFramework-Emulator@noreply.github.com
Cc: Ravi KhatriRavi.Khatri@kpit.com; Mentionmention@noreply.github.com
Subject: Re: [Microsoft/BotFramework-Emulator] Not ableto connect with any BotBuilder-Samples(Node.js Samples) using Bot botframework-emulator (#132)

Hi @ravik12KPIThttps://github.com/ravik12kpit, While we still don't have root cause for this issue, a workaround reported by another user is to change your endpoint protocol from http to https. YMMV. If it works, please let us know here.
https://localhost:3978/api/messages

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/BotFramework-Emulator/issues/132#issuecomment-304956316, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AZQhVkv7rP0hJe30L3R7boBHhfUrvqf7ks5r_FbagaJpZM4MifJl.

This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails.

Still not working just changed http://localhost:3978/api/messages to https://localhost:3978/api/messages.
From: Ravi Khatri
Sent: Wednesday, May 31, 2017 7:52 AM
To: Microsoft/BotFramework-Emulator reply@reply.github.com; Microsoft/BotFramework-Emulator BotFramework-Emulator@noreply.github.com
Cc: Mention mention@noreply.github.com
Subject: RE: [Microsoft/BotFramework-Emulator] Not ableto connect with any BotBuilder-Samples(Node.js Samples) using Bot botframework-emulator (#132)

Okay I will check it and let you know.

Sent from my Windows Phone


From: Eric Andersonnotifications@github.com
Sent: ‎30-‎05-‎2017 23:20
To: Microsoft/BotFramework-EmulatorBotFramework-Emulator@noreply.github.com
Cc: Ravi KhatriRavi.Khatri@kpit.com; Mentionmention@noreply.github.com
Subject: Re: [Microsoft/BotFramework-Emulator] Not ableto connect with any BotBuilder-Samples(Node.js Samples) using Bot botframework-emulator (#132)

Hi @ravik12KPIThttps://github.com/ravik12kpit, While we still don't have root cause for this issue, a workaround reported by another user is to change your endpoint protocol from http to https. YMMV. If it works, please let us know here.
https://localhost:3978/api/messages

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/BotFramework-Emulator/issues/132#issuecomment-304956316, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AZQhVkv7rP0hJe30L3R7boBHhfUrvqf7ks5r_FbagaJpZM4MifJl.

This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails.

I'm having the same issue and it appears that the Bot Emulator is configuring ngrok for some random local port - every time I restart the emulator it says "Emulator listening http://[::]:some-random-port". Once I enter in an actual endpoint, the emulator works for that endpoint but the ngrok association isn't updated. If you go to the ngrok traffic inspector page on localhost:4040 you can see the port it is listening on and it isn't the port in my emulator configuration. Seems to me, ngrok shouldn't be initialized until someone configures the endpoint URL.

i have same issue :(

It looks like various connection issues in the last two years have rolled into this one that may have been unrelated to each other. We're going to close this for now. Please open a new issue if you're on the latest version of the Bot Framework Emulator and experiencing connection issues while following a sample from BotBuilder-Samples.

Was this page helpful?
0 / 5 - 0 ratings