BotFramework-Emulator: Ngrok doesn't work with Emulator
Github issues should be used for bugs and feature requests. Use Stack Overflow for general “how-to” questions.
Version
4.14
Describe the bug
After upping the application and providing request through ngrok, ngrok falls down and give an exception
“Oops… Your ngrok tunnel seems to have an error. Please check the Ngrok Status Viewer for more details”
“Looks like the ngrok tunnel does not exist anymore…”
Using last version of ngrok and emulator, the links provided properly.
The last log from ngrok
Ngrok Logger starting
t=2021-10-04T13:58:03+0300 lvl=info msg="received stop request" obj=app stopReq="{err:<nil> restart:false}"
t=2021-10-04T13:58:03+0300 lvl=info msg="session closing" obj=tunnels.session err=nil
t=2021-10-04T13:58:03+0300 lvl=info msg="no configuration paths supplied"
t=2021-10-04T13:58:03+0300 lvl=info msg="ignoring default config path, could not stat it" path=/home/maxim/.ngrok2/ngrok.yml err="stat /home/maxim/.ngrok2/ngrok.yml: no such file or directory"
t=2021-10-04T13:58:03+0300 lvl=info msg="starting web service" obj=web addr=127.0.0.1:4040
t=2021-10-04T13:58:03+0300 lvl=info msg=start pg=/api/tunnels id=4823c88208bf2173
t=2021-10-04T13:58:03+0300 lvl=warn msg="ngrok is not yet ready to start tunnels" pg=/api/tunnels id=4823c88208bf2173 err="a successful ngrok tunnel session has not yet been established"
t=2021-10-04T13:58:03+0300 lvl=info msg=end pg=/api/tunnels id=4823c88208bf2173 status=503 dur=1.089392ms
t=2021-10-04T13:58:03+0300 lvl=info msg=start pg=/api/tunnels id=8f5a59c2760d0499
t=2021-10-04T13:58:03+0300 lvl=warn msg="ngrok is not yet ready to start tunnels" pg=/api/tunnels id=8f5a59c2760d0499 err="a successful ngrok tunnel session has not yet been established"
t=2021-10-04T13:58:03+0300 lvl=info msg=end pg=/api/tunnels id=8f5a59c2760d0499 status=503 dur=368.768µs
t=2021-10-04T13:58:03+0300 lvl=info msg=start pg=/api/tunnels id=aac441a0694d3788
t=2021-10-04T13:58:03+0300 lvl=info msg="tunnel session started" obj=tunnels.session
t=2021-10-04T13:58:03+0300 lvl=info msg="client session established" obj=csess id=18bdb6edcb1f
t=2021-10-04T13:58:03+0300 lvl=info msg="started tunnel" obj=tunnels name="e6b52930-2501-11ec-8791-b181e964dc45 (http)" addr=http://localhost:32815 url=http://bd35-178-238-114-10.ngrok.io
t=2021-10-04T13:58:03+0300 lvl=info msg="started tunnel" obj=tunnels name=e6b52930-2501-11ec-8791-b181e964dc45 addr=http://localhost:32815 url=https://bd35-178-238-114-10.ngrok.io
t=2021-10-04T13:58:03+0300 lvl=info msg=end pg=/api/tunnels id=aac441a0694d3788 status=201 dur=277.407116ms
t=2021-10-04T13:58:08+0300 lvl=info msg="join connections" obj=join id=b0ab7155ea5b l=[::1]:32815 r=178.238.114.10:59380
To Reproduce
Steps to reproduce the behavior:
- Turn up the bot
- Open Emulator
- Choose the bot config
- Emulator get error, written upper.
Expected behavior
Emulator starts conversationUpdate and then user can interract with user
Screenshots
Additional context
[bug]
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 2
- Comments: 25 (11 by maintainers)
Hello all, the new nightly build is finally out with the fix to Ngrok:
https://github.com/microsoft/botframework-emulator-nightlies/releases/tag/v4.14.0-277368
Thank you for your patience! Keep an eye out for a stable release of Emulator as well if you don’t want to switch to the nightly for now.
Stable version 4.14.1 is now available as well.
@tonyanziano thank you for investigating this issue, and for being so transparent of your steps to resolve it 😃
The builds have been fixed, and we just merged my change in. I will kick off a nightly build and update this thread when it is out.
We will most likely release a stable patch as well (4.14.1).
Hello all,
We’ve figured out the problem with the Windows build. It turns out that the special internal build of Electron that we use just recently started shipping pre-signed, so we were trying to re-sign a binary that was already signed which was causing the error.
Our plan is to modify our build pipeline to unsign the binary before re-signing it, and then hopefully it should word like normal.
There was also a Mac certificate that seems to have expired in our Mac pipeline, also blocking that one from releasing. However, we think we know what the problem is, and hope to have both pipelines fixed tomorrow.
We should have a new Emulator build out either tomorrow or Thursday. Thank you for your patience!
Hey all, another update:
We’ve tested the build and confirmed the fix, and are updating our build pipelines to accommodate the new Electron version. Mac and Linux are building, but we are having some trouble with the external service that signs our Windows .exe.
I’ve reached out to the team that runs the service and hope to have a resolution soon so we can get a new build out and unblock those who are affected by this ngrok issue.
So it looks like the better approach is to just update Electron. A fix for the expired cert was merged into Electron and backported to versions 12 and up.
I’m currently testing Emulator locally on version 13.6.1 of Electron, and it seems to have fixed the issue. We will need to test all 3 platforms with a packaged version of the Emulator before a new release, but things look good for now.
I managed to implement a fix on a local build of the Emulator that enabled me to talk to a bot with a remote URL:
For now, I at least know that the method that I tried works, but I might have to take some more time to evaluate the fix and make sure that it is production ready.
I plan to have a new public build of the Emulator out by the end of the week with this fix, and I will update this thread if anything comes up.
Hey all,
Sorry for jumping into this so late. I just reproduced this locally trying to talk to a remote bot.
I will look into it this week and see if I can figure out what is causing the error. I think @stevkan is right in the sense that something in the ngrok service might have changed, because we haven’t changed any of this code in a very long time.
I have the same issue and report the same as all the above. Any resolution coming?