You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems like there's an issue with the api responses when using an auth token.
I've tested the setup once with and once without an config file, and if the auth is in the config file, the api response returns empty.
The issue doesnt exist when using the non-docker version of ngrok.
Steps to reproduce:
Seems like there's an issue with the api responses when using an auth token.
I've tested the setup once with and once without an config file, and if the auth is in the config file, the api response returns empty.
The issue doesnt exist when using the non-docker version of ngrok.
Steps to reproduce:
docker run --rm -it -p 4040:4040 -v ${HOME}/.ngrok2/ngrok.yml:/ngrok_auth.yml:ro --name www_ngrok wernight/ngrok ngrok http -config=/ngrok_auth.yml 3000
curl $(docker port www_ngrok 4040)/api/tunnels
Expected:
To have a response with the tunnel listed
Actual result:
curl: (52) Empty reply from server
The text was updated successfully, but these errors were encountered: