WSL: ngrok - consoleui failed: Failed to initialize terminal: invalid argument

Hi I’m trying to get ngrok working due to nodejs development and sharepoint online and webhooks. But it seems only to work on the CMD and not on the WSL. Is there any obvious that I need to do in order to run ngrok. It works very well in the commandline.

Cheers, Mario

  • Your Windows build number:
    Microsoft Windows [Version 10.0.15063] Ubuntu version 16.04.1 LTS

  • What you’re doing and what’s happening: ngrok http 3000 (installed via npm i -g ngrok)

  • What’s wrong / what should be happening instead: consoleui failed: Failed to initialize terminal: invalid argument

Expecting ngrok tunnel to be set up like it would in the CMD.

  • Strace of the failing command, if applicable: Multiple strace.txt so I’ve zipped them as a attachment. strace.zip

About this issue

  • Original URL
  • State: closed
  • Created 10 years ago
  • Reactions: 21
  • Comments: 29 (3 by maintainers)

Most upvoted comments

I had the same issue on WSL. Using ngrok’s --log option to write the log to stdout or stderr solved the problem for me. e.g. ngrok http 3000 --log stderr

I used the following options and I was able to see the public URL in the debug output, and it did in fact work. I was able to browse to it on my Android phone: --log "stdout" --log-level "debug"

I am facing the same issue on WSL with the same windows version - 10.0.1.15063. With WSL Ubuntu version 16.04.1 LTS

Decide to install the latest downloadable Insider Preview ISO on a virtual machine and test this for myself and it’s working 😃

image

Now I’m thinking on upgrading to Insider Preview on my main system, but afraid that it might not be very stable…

There have been changes in Insiders Build to address issues like signal-driven IO support for tty/pty (see therealkenc’s ref above) so it would be interesting to try this on a recent Insiders release. If there are still issues then we need to dig into the strace, et al. to see what is still blocking.

The --log work around works for me 😃

EDIT

Scrap that, --log removes the error and gives me sensible output but the tunnel does not start.

EDIT

--log does work, see below