-
-
Notifications
You must be signed in to change notification settings - Fork 331
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
docker-compose.yml #110
Comments
Instead of rebuild the image you guys can try to use the command settings, it work perfect for me
|
Awesome, this way it is even simpler to use. Thanks! Just this line:
needs to change to something like this:
in order to get a predictable port for the proxy, that will than be mapped to the public HTTPS port 443. I still continue to use the self building script, because the machine I'm using it on has an ARM CPU. |
I am confused a little bit with the network part. What do I need to have for the network? Error that I got: |
The See this for details: https://nginxproxymanager.com/advanced-config/#best-practice-use-a-docker-network |
https://github.com/ricardoapaes/bore-server I implemented this solution using nginx, then take a look. |
I made your great tool work on a https://github.com/NginxProxyManager/nginx-proxy-manager driven virtual server. Maybe you'd like to add some of the following to your project:
ENTRYPOINT ["./bore", "server", "--min-port=8080", "--max-port=8080"]
docker-compose.yml
and build and start it likedocker compose up -d
The
networks
line are specific to the proxy.The port is required to get the protocol working.
In the proxy I configured like this:
Now with something like
bore local 8080 --to tunnel.example.com
I can fire it up on the client. HTTPS also works fine if configured in the Nginx Proxy Manager.The text was updated successfully, but these errors were encountered: