request to http://localhost:3978/api/messages failed, reason: connect ECONNREFUSED 127.0.0.1:3978

[baghaeifar]

No description provided.

[tonyanziano]

@baghaeifar this usually indicates that your bot is not running.

Please make sure you start your bot before trying to connect to it via the emulator.

Also, it is very hard to diagnose an issue without more information. Please provide more information about your scenario (steps taken to reproduce your issue, what type of bot you are using, etc.) and screenshots if possible.

[axelsrz]

Closing due to inactivity

[alatas]

I have the same problem. When I was starting the project with the IISExpress it seems to use localhost address, but it was starting to listen only on ::1 ipv6 address, not 127.0.0.1 ipv4 address.

When the emulator tries to connect to localhost:3978, emulatore resolves localhost to 127.0.0.1 ipv4 address, and then emulator gets ECONNREFUSED error. Because there is no listening application on 127.0.0.1 port 3978.

I changed the project run configuration from IISExpress to AspNetCore.Hosting. Then everything started to work correctly. Because it listens both ::1 and 127.0.0.1.

[funnysekhar2014]

I am getting the same error "request to https://localhost:3978/api/messages failed, reason: connect ECONNREFUSED 127.0.0.1:3978". But didnt understand the above solution provide by @alatas.
can someone help me in getting this resolved in step by step.

{
"error": {
"code": "ServiceError",
"message": "request to https://localhost:3978/api/messages failed, reason: connect ECONNREFUSED 127.0.0.1:3978"
}
}

Getting this message in CMD when NPM was started:

Please let me know if any other info is required

[jiehan1029]

Hi @alatas , I think I'm getting the same issue that the emulator is listening on ipv6 http://[::]:51208 while my SDK is trying to send activities to http://localhost:51208. Could you share how you fixed that? I don't know how to changed the project run configuration from IISExpress to AspNetCore.Hosting as your post said

---- update:
actually found the workaround using ngrok v2 as directed here #2389 (comment)