-
Notifications
You must be signed in to change notification settings - Fork 333
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
Bottender ngrok "ghost session" prevents tunnel from opening #997
Comments
Update: After some more poking around (and even hardwiring my ngrok token into the
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Hello,
I'm trying to get the Facebook Messenger channel set up by following the tutorial, but I'm having some trouble getting ngrok to work. I modified
dev.js
to print out the error object for more details:And this is the error I got:
(I'm on an M1 Mac running Monterey 12.6)
To Reproduce
Steps to reproduce the behavior:
npm run dev
Expected behavior
I expect
npm run dev
to successfully start ngrok.Additional context
It seems to me that the error code is either 103 (Account has been suspended) or 502 (limited to a certain number of max addresses), not sure which one it is.
I have ngrok installed via homebrew and when I run it with my access token it says I already have an ngrok session coming from my laptop's IP address. However, running
top | grep ngrok
orps aux | grep ngrok
reveals that there are no ngrok processes running. I even tried resetting my ngrok auth token and reauthenticating to prevent any old clients from connecting, but it still thinks I have this extra session.I even edited my
ngrok.yml
file to delete my authtoken, and the (homebrew) ngrok client connects just fine without an account. However, bottender still gives me the above error. Where is bottender is getting this mystery authtoken and where this "ghost" process coming from? I couldn't find angrok.yml
file inside my project (only the system-widengrok.yml
exists). I'm starting to wonder if there's a hardcoded API key in the library somewhere, but I know that's absurd.Does anyone know where this "ghost session" is coming from?
The text was updated successfully, but these errors were encountered: