Firewall/NGINX configuration on the server

[breezykermo]

Thanks so much for this wonderful tool, and for the excellent example of a simple and useful Rust codebase.

I'm not totally familiar with how tunnels work, and so it may be that this is an easy question to answer: but how does one set this up when using a firewall (UFW) and NGINX on the server-side? Do I need to expose just the control port in the NGINX configuration, or will there be issues when attempting to open a new tunnel?

Thanks again for the excellent software!

[ekzhang]

Hey Lachlan, bore assigns arbitrary ports in the range specified, from the configured min_port number (default 1024) to 65535. You would need to set your firewall to allow incoming TCP connections on those ports. You also need to enable the control port, which currently is fixed at 7835 and non-configurable.

bore is a standalone network service at the transport layer and doesn't conflict with or otherwise interact with nginx. You can run nginx and bore at the same computer together. For example, the public server instance at bore.pub has a quick nginx configuration set up that handles the 308 Permanent Redirect / -> https://github.com/ekzhang/bore response.

[breezykermo]

Apologies if this is not the appropriate place to ask for this configuration (feel free to close if this is not support you are interested in providing!); but I am still having trouble.

The following is my UFW status on a remote machine, and the server running on a process:

When I try to connect from a local terminal, I get the following:

Have I set this up incorrectly?

[ekzhang]

Hi Lachlan, I'm not an expert on UFW but a quick Google search shows that the syntax for allowing a port range is 1024:65535, not 1024,65535 as you've shown in your screenshot. Could you try allowing the full range of ports used by bore?

[breezykermo]

Wow, that was indeed it. Thank you for bearing with me, being network-illiterate! For those who have the same issue, the solution was to run this command on the server: sudo ufw allow proto tcp from any to any port 1024:65535