Frequently asked questions
Answers about private mesh connections, publishing services, DNS and the hosted network. For setup steps, see the guides.
How is noobtunnel different from Tailscale and Pangolin?
noobtunnel combines a private WireGuard mesh, public HTTP/S, TCP and UDP publishing, and domain management in one dashboard, with a network of POPs you can choose for publishing. Bring-your-own-domain DNS includes record management and Pro/Admin GeoDNS and load balancing.
There is overlap: Tailscale connects devices through a private mesh and also offers Serve and Funnel for sharing services. Pangolin provides identity-aware access to public and private resources through connectors and clients. noobtunnel is an independently developed project inspired by both, with its own routing and hosted-service allowances. It is not affiliated with either, and compatibility or matching features should not be assumed.
Compare the workflows you need using the Tailscale feature overview, Tailscale Funnel documentation and Pangolin resource documentation.
What DDoS protection does the network have?
We select POP hosting providers that advertise DDoS protection. That protection is supplied by the hosting provider, and its coverage, capacity and response depend on that provider's service. We do not independently guarantee their advertised protection or promise that every attack will be stopped.
Provider protection does not replace application security. An HTTP request flood, an expensive endpoint or an attack on your backend can still affect availability. noobtunnel also offers resource access controls and HTTP/S security settings, including bot checks and abuse-reputation blocking. These controls have different purposes from network-level DDoS mitigation.
Multiple POPs and health-based DNS routing help when a location becomes unavailable; they do not scrub attack traffic or make a service immune to DDoS attacks.
How reliable is the network, and what happens if a POP goes offline?
The hosted control service and its DNS run across multiple POPs with replicated configuration. The website at noobtunnel.top uses the shared control hostname, tunnel.byenoob.com, for Auto GeoDNS and HTTPS health checks. When a POP fails those checks, DNS selects the geographically nearest remaining healthy POP. If every checked POP is unavailable, DNS cannot provide a healthy route.
When a POP goes offline, affected single-POP tunnels automatically move to the next-closest healthy POP that can host them, then move back after their original POP recovers. Your backend must remain reachable. Allow time for health checks, reconnections and DNS updates; active connections may need to reconnect.
Multi-POP tunnels keep serving through their remaining healthy POPs, though connections using the failed POP may drop. Fixed IPs or manually managed DNS may need updating. If a backup needs a different public port, the dashboard shows the active address and port.
Are my published services redundant too?
A published resource normally listens through its primary exit POP. Admin and Pro accounts can select additional publishing POPs, running the same service at each public address and port. Your backend also needs to remain reachable.
Hosted DNS selects a healthy publishing POP and checks its listener and TCP backend reachability. DNS caches delay failover and existing connections are not transferred. UDP health checks confirm the listener and agent availability, not application responses. Manually managed domains need DNS records for the selected public addresses. Backend load balancing remains a separate feature.
Do I need port forwarding or a public IP at home?
Normally, no. The agent establishes an outbound connection, and a published resource accepts visitors at the POP before forwarding traffic to your agent and backend. This can work behind CGNAT. Our service hosting guide walks through installing an agent and publishing a test website. Your network still needs to allow the required outbound connections, and the configured backend must be reachable from the agent.
Direct mesh connections depend on NAT and firewall conditions. When a direct path cannot be established, traffic can use a POP relay.
Do visitors need to install an agent?
Visitors to a publicly published service do not need a noobtunnel agent. They use the service's public hostname or assigned port. Devices accessing your private mesh need an enrolled agent or a configured route into that mesh. Publishing a service makes it publicly reachable unless you apply access controls.
Can I use my own domain?
Yes. In Domains → BYOD, choose a delegated subdomain such as app.example.com or bring your whole domain. For a subdomain, add the assigned NS records at Cloudflare or your current DNS provider; your registrar nameservers and the rest of your domain stay unchanged. You can manage records at app.example.com and below it, including Pro/Admin GeoDNS and balancing. Delegated traffic does not use the parent zone's Cloudflare proxy protection.
Whole-domain setup changes registrar nameservers. Copy existing records for the zone, including mail records, before delegating. Hosted DNSSEC signing is not available, so do not publish a DS record for a delegated child zone.
Auto GeoDNS uses our iplog service to determine a country and selects the geographically nearest healthy configured address. When the resolver supplies a visitor subnet, DNS uses it; otherwise it uses the resolver's location. Unknown locations use the default balanced pool. Auto does not measure the fastest connection or create a public listener on another POP.
Is my traffic encrypted, and can the operator see it?
WireGuard protects mesh traffic between its tunnel endpoints. Public service publishing has a different trust boundary: HTTPS can terminate at the POP proxy, which handles the request before forwarding it to your backend. Backend encryption and authentication are separate settings. Do not assume a published service has one uninterrupted end-to-end HTTPS session.
The hosted service processes account information, connection metadata and operational logs. It is not a no-logs anonymity service. See Privacy & cookies for details.
What affects connection speed?
Your internet connection, backend performance, route, protocol and available shared POP capacity all affect speed. Direct mesh traffic takes a different path from relayed mesh traffic and published resources. Plan allowances apply to the relevant traffic path; an advertised maximum is not a dedicated or guaranteed connection speed. See Pricing for current allowances.
How do Pro subscriptions work?
Pro costs €1.99 per month. Open Settings → Plan & billing to subscribe through Stripe Checkout. Your plan activates after payment is verified. Manage billing lets you update your payment method, view invoices or cancel; scheduled cancellation keeps Pro until the end of your paid period. If payment cannot be renewed, Free allowances return without deleting your account or services.
How do I report a problem or abuse?
Sign in and create a ticket in the dashboard, or email admin@byenoob.com. Include the affected domain or resource, approximate time in UTC and the error you saw. For security or abuse reports, include enough detail to investigate safely. Do not send passwords, private keys or enrollment/API tokens. See Contact and the troubleshooting guide.