A connection needs an address, a port, and a route
Networking connects devices and services across a network. The address identifies the destination, while the port identifies the service at that destination. A web server might accept HTTPS on port 443, while SSH for server administration commonly uses port 22.
An address alone is not enough. There must be a usable route between your device and the destination. Routers forward the traffic, and firewall rules determine which connections may pass. The service must also listen on a reachable address and the expected port.
Working on the server does not prove access from your laptop
An application can work on the server itself yet time out when you open it from a laptop. It may listen only on localhost, the laptop may have no route into the private network, or a rule may block the port.
Start troubleshooting with specific questions: Which device sends the request? Which destination address and port does it use? Is that destination reachable from this network? These checks help narrow down a connection problem before you change application code.
A tunnel provides a particular route
In this example, the server at 10.0.1.20 sits behind the company firewall. MainPath needs SSH for setup and deployments. When public SSH is unavailable, you can create a tunnel and assign it to the server. Supported options include a jump host, reverse SSH, WireGuard, and OpenVPN.
With WireGuard or OpenVPN, MainPath joins your existing network as a client. You enter the server’s internal address as its host. Without an assigned tunnel, MainPath continues to use direct public SSH. See Network tunnels for the setup steps.
That management route does not determine how users open your application. HTTP and HTTPS must still be reachable if you serve a public website. A tunnel connection also does not replace signing in and checking permissions within the application.
Workspaces have a separate private network
Access to a workspace VM requires Tailscale, including when you use its apps in a browser. This private network is separate from server tunnels. Tailscale for workspaces explains the setup; Servers covers the available server options.