-
Notifications
You must be signed in to change notification settings - Fork 143
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
Specifying hostname to forward request #6
Comments
May be you'd like to start a WiKi page? I've enabled it. |
I got the same error, i changed the command from the example to the below: docker run --rm -d -p 4040 --link www:http --name www_ngrok wernight/ngrok ngrok http http:80 |
@bkuhl could you explain a little more on the following based on your solution? env_file: .env |
NGROK_LOOK_DOMAIN should be what is used for this, but it doesn't work. Currently, using the workaround @bkuhl provided is working.
|
@madebylee Basically that's saying to read environment variables from |
@bkuhl , should we use .env here ? or is it ok not to have ?, if ever what's inside in the .env ? Thank you in advance ngrok: |
@ezekel You should be able to use the |
@bkuhl , I rebuild my docker , my question after I rebuild is there a command to run so that it will expose now to internet ? |
Ok I will rebuild again. thank you fro the quick reply |
@bkuhl, I'm done rebuilding my docker, what command to run for ngrok ? Thank you in advance |
@bkuhl by the way is this will work in my local I used host in windows. then I access my app like this myapp.local, is this will work in ngrok too ? |
@wernight , can I ask please what command I will run so that it will generate ngrok url Thank you in advance |
I was experiencing an issue where ngrok could not access localhost:80. It looked like ngrok was trying to take an external request into the docker container and fowarding it to
localhost:80
which it couldn't find.Here's an example of my not functional config:
The solution was to tell it to forward incoming requests to
web:80
and not alias theweb
container. Port80
was the internal port that myweb
container was listening for, not the one that is publicly exposed. I was able to achieve this with the following configuration:In this case I happened to resolve the issue but wanted to post it here in case it was helpful to someone else.
The text was updated successfully, but these errors were encountered: