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

Outdated ngrok.exe version causing connection failure #327

Open
andrew-braun opened this issue Feb 12, 2025 · 0 comments
Open

Outdated ngrok.exe version causing connection failure #327

andrew-braun opened this issue Feb 12, 2025 · 0 comments

Comments

@andrew-braun
Copy link

andrew-braun commented Feb 12, 2025

I've been starting up tunnels in my node app for a few years with this package, but this morning I got an error out of nowhere. Apparently, the version of ngrok that this package is using is 3.3.0, but ngrok now requires that we use at least 3.6.0.

data:  t=2025-02-12T14:13:13+0400 
lvl=eror msg="session closing" 
obj=tunnels.session 
err="authentication failed: Your ngrok-agent version \"3.3.0\" is too old. The minimum supported agent version for your account is \"3.6.0\". Please update to a newer version with `ngrok update`, by downloading from https://ngrok.com/download, or by updating your SDK version. Paid accounts are currently excluded from minimum agent version requirements. To begin handling traffic immediately without updating your agent, upgrade to a paid plan: https://dashboard.ngrok.com/billing/subscription.

I tried replacing the ngrok.exe in node_modules/ngrok/bin and it worked perfectly. For better future-proofing, I didn't use that as my main solution and instead used the binPath property in ngrok.connect to point to a copy of the executable in a bin folder in my project, like so:

ngrok.connect({
            addr: <addr>,
            proto: 'http',
            authtoken: NGROK_AUTH_TOKEN,
            schemes: ['https'],
            binPath: (path) => (path = './bin')
        });

It looks like the package hasn't been updated for a while, but, unless I'm missing something obvious, this seems like a fairly simple update. Happy to open a PR for it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant