# Possible regression: dashboard across VLANs times out after 0.4.0 → 0.4.0.2; masquerade restores access
**URL:** https://community.start9.com/t/possible-regression-dashboard-across-vlans-times-out-after-0-4-0-0-4-0-2-masquerade-restores-access/5822
**Category:** StartOS Support
**Created:** [October 7, 2026, 6:36pm UTC](https://community.start9.com/t/possible-regression-dashboard-across-vlans-times-out-after-0-4-0-0-4-0-2-masquerade-restores-access/5822 "2026-10-07T18:36:38Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Catnip](https://community.start9.com/u/Catnip)
#### Post date: [October 7, 2026, 6:36pm UTC](https://community.start9.com/t/possible-regression-dashboard-across-vlans-times-out-after-0-4-0-0-4-0-2-masquerade-restores-access/5822/1 "2026-10-07T18:36:38Z")
After updating StartOS from **0.4.0 to 0.4.0.2** , I lost dashboard access from a Windows PC on another VLAN. The same PC and server IP worked before the update.
Network:
- Windows PC: **10.0.3.100**
- StartOS: **10.0.11.2** , on the Nodes VLAN ( **10.0.11.0/28** )
- Router: UniFi UCG Max
- Miners on the same VLAN as StartOS continued connecting successfully.
My existing firewall rule allows TCP **80 and 443** from `10.0.3.100` to `10.0.11.2`, with automatic return traffic enabled. UniFi recorded hits on this rule, and its gateway ping test received replies from StartOS.
Before the workaround, Windows `Test-NetConnection` reported `TcpTestSucceeded: False` on both 80 and 443. Browser access to `https://10.0.11.2/` timed out.
**Workaround:** Adding a UniFi masquerade rule with source `10.0.3.100`, destination `10.0.11.2`, and outbound interface **Nodes** restored dashboard access.
StartOS shows its local IP and `.local` HTTPS dashboard addresses enabled, with public dashboard access disabled.
The release notes mention changes for services accessed across routed private networks/VLANs. Could those changes have affected dashboard traffic or reply routing? Could my PC’s `10.0.3.100` address overlap StartOS’s internal container network?
I haven’t collected server routes or firewall rules, so the cause is unconfirmed. Is there a supported fix that removes the need for masquerade, and what diagnostics would help?
---
### Author:  [@George](https://community.start9.com/u/George)
#### Post date: [October 7, 2026, 9:45pm UTC](https://community.start9.com/t/possible-regression-dashboard-across-vlans-times-out-after-0-4-0-0-4-0-2-masquerade-restores-access/5822/2 "2026-10-07T21:45:47Z")
> [@Catnip](#):
>
> Could my PC’s `10.0.3.100` address overlap StartOS’s internal container network?
Absolutely. You will probably want to change the net on your PC’s network.
10.0.3.0/24 is the RFC1918 private network used by the services’ container bridge interface.