Troubleshooting

• Wait 90 seconds after powering on — the Pi takes time to boot
• Make sure your device is on the same WiFi network as the Pi (or connected via ethernet to the same router)
• Try the Pi's IP address directly — find it in your router's device list, then visit http://192.168.x.x:8080
• On Windows, .local addresses sometimes don't work — use the IP address instead
• Check the Pi has power (the green LED should be lit)
• If the Pi is connected via the Neto-Setup hotspot, make sure you're connected to that hotspot, not your normal WiFi

The default credentials are admin / admin. If you changed them during setup and can't remember them, there is currently no password reset — contact support at support@neto.network.

Tests run every 5 minutes. If you just completed setup, wait up to 5 minutes and reload the page. You can also click ▶ Run now in the top-right corner to trigger an immediate test.

• Check that your WiFi credentials are correct in Settings — a typo in the SSID or password means Neto can't connect and tests fail silently
• Make sure the SSID you entered matches exactly, including capitalisation
• Check Settings → WiFi and re-enter your credentials, then click Run now

• Wrong SSID — the 5 GHz SSID is often different from 2.4 GHz (e.g. MyNetwork_5G). Check your router's admin page or the label on the back of your router
• Not configured — if the 5 GHz SSID field is blank in Settings, that band won't be tested. Enter the SSID and save
• Pi too far from router — 5 GHz has shorter range. Move the Pi closer to the router and try again
• Router doesn't broadcast 5 GHz — older routers may be 2.4 GHz only. Check your router's specs

• Check if your other devices can access the internet — if they can't either, it's a router or ISP issue, not a Neto issue
• If other devices are fine but Neto's gateway ping is failing, the WiFi password may be wrong — double-check in Settings
• Very high gateway ping (over 100 ms) that isn't reflected on other devices may indicate WiFi interference — check the Spectrum analyser
• Try clicking Run now and watching the Logs page to see what's happening in real time

This is a known behaviour when both ethernet and WiFi are connected to the Pi. The external ping uses the WiFi route preference set by Neto, but occasionally the kernel routes the response back via ethernet, causing the test to fail.

• Unplug the ethernet cable — Neto works perfectly on WiFi only and this eliminates the routing conflict
• Or change the external ping target in Settings to a different IP like 1.1.1.1

This is usually normal — Neto measures real-world WiFi throughput, not the theoretical maximum of your internet plan. Several factors affect this:

• WiFi overhead — WiFi is typically 50–70% efficient. A 100 Mbps plan often delivers 50–70 Mbps over WiFi
• Distance from router — the further the Pi is from the router, the lower the WiFi signal and speed
• 2.4 GHz vs 5 GHz — 2.4 GHz is slower but has better range. 5 GHz is faster but shorter range. Compare both bands on the dashboard
• Interference — channel congestion from neighbouring networks reduces throughput. Check the Spectrum analyser
• Time of day — ISP congestion during peak hours (6–10 pm) commonly reduces speeds. Check the Graphs page for patterns

Speedtest results can be blank if:

• Speedtest is disabled in Settings — check the Speedtest toggle
• The speedtest server couldn't be reached during that test cycle — usually a temporary internet issue
• The test timed out — can happen on very slow connections. Try disabling speedtest and re-enabling it, then click Run now

The spectrum scan runs at the start of each test cycle. If you've just set up Neto, click ▶ Run now and then refresh the Spectrum page after about 30 seconds.

If it remains empty after a run, the WiFi scan may be failing. This can happen if:

• The Pi's WiFi adapter doesn't support passive scanning — uncommon on Pi 3/4/5 but possible with some USB adapters
• The iw tool isn't installed — this is installed by default with Neto but may be missing on a custom setup