Network general
Everyday home network problems at Sunbury — getting online, finding devices on 192.168.2.0/24, and understanding why CGNAT means no port forwarding. Start here when something "just won't connect."
Home network map
flowchart TD
NBN[NBN modem] --> UDM[UniFi Dream Machine SE]
UDM --> AP[U7 access points Wi‑Fi]
UDM --> NAS[TrueNAS 192.168.2.203]
UDM --> PC[Windows PC 192.168.2.200]
NAS --> TUN[cloudflared to Cloudflare]| If this fails… | It is probably… | Also check |
|---|---|---|
| Everything offline | WAN / NBN / UDM power | PWR-*, When internet is broken |
| Wi‑Fi only | AP or signal | UNI-* |
| NAS IP unreachable | LAN cable, NAS power, pool | NAS-*, Outage runbook |
| Public URLs only | Tunnel / Cloudflare | TUN-* — not NET-* first |
A: drive missing |
SMB / credentials | Windows shares, NET-004 |
Integrated runbooks: Symptom finder · Outage runbook · Network
42 entries — IDs NET-001 through NET-042.
NET-001: Nothing on Wi‑Fi or ethernet can reach the internet
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: The NBN link, UniFi Dream Machine SE, or a power outage upstream has dropped the whole house connection. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Phones, the Windows PC, and smart devices all show "No internet" or pages never load. Likely cause: The NBN link, UniFi Dream Machine SE, or a power outage upstream has dropped the whole house connection. Fix: 1. Check whether the Dream Machine SE has power and normal lights (not all dark). 2. Check the NBN box lights — confirm it is powered on. 3. Wait five minutes after any power blip, then try opening google.com on a phone. 4. If still down, power-cycle in order: NBN box off 30 seconds, then Dream Machine off 30 seconds, then turn both back on and wait five minutes.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Follow When internet is broken or see Common Issues. Deep dive: When internet is broken
NET-002: Only one device has no internet — everything else works
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: That single device lost its Wi‑Fi connection, has aeroplane mode on, or needs a quick restart. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Your phone or laptop cannot browse, but another device on the same Wi‑Fi works fine. Likely cause: That single device lost its Wi‑Fi connection, has aeroplane mode on, or needs a quick restart. Fix: 1. Confirm aeroplane mode is off and Wi‑Fi is on. 2. Turn Wi‑Fi off, wait ten seconds, turn it back on, and rejoin the home network. 3. If it still fails, restart the device completely. 4. As a last step, "Forget" the Wi‑Fi network and rejoin using the password from Vaultwarden.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See UniFi Wi‑Fi basics. Deep dive: When internet is broken
NET-003: I can browse the web but cannot open dsm.saxobroko.com or 192.168.2.203
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: TrueNAS is off, asleep, or its fixed IP 192.168.2.203 changed after a router reboot.
Diagnose (2 min):
1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook.
2. Check Service matrix for which app/host owns the broken URL.
3. If a single device only, retry from a second device on the same network.
Symptoms: Google and email work, but the TrueNAS web page or NAS address does not load on the LAN.
Likely cause: TrueNAS is off, asleep, or its fixed IP 192.168.2.203 changed after a router reboot.
Fix:
1. Walk to the NAS and confirm it is powered on with normal drive lights.
2. On the Windows PC, open a browser and try https://192.168.2.203 directly.
3. If that fails, open the UniFi app and check whether TrueNAS appears online with IP 192.168.2.203.
4. If the IP is wrong, set a fixed IP reservation for TrueNAS in UniFi (see UNI-020).
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See TrueNAS basics or Common Issues. Deep dive: When internet is broken
NET-004: Windows PC cannot see the A: drive (media share)
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: The PC lost its connection to TrueNAS at 192.168.2.203, or TrueNAS is offline.
Diagnose (2 min):
1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook.
2. Check Service matrix for which app/host owns the broken URL.
3. If a single device only, retry from a second device on the same network.
Symptoms: File Explorer shows an error when opening drive A:, or the mapped network drive has a red X.
Likely cause: The PC lost its connection to TrueNAS at 192.168.2.203, or TrueNAS is offline.
Fix:
1. Confirm TrueNAS is on — try https://192.168.2.203 in a browser.
2. On the Windows PC, open File Explorer, right-click the A: drive, and choose Reconnect.
3. If prompted, enter the share username and password from Vaultwarden.
4. If it still fails, restart the PC and try again.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See Windows shares or Windows PC basics. Deep dive: When internet is broken
NET-005: Two devices seem to fight over the same IP address
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Two devices were manually given the same IP (for example both set to 192.168.2.203), or a fixed IP was assigned twice.
Diagnose (2 min):
1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook.
2. Check Service matrix for which app/host owns the broken URL.
3. If a single device only, retry from a second device on the same network.
Symptoms: One device works, then another stops; UniFi may show an IP conflict warning.
Likely cause: Two devices were manually given the same IP (for example both set to 192.168.2.203), or a fixed IP was assigned twice.
Fix:
1. Open UniFi → Clients and look for a conflict or duplicate IP warning.
2. Make sure only TrueNAS uses 192.168.2.203 and only the Windows PC uses 192.168.2.200.
3. Remove any manual static IP on the device itself unless Saxon documented it — let UniFi assign fixed IPs instead.
4. Restart the affected devices one at a time.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See UniFi fixed IPs (UNI-020) or Network. Deep dive: When internet is broken
NET-006: My phone shows connected to Wi‑Fi but has no internet
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: The phone joined Wi‑Fi but the router lost WAN internet, or the phone has a stale connection. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Wi‑Fi icon is full bars, but apps say offline or pages spin forever. Likely cause: The phone joined Wi‑Fi but the router lost WAN internet, or the phone has a stale connection. Fix: 1. Turn Wi‑Fi off and back on on the phone. 2. Test whether another device on the same Wi‑Fi can reach google.com. 3. If nothing works house-wide, check the Dream Machine and NBN box (see NET-001). 4. If only the phone fails, forget the network and rejoin.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See When internet is broken. Deep dive: When internet is broken
NET-007: Ethernet works on the Windows PC but Wi‑Fi is slow or drops
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Wi‑Fi signal is weak in that room, or an access point is offline — not a general internet fault. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: The PC on a cable is fast and stable; phones and laptops on Wi‑Fi buffer or disconnect. Likely cause: Wi‑Fi signal is weak in that room, or an access point is offline — not a general internet fault. Fix: 1. Stand near a U7 access point and test speed again. 2. Open UniFi → Devices and confirm both U7 APs show Connected. 3. Restart the affected phone or laptop Wi‑Fi. 4. If one AP shows offline, check its PoE cable and power (see UNI-015).
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See UniFi Wi‑Fi or UniFi basics. Deep dive: When internet is broken
NET-008: Wi‑Fi works but the Windows PC on ethernet cannot get online
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Bad ethernet cable, wrong port, or the PC's network adapter needs a reset. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Phones browse fine; the PC wired to the switch or router shows no internet. Likely cause: Bad ethernet cable, wrong port, or the PC's network adapter needs a reset. Fix: 1. Confirm the ethernet cable clicks firmly into both the PC and the wall port or switch. 2. Try a different cable if one is available. 3. On Windows, open Settings → Network → Ethernet and confirm it says Connected. 4. Restart the PC.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See Windows PC basics. Deep dive: When internet is broken
NET-009: I cannot ping 192.168.2.203 from my laptop
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: TrueNAS is off, your device is on the wrong network, or a firewall on the NAS is blocking ping (ping failure alone does not always mean the NAS is dead). Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: A "Request timed out" or "Host unreachable" message when trying to reach the NAS by IP.
Likely cause: TrueNAS is off, your device is on the wrong network, or a firewall on the NAS is blocking ping (ping failure alone does not always mean the NAS is dead).
Fix:
1. Confirm you are on the home Wi‑Fi — not mobile data or a guest network.
2. Check that TrueNAS is powered on.
3. Open a browser and try https://192.168.2.203 — that is a better test than ping for beginners.
4. If the browser loads, the NAS is fine even if ping fails.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See TrueNAS basics. Deep dive: When internet is broken
NET-010: Device got an IP like 169.254.x.x instead of 192.168.2.x
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: The device could not reach the Dream Machine DHCP server — often after waking from sleep or a bad cable. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Network settings show a "self-assigned" or 169.254 address; nothing on the LAN works from that device.
Likely cause: The device could not reach the Dream Machine DHCP server — often after waking from sleep or a bad cable.
Fix:
1. Confirm you are connected to the home Wi‑Fi or a working ethernet port.
2. Restart the device.
3. On Windows, open Command Prompt and run ipconfig /renew (or restart).
4. If it persists, restart the Dream Machine SE and wait five minutes.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See When internet is broken. Deep dive: When internet is broken
NET-011: Everything on the LAN feels slow — copying files takes forever
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Wi‑Fi congestion, a device on 2.4 GHz far from an AP, or TrueNAS disks under heavy load — not necessarily NBN speed. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Large file copies to the NAS crawl; Jellyfin on LAN stutters even though internet speed tests look fine.
Likely cause: Wi‑Fi congestion, a device on 2.4 GHz far from an AP, or TrueNAS disks under heavy load — not necessarily NBN speed.
Fix:
1. Move closer to a U7 access point or plug into ethernet for a speed test copy.
2. Pause active downloads or torrents on the Windows PC.
3. Check TrueNAS is not running a heavy scrub — see the TrueNAS UI at 192.168.2.203.
4. Restart the slow device’s Wi‑Fi connection.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See Common Issues or Pool scrub guide. Deep dive: When internet is broken
NET-012: I am on mobile data and homelab sites show 403 Forbidden
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: block no aus — homelab URLs are intentionally blocked outside Australia. This is not a home LAN problem. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: stream.saxobroko.com, dash.saxobroko.com, or similar return a Cloudflare block page while travelling overseas.
Likely cause: block no aus — homelab URLs are intentionally blocked outside Australia. This is not a home LAN problem.
Fix:
1. Understand this is expected behaviour when not in Australia.
2. Use services that are meant to be public (docs.saxobroko.com, status.saxobroko.com) if you need access abroad.
3. Do not change WAF rules unless Saxon or a trusted admin authorises it.
4. When back in Australia, test again without VPN.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See WAF rules or Cloudflare edge (CFL-003). Deep dive: When internet is broken
NET-013: Sites work at home on Wi‑Fi but not on 4G/5G outside
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Homelab apps require the Cloudflare tunnel and Australian geo rules — or you are outside AU where block no aus applies. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Jellyfin and dash load on home Wi‑Fi; on phone data away from home they fail or show 403.
Likely cause: Homelab apps require the Cloudflare tunnel and Australian geo rules — or you are outside AU where block no aus applies.
Fix:
1. Confirm you are in Australia when testing homelab URLs.
2. Check status.saxobroko.com on mobile data — if that loads, the internet path is fine.
3. If only homelab URLs fail abroad, that is by design (see NET-012).
4. At home on Wi‑Fi, if they fail, check the tunnel (see Cloudflare tunnel).
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See Network. Deep dive: When internet is broken
NET-014: What is CGNAT and why can't we port-forward?
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: The ISP puts the house on CGNAT — the router never gets a real public IP it can forward to. That is why Saxon uses Cloudflare Tunnels instead. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: You read about "opening ports" online but nothing works; router port-forward settings have no effect on saxobroko.com services.
Likely cause: The ISP puts the house on CGNAT — the router never gets a real public IP it can forward to. That is why Saxon uses Cloudflare Tunnels instead.
Fix:
1. Do not waste time on WAN port forwarding for homelab apps — it will not work on this connection.
2. External access goes through cloudflared on TrueNAS — see cloudflared.
3. LAN access still uses normal IPs like 192.168.2.203.
4. For new public sites, add a tunnel hostname — not a port forward.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See What is Cloudflare. Deep dive: When internet is broken
NET-015: LAN works but every *.saxobroko.com site is down at once
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: The Cloudflare tunnel (cloudflared) stopped on TrueNAS, or Cloudflare had an edge outage — not the UniFi router.
Diagnose (2 min):
1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook.
2. Check Service matrix for which app/host owns the broken URL.
3. If a single device only, retry from a second device on the same network.
Symptoms: stream, dash, vault, and dsm all fail from outside the house (or even inside), but 192.168.2.203 may still work locally.
Likely cause: The Cloudflare tunnel (cloudflared) stopped on TrueNAS, or Cloudflare had an edge outage — not the UniFi router.
Fix:
1. On the LAN, open https://192.168.2.203 and confirm TrueNAS is up.
2. Check status.saxobroko.com — if many services show down, suspect the tunnel.
3. Restart cloudflared on TrueNAS — Restart cloudflared.
4. Wait two minutes and retry one URL like stream.saxobroko.com.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See Cloudflare tunnel (TUN-001). Deep dive: When internet is broken
NET-016: docs.saxobroko.com works but stream.saxobroko.com does not
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: SaxDocs is on Cloudflare Pages (no tunnel). Jellyfin and others need cloudflared on TrueNAS — different paths. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: SaxDocs loads (after login), but media and dashboard URLs fail.
Likely cause: SaxDocs is on Cloudflare Pages (no tunnel). Jellyfin and others need cloudflared on TrueNAS — different paths.
Fix:
1. Confirm whether https://192.168.2.203 works on the LAN — that tests TrueNAS, not Pages.
2. If LAN works but public URLs fail, restart cloudflared.
3. Do not assume fixing DNS for docs fixes stream — check the tunnel separately.
4. See Network URL list.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See cloudflared. Deep dive: When internet is broken
NET-017: I typed 192.168.1.1 but nothing loads — wrong address?
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Saxon's LAN uses 192.168.2.0/24, not 192.168.1.x. The Dream Machine is typically 192.168.2.1.
Diagnose (2 min):
1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook.
2. Check Service matrix for which app/host owns the broken URL.
3. If a single device only, retry from a second device on the same network.
Symptoms: Browser times out on 192.168.1.1; tutorials online assume that IP for "the router."
Likely cause: Saxon's LAN uses 192.168.2.0/24, not 192.168.1.x. The Dream Machine is typically 192.168.2.1.
Fix:
1. Try https://192.168.2.1 instead for the UniFi router page.
2. Use https://192.168.2.203 for TrueNAS.
3. Use 192.168.2.200 as the Windows PC's usual address.
4. Log in with credentials from Vaultwarden.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See Home network simple. Deep dive: When internet is broken
NET-018: New device cannot get an IP on the network
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: DHCP pool full (rare), wrong Wi‑Fi password, or guest network isolation blocking LAN access. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: A smart plug, TV, or guest phone connects to Wi‑Fi but shows no IP or "limited connectivity."
Likely cause: DHCP pool full (rare), wrong Wi‑Fi password, or guest network isolation blocking LAN access.
Fix:
1. Confirm the correct Wi‑Fi password from Vaultwarden.
2. Join the main household SSID, not guest, if the device needs NAS access.
3. Restart the Dream Machine SE if many devices fail at once.
4. In UniFi, check Clients to see if the device appears with a 192.168.2.x address.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See UniFi Wi‑Fi (UNI-001). Deep dive: When internet is broken
NET-019: After a power outage the whole network is weird
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Equipment booted in the wrong order or DHCP leases were lost during the outage. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Some devices online, some not; NAS or PC has wrong IP; tunnels down.
Likely cause: Equipment booted in the wrong order or DHCP leases were lost during the outage.
Fix:
1. Wait five minutes after power returns — NBN and router need time.
2. Confirm boot order: NBN box first, then Dream Machine, then TrueNAS and PC.
3. Check TrueNAS is at 192.168.2.203 and PC at 192.168.2.200 in UniFi.
4. Restart cloudflared once TrueNAS is fully up.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See Power outage recovery. Deep dive: When internet is broken
NET-020: How do I know if the problem is NBN vs my homelab?
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Multiple layers — a quick test order saves guesswork. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: You are not sure whether to blame the ISP, UniFi, TrueNAS, or Cloudflare.
Likely cause: Multiple layers — a quick test order saves guesswork.
Fix:
1. Test google.com on home Wi‑Fi — if it fails, start with NET-001 (internet down).
2. If google works, test 192.168.2.203 — if that fails, TrueNAS or LAN (NET-003).
3. If LAN works, test status.saxobroko.com on mobile data — Cloudflare/public path.
4. If status works but stream.saxobroko.com fails, check tunnel (TUN-001).
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See Check status page. Deep dive: When internet is broken
NET-021: VPN on my phone breaks access to 192.168.2.x addresses
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: The VPN sends all traffic elsewhere, so your phone is no longer "on" the home LAN logically. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: With a VPN enabled, the NAS UI or local apps no longer load.
Likely cause: The VPN sends all traffic elsewhere, so your phone is no longer "on" the home LAN logically.
Fix:
1. Turn the VPN off when at home and you need local NAS access.
2. Use public URLs (dsm.saxobroko.com) through the tunnel instead if you must keep VPN on.
3. Some VPN apps have "local network bypass" — enable it if available.
4. Reconnect to home Wi‑Fi after changing VPN settings.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See Network. Deep dive: When internet is broken
NET-022: Smart TV cannot reach Jellyfin on the LAN
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: TV is on guest Wi‑Fi, wrong subnet, or the Jellyfin app needs the public URL even at home. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: TV apps cannot find the server; browser on TV fails for local IP.
Likely cause: TV is on guest Wi‑Fi, wrong subnet, or the Jellyfin app needs the public URL even at home.
Fix:
1. Confirm the TV is on the main home Wi‑Fi, not guest.
2. In the Jellyfin app, try server URL https://stream.saxobroko.com (works via tunnel even at home).
3. Alternatively use http://192.168.2.203:8096 if Saxon documented the LAN port — check Services.
4. Restart the TV's network settings.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See Jellyfin for beginners. Deep dive: When internet is broken
NET-023: Duplicate Wi‑Fi names — which network is the real one?
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Neighbour's SSID, old router still broadcasting, or UniFi 2.4/5 GHz names split vs combined. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Two similar network names appear; unsure which is Saxon's UniFi network. Likely cause: Neighbour's SSID, old router still broadcasting, or UniFi 2.4/5 GHz names split vs combined. Fix: 1. Check Vaultwarden for the exact SSID name and password. 2. Ask UniFi admin (or check UniFi app) for the official network name. 3. Do not join unknown open networks pretending to be home Wi‑Fi. 4. Forget wrong networks on your device after joining the correct one.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See UniFi Wi‑Fi basics. Deep dive: When internet is broken
NET-024: Windows says Unidentified Network on ethernet
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Windows did not get DHCP from the Dream Machine, or the adapter driver glitched. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: PC connects by cable but Windows treats the network as public/unidentified and blocks some apps.
Likely cause: Windows did not get DHCP from the Dream Machine, or the adapter driver glitched.
Fix:
1. Unplug and replug the ethernet cable.
2. Run ipconfig /renew in Command Prompt as administrator.
3. Restart the PC.
4. Confirm the PC gets 192.168.2.200 (or another 192.168.2.x address) in ipconfig.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See Windows PC basics. Deep dive: When internet is broken
NET-025: Can I use 192.168.2.203 in the browser without HTTPS?
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: TrueNAS prefers HTTPS on the LAN; plain HTTP may redirect or warn. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: http://192.168.2.203 shows a certificate warning or redirects oddly.
Likely cause: TrueNAS prefers HTTPS on the LAN; plain HTTP may redirect or warn.
Fix:
1. Use https://192.168.2.203 in the address bar.
2. Accept the local certificate warning if the browser asks — you are on your own LAN.
3. For the public URL use https://dsm.saxobroko.com (through Cloudflare tunnel).
4. Do not disable HTTPS unless Saxon documented a specific exception.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See TrueNAS basics. Deep dive: When internet is broken
NET-026: Phone switches between Wi‑Fi and mobile data and apps break
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Weak Wi‑Fi at the edge of coverage causes the phone to hop networks mid-session. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Streaming or login apps fail when walking around; connection flickers between Wi‑Fi and 4G. Likely cause: Weak Wi‑Fi at the edge of coverage causes the phone to hop networks mid-session. Fix: 1. Move closer to a U7 access point while using heavy apps. 2. Temporarily disable mobile data to force Wi‑Fi only while testing. 3. Forget and rejoin Wi‑Fi if the phone keeps a bad association. 4. For homelab URLs, wait until on stable Wi‑Fi or strong mobile data in Australia.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See UniFi Wi‑Fi (UNI-025). Deep dive: When internet is broken
NET-027: Neighbour's Wi‑Fi seems stronger than ours
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Normal RF environment — placement of U7 APs and home layout matter, not ISP speed. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Your device tries to join a nearby network or signal is weak in some rooms. Likely cause: Normal RF environment — placement of U7 APs and home layout matter, not ISP speed. Fix: 1. Confirm you are connected to the home SSID from Vaultwarden. 2. Note which rooms are weak — report to Saxon for AP placement review (do not move APs unless trained). 3. Use ethernet on the Windows PC for heavy tasks. 4. Check both U7 APs are online in UniFi.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See UniFi. Deep dive: When internet is broken
NET-028: I changed something and now nothing on 192.168.2.x talks
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Subnet mask, gateway, or IP range was changed away from 192.168.2.0/24.
Diagnose (2 min):
1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook.
2. Check Service matrix for which app/host owns the broken URL.
3. If a single device only, retry from a second device on the same network.
Symptoms: After editing router or NAS settings, printers, shares, and apps all fail together.
Likely cause: Subnet mask, gateway, or IP range was changed away from 192.168.2.0/24.
Fix:
1. Stop making further changes.
2. Open UniFi and confirm LAN is still 192.168.2.1/24 (gateway .1, subnet 255.255.255.0).
3. Confirm TrueNAS and PC fixed IPs are still .203 and .200.
4. Reboot Dream Machine and TrueNAS if settings were wrong and have been corrected.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Contact Saxon or follow Handover first 24 hours. Deep dive: When internet is broken
NET-029: Browser says DNS_PROBE_FINISHED_NXDOMAIN for saxobroko.com
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: DNS problem — either your device's DNS, home router DNS, or Cloudflare DNS records — not LAN cabling. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Any *.saxobroko.com name does not resolve — "server not found" before a page loads.
Likely cause: DNS problem — either your device's DNS, home router DNS, or Cloudflare DNS records — not LAN cabling.
Fix:
1. Test on mobile data vs home Wi‑Fi to see if it is local or global.
2. Try https://1.1.1.1 in the browser to check basic internet.
3. If all subdomains fail everywhere, see DNS & domains (DNS-001).
4. If only one subdomain fails, see DNS-015.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See What is DNS. Deep dive: When internet is broken
NET-030: Internet works but DNS feels slow — pages delay before loading
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Router or device using a slow DNS server, or ISP DNS hiccup — unrelated to TrueNAS. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Long pause before sites start loading; then they open normally.
Likely cause: Router or device using a slow DNS server, or ISP DNS hiccup — unrelated to TrueNAS.
Fix:
1. Restart the Dream Machine SE.
2. Restart the affected device.
3. In UniFi, confirm DNS is set to reliable forwarders (often 1.1.1.1 or ISP auto).
4. Test again after five minutes.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See DNS & domains (DNS-010). Deep dive: When internet is broken
NET-031: Gaming on the Windows PC lags but speed test is fine
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Wi‑Fi on another device, background torrents on the PC, or ISP routing — not NAS-related. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: High ping in games; downloads speed test normal on 192.168.2.200.
Likely cause: Wi‑Fi on another device, background torrents on the PC, or ISP routing — not NAS-related.
Fix:
1. Pause qBittorrent and large downloads on the PC — see qBittorrent guide.
2. Use ethernet for gaming if possible.
3. Check no one is streaming 4K Jellyfin transcoding heavily on the NAS.
4. Test at a quiet time to rule out household congestion.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See PC specs. Deep dive: When internet is broken
NET-032: How do I reach the router admin page safely?
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Admin UI is on the LAN only at the gateway IP — typically 192.168.2.1.
Diagnose (2 min):
1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook.
2. Check Service matrix for which app/host owns the broken URL.
3. If a single device only, retry from a second device on the same network.
Symptoms: You need UniFi settings but do not know the address or login.
Likely cause: Admin UI is on the LAN only at the gateway IP — typically 192.168.2.1.
Fix:
1. Connect to home Wi‑Fi or ethernet — not mobile data.
2. Open the UniFi Network phone app, or browse to https://192.168.2.1.
3. Log in with UniFi admin credentials from Vaultwarden.
4. Do not expose UniFi admin to the public internet.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See UniFi or UniFi Wi‑Fi (UNI-005). Deep dive: When internet is broken
NET-033: TrueNAS responds on LAN but SMB share password fails
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Wrong username/password — not a network outage. Credentials live in Vaultwarden. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: 192.168.2.203 loads in browser; Windows A: drive asks for password and rejects it.
Likely cause: Wrong username/password — not a network outage. Credentials live in Vaultwarden.
Fix:
1. Open Vaultwarden (vault.saxobroko.com) and find the TrueNAS or SMB share login.
2. Re-enter credentials carefully — watch Caps Lock.
3. Try mapping the share again from File Explorer.
4. Confirm the share user is still enabled on TrueNAS (ask Saxon if unsure).
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See Windows shares. Deep dive: When internet is broken
NET-034: Device shows wrong hostname in UniFi client list
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: DHCP hostname from manufacturer — compare MAC address and IP to known devices. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Unknown name appears online; unsure if it is the NAS, PC, or a stranger.
Likely cause: DHCP hostname from manufacturer — compare MAC address and IP to known devices.
Fix:
1. Match IP to known list: TrueNAS .203, Windows PC .200, gateway .1.
2. In UniFi, click the client and note MAC — compare to device label or Saxon's notes.
3. Rename the client in UniFi for clarity (cosmetic only).
4. If truly unknown, change Wi‑Fi password only after Saxon approves — could be a neighbour.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See Physical equipment map. Deep dive: When internet is broken
NET-035: IPv6 works but IPv4 homelab addresses fail (or the reverse)
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Mixed IPv4/IPv6 path — homelab LAN is IPv4 (192.168.2.0/24) for practical purposes.
Diagnose (2 min):
1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook.
2. Check Service matrix for which app/host owns the broken URL.
3. If a single device only, retry from a second device on the same network.
Symptoms: Some sites load over IPv6; 192.168.2.x or legacy apps break.
Likely cause: Mixed IPv4/IPv6 path — homelab LAN is IPv4 (192.168.2.0/24) for practical purposes.
Fix:
1. Use explicit IPv4 addresses (192.168.2.203) for NAS and PC tests.
2. Do not disable IPv6 unless Saxon documented a reason — usually unnecessary.
3. For public URLs, use normal https:// hostnames, not raw IPs.
4. Focus troubleshooting on IPv4 LAN first.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See Network. Deep dive: When internet is broken
NET-036: Printer or IoT device needs LAN access but cannot see NAS
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Device is on guest or IoT VLAN/SSID with isolation from main LAN. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Smart home gear works for internet but cannot reach local servers.
Likely cause: Device is on guest or IoT VLAN/SSID with isolation from main LAN.
Fix:
1. Check which Wi‑Fi network the device joined — main vs guest.
2. Move it to the main SSID if Saxon said it needs local access.
3. If isolation is intentional, do not bypass without Saxon — security trade-off.
4. Confirm device has a 192.168.2.x address in UniFi.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See UniFi Wi‑Fi (UNI-030). Deep dive: When internet is broken
NET-037: Thunderstorm / NBN maintenance — should I unplug everything?
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Power surges can damage gear — brief outages usually need only patience, not full shutdown. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Weather alert or ISP SMS; unsure whether to shut down NAS and router. Likely cause: Power surges can damage gear — brief outages usually need only patience, not full shutdown. Fix: 1. For brief storms, a normal UPS (if installed) handles flickers — see power FAQ when available. 2. After outage, follow Power outage recovery. 3. Do not repeatedly power-cycle TrueNAS — wait between attempts. 4. Check ISP status page on mobile data if NBN is down for hours.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See Turn everything on. Deep dive: When internet is broken
NET-038: Laptop works at a café but not at home
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Home-specific — wrong password, DNS, proxy settings, or UniFi issue — not the laptop hardware. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Same laptop browses on public Wi‑Fi; at Sunbury home Wi‑Fi it fails or is very slow. Likely cause: Home-specific — wrong password, DNS, proxy settings, or UniFi issue — not the laptop hardware. Fix: 1. Forget home Wi‑Fi and rejoin with Vaultwarden password. 2. Disable VPN and proxy temporarily. 3. Compare with another device on the same home Wi‑Fi (NET-002). 4. Check UniFi for client blocked or restricted (rare).
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See When internet is broken. Deep dive: When internet is broken
NET-039: What does 192.168.2.0/24 mean in plain English?
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: It is the "address neighbourhood" for all home devices — from .1 (router) up to .254.
Diagnose (2 min):
1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook.
2. Check Service matrix for which app/host owns the broken URL.
3. If a single device only, retry from a second device on the same network.
Symptoms: Documentation mentions 192.168.2.0/24 and it makes no sense.
Likely cause: It is the "address neighbourhood" for all home devices — from .1 (router) up to .254.
Fix:
1. Remember: router ≈ 192.168.2.1, NAS = 192.168.2.203, PC = 192.168.2.200.
2. Any device on home Wi‑Fi should get a 192.168.2.x address when healthy.
3. If you see a different prefix (like 192.168.1.x), something is wrong (NET-017).
4. Read Home network simple for a gentle overview.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See Glossary. Deep dive: When internet is broken
NET-040: status.saxobroko.com shows services down — is the LAN dead?
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: Status is an external monitor — it can show tunnel or app failures even when home Wi‑Fi still browses google.com. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Status page lists red/down for Jellyfin, tunnel, or NAS checks.
Likely cause: Status is an external monitor — it can show tunnel or app failures even when home Wi‑Fi still browses google.com.
Fix:
1. Check home internet with google.com on Wi‑Fi (NET-001 if that fails).
2. Open https://192.168.2.203 on LAN — if that fails, TrueNAS is the issue.
3. If LAN works but status is red, restart cloudflared and check Monitoring.
4. Use status as a hint, not the only test.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See Check status page. Deep dive: When internet is broken
NET-041: I need to wire a new device — which port on the Dream Machine?
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: UDM SE has LAN ports for internal devices and a separate WAN port for NBN — plugging into WAN by mistake breaks things. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: New PC or switch needs ethernet; unsure which physical port to use on the UDM SE.
Likely cause: UDM SE has LAN ports for internal devices and a separate WAN port for NBN — plugging into WAN by mistake breaks things.
Fix:
1. Connect home devices to LAN ports (usually numbered), not the WAN/Internet port.
2. WAN port should only go to the NBN box or modem.
3. Wait 30 seconds and confirm link lights on both ends.
4. Check UniFi shows the client online with a 192.168.2.x IP.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See Physical equipment map. Deep dive: When internet is broken
NET-042: Everything checks out but I am still stuck — who do I call?
Stack context: LAN · UniFi · CGNAT · 192.168.2.0/24
Integrated runbooks: Symptom finder · Outage runbook · Network
Why this happens: May need Saxon, ISP support, or professional help — knowing which saves time. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: You followed FAQs and guides; problem persists and you are not comfortable changing more. Likely cause: May need Saxon, ISP support, or professional help — knowing which saves time. Fix: 1. Write down what works (google? LAN IP? one URL?) and what fails — use NET-020 order. 2. If no internet at all after power cycle, call ISP/NBN support. 3. If internet OK but homelab down, check Handover contacts and Common Issues. 4. Do not wipe TrueNAS, delete Cloudflare DNS, or factory-reset the Dream Machine without explicit instructions.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? See FAQ overview and search (Ctrl+K) for your symptom. Deep dive: When internet is broken