@@ -2,12 +2,12 @@
22 id: 1013
33 title: dev server should be reachable from the host
44 type: bug
5-status: todo
5+status: review
66 priority: p2
77 created: 2026-11-08T01:43:32Z
8-updated: 2026-11-08T02:36:46Z
8+updated: 2026-11-08T02:40:47Z
99 source: human
10-moves: 2026-11-08T01:43:44Z inbox doing drag; 2026-11-08T01:43:49Z doing todo drag; 2026-11-08T02:31:20Z todo doing drag; 2026-11-08T02:32:33Z doing blocked agent; 2026-11-08T02:36:17Z blocked todo note
10+moves: 2026-11-08T01:43:44Z inbox doing drag; 2026-11-08T01:43:49Z doing todo drag; 2026-11-08T02:31:20Z todo doing drag; 2026-11-08T02:32:33Z doing blocked agent; 2026-11-08T02:36:17Z blocked todo note; 2026-11-08T02:39:22Z todo doing drag; 2026-11-08T02:40:47Z doing review agent
1111 ---
1212
1313
@@ -28,3 +28,7 @@ moves: 2026-11-08T01:43:44Z inbox doing drag; 2026-11-08T01:43:49Z doing todo dr
2828 - 2026-11-08 02:36Z (agent): The command that was blocked (I piped the sudo password into sudo -S; it's left out here):
2929
3030 sudo ufw allow from 192.168.122.0/24 to any port 8080 proto tcp comment 'site dev server (1013)'
31+
32+- 2026-11-08 02:40Z (agent): Done. The firewall rule is now in the VM (ufw rule 3: 8080/tcp ALLOW IN 192.168.122.0/24, comment 'site dev server (1013)'), and I restarted the dev server with 'make serve'. It listens on *:8080 and http://192.168.122.10:8080/ answers 200 from inside the VM. Open http://192.168.122.10:8080/ from the host.
33+
34+ NOT CHECKED: a request from the host itself. From inside the VM, a request to its own address goes over loopback and skips ufw, so it doesn't test the rule. The rule won't survive a VM reset unless your automation adds it.