Network diagnostics hub

NAS & Home Server Remote Access Checker

Describe your remote-access setup and 17NAS combines its existing diagnostics layer by layer to show where access most likely breaks: public internet, DNS, port reachability, or HTTPS / reverse proxy.

Only the checks you choose are run. Nothing is stored, and your WAN address is compared locally without ever being connected to.

NAS & Home Server Remote Access Checker

For example: nas.example.com. Hostnames only — no URLs, paths, or ports.
For example: 443 or 5001. This checks one TCP port on the public IP of your current connection — it does not scan the hostname.
The IPv4 shown on your router's Internet / WAN status page. It is parsed and compared locally in your browser and never connected to.

All three fields are optional — each one you fill runs that layer of the check.

Checks that will run
  • Fill in any field to enable its check layer.

The HTTPS check connects from the 17NAS server to the public hostname you enter (handshake and response headers only). No network test runs until you press the button.

Ready

Recommended detailed tools

The hub is a summary only. Use the full tools to go deeper. NAT type and IPv6 tests are never run automatically.

How the remote access check works

Remote access breaks down into four layers: public internet (whether you have an inbound-capable public IPv4), name resolution (whether DNS points to your current network), port reachability (whether the TCP port answers from the internet), and application edge (whether HTTPS / TLS / the reverse proxy work). This page maps the fields you fill to those layers, runs 17NAS's existing diagnostics per layer, and synthesizes a cautious conclusion from the evidence. Each layer has a dedicated full tool for deeper investigation.

Why "everything is configured but it still fails"

Remote NAS access needs every layer to hold: correct DNS, an inbound-capable public IPv4, effective port forwarding, a listening service, and a healthy reverse proxy with a valid certificate. Any broken layer looks almost the same from the outside. Layer-by-layer isolation beats trial and error — confirm where DNS points, then port reachability, then HTTPS / the proxy, to narrow the problem fastest.

What each layer answers

The public-internet layer answers "do I have an inbound-capable public IPv4" (CGNAT check); name resolution answers "does my hostname point to my current network" (DNS / DDNS check); port reachability answers "is the TCP port reachable from the internet" (open port check); the application edge answers "are HTTPS / TLS / the reverse proxy healthy" (HTTPS check). NAT type and IPv6 are complementary dimensions — run those tools manually when needed.

What to check next

Isolate by layer: fix DNS pointing with the DNS / DDNS Checker, confirm CGNAT status and consider IPv6 or relays when the public layer fails, verify forwarding with the Open Port Checker and Port Forwarding Helper, and inspect certificates and 502 / 504 details with the HTTPS Checker.