BryanNet

Cloudflare Tunnel for web access (not router API)

Prerequisites and authority

Local installation authority, a complete approved release package, working Docker and access to the deployment record are required. Preserve existing data before installation/update/removal.

Use a stable tunnel for web access

This guide describes an optional Cloudflare deployment. BryanNet is provider-neutral: an existing reverse proxy, another persistent HTTPS tunnel or an organization's hosted ingress may meet the same application requirements. Do not migrate a working ingress merely to follow this example. Responsibility and support boundaries are described in LAN access, firewall, DNS and HTTPS.

An HTTPS tunnel can expose selected BryanNet web routes from a local host without forwarding inbound web ports at the internet gateway. It does not create the API-to-MikroTik management path.

Use a persistent production tunnel with stable hostnames for customer access or payment callbacks. Temporary Quick Tunnel addresses are suitable for development and can change; do not configure production provider callbacks against them.

  1. Prepare the domain, tunnel account and intended hostnames.
  2. Map each required hostname to its correct local application origin.
  3. Keep administrator access private or protect it with an access policy appropriate to staff.
  4. Ensure payment callbacks remain reachable by the provider and are verified by the application's provider-authentication mechanism. Interactive login walls can prevent delivery.
  5. Update API/admin/customer public URLs and confirm generated links.
  6. Test from an external connection, then submit one sandbox payment.
  7. Restart the host and verify the tunnel service reconnects.

A working public admin page cannot demonstrate that router management is healthy. Routers need LAN reachability or a routed VPN. If router scripts send events back to BryanNet, test that reverse application path as well.

Do not put API secrets in tunnel URLs. Protect credentials for the tunnel and retain the configuration in the deployment recovery record. Exact tunnel installation commands are provider-specific and should be linked to the provider's maintained instructions.

Related guides

Related guides: First-deployment walkthrough and success checklist, Deployment verification and first login, Back up BryanNet and validate backups, Restore BryanNet safely, Product updates, compatibility and rollback.