Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ngrok fails to spawn - no matter what (macOS) #2394

Closed
tbrodbeck opened this issue Aug 10, 2022 · 6 comments
Closed

Ngrok fails to spawn - no matter what (macOS) #2394

tbrodbeck opened this issue Aug 10, 2022 · 6 comments
Assignees
Labels
Bot Services equired for internal Azure reporting. Do not delete. Do not change color. Bug Your classic code defect customer-reported Required for internal Azure reporting. Do not delete.

Comments

@tbrodbeck
Copy link

tbrodbeck commented Aug 10, 2022

Version

Version 4.14.1 (4.14.1.277373)

Describe the bug

ngrok does not connect

To Reproduce

Example steps to reproduce the behavior:

  1. Open the Bot Framework Emulator bot endpoint configuration

Expected behavior

I would expect the ngrok connection to work.

Screenshots

Screen Shot 2022-08-10 at 19 16 38

Additional context

Path to ngrok on my system: /usr/local/bin/ngrok (installed with Homebrew)

ngrok version 3.0.6

macOS Version 12.5 (21G72)

Bot Emulator Settings:
Screen Shot 2022-08-10 at 19 23 38
I tried all kinds of settings, nothing makes ngrok connect to the Bot Emulator.

[bug]

@tbrodbeck tbrodbeck added the Bug Your classic code defect label Aug 10, 2022
@tbrodbeck tbrodbeck changed the title Ngrok fails to spawn - no matter what Ngrok fails to spawn - no matter what (macOS) Aug 10, 2022
@tbrodbeck
Copy link
Author

After hours of debugging I found a workaround. Using ngrok version 2: https://dl.equinox.io/ngrok/ngrok/stable/archive

@dmvtech
Copy link
Collaborator

dmvtech commented Aug 11, 2022

Possibly related to: #2389

@munozemilio munozemilio added customer-reported Required for internal Azure reporting. Do not delete. customer-replied-to Required for internal reporting. Do not delete. Bot Services equired for internal Azure reporting. Do not delete. Do not change color. and removed customer-replied-to Required for internal reporting. Do not delete. labels Aug 14, 2022
@axelsrz
Copy link
Member

axelsrz commented Aug 22, 2022

Closing due to issue fixed.

@axelsrz axelsrz closed this as completed Aug 22, 2022
@libardolara
Copy link

Was it fixed? I still gave the same issue. I see that #2389 is still open.

@anishprasad01
Copy link
Contributor

@libardolara

No, the issue with Ngrok 3 has not been fixed due to other priorities. For the time being, the workaround is to use Ngrok 2. I hope to have this fixed in the near future.

@anishprasad01
Copy link
Contributor

Should be fixed once #2399 is merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bot Services equired for internal Azure reporting. Do not delete. Do not change color. Bug Your classic code defect customer-reported Required for internal Azure reporting. Do not delete.
Projects
None yet
Development

No branches or pull requests

6 participants