Unable to access visualization page via browser

[darkSystemCode]

I configured sensing-server according to the introductory tutorial. The console output was successful, but I could not access the page normally. The page prompted 404. According to the program, the page showing 404 means that the program ran successfully, but the access resource could not be found. Why is this happening?

Here are the logs from my run:

sensing-server --source esp32 --udp-port 5005 --http-port 3000 --ws-port 3001

  2026-03-08T08:24:51.972987Z  INFO sensing_server: WiFi-DensePose Sensing Server (Rust + Axum + RuVector)
  2026-03-08T08:24:51.973099Z  INFO sensing_server:   HTTP:      http://localhost:3000
  2026-03-08T08:24:51.973168Z  INFO sensing_server:   WebSocket: ws://localhost:3001/ws/sensing
  2026-03-08T08:24:51.973275Z  INFO sensing_server:   UDP:       0.0.0.0:5005 (ESP32 CSI)
  2026-03-08T08:24:51.973341Z  INFO sensing_server:   UI path:   ../../ui
  2026-03-08T08:24:51.973402Z  INFO sensing_server:   Source:    esp32
  2026-03-08T08:24:51.973467Z  INFO sensing_server: Data source: esp32
  2026-03-08T08:24:51.973521Z  INFO sensing_server: Vital sign detector sample rate: 10.0 Hz
  2026-03-08T08:24:51.973814Z  INFO sensing_server: Discovered 0 model files, 0 recording files
  2026-03-08T08:24:51.975114Z  INFO sensing_server: UDP listening on 0.0.0.0:5005 for ESP32 CSI frames
  2026-03-08T08:24:51.975153Z  INFO sensing_server: WebSocket server listening on 127.0.0.1:3001
  2026-03-08T08:24:51.975456Z  INFO sensing_server: HTTP server listening on 127.0.0.1:3000
  2026-03-08T08:24:51.975514Z  INFO sensing_server: Open http://localhost:3000/ui/index.html in your browser

Page feedback information：

  Request URL:
  http://localhost:3000/ui/index.html
  Request Method:
  GET
  Status Code:
  404 Not Found
  Remote Address:
  127.0.0.1:3000
  Referrer Policy:
  strict-origin-when-cross-origin

What should I do? Or where did I configure it wrong?

[ruvnet]

Fix your networking.

[darkSystemCode]

Fix your networking.

Is this the host network where I run sensing-server? My host network is good, but I use a VPN proxy network, does this have an impact?

[ruvnet]

UI Path Issue

The log shows UI path: ../../ui which is a relative path that doesn't exist when running the compiled binary from a different location.

Quick Fix

When running from the source directory, specify the absolute UI path:

sensing-server --source esp32 --udp-port 5005 --http-port 3000 --ws-port 3001 \
  --ui-path /full/path/to/RuView/ui

Where is the UI?

The UI files are in the repository at:

• ui/index.html (main entry point)
• ui/js/, ui/css/ (assets)

Running from source

If you built from source, run from the workspace root:

cd rust-port/wifi-densepose-rs
cargo run --release -p wifi-densepose-sensing-server -- \
  --source esp32 --ui-path ../../ui --http-port 3000 --ws-port 3001

Using Docker (recommended)

Docker has the correct paths baked in:

docker run -p 3000:3000 -p 3001:3001 -p 5005:5005/udp \
  -e CSI_SOURCE=esp32 \
  ruvnet/wifi-densepose:latest

Then open: http://localhost:3000/ui/index.html

Verify UI files exist

ls -la ui/
# Should show index.html, js/, css/, etc.

If the ui/ folder is missing, you may need to clone the full repository or download the UI assets separately.

[ruvnet]

If you're running the Docker container and can't access the visualization page, make sure you're mapping the correct ports:

ports:
  - "3000:3000"    # HTTP + WebSocket (sensing server)
  - "5005:5005/udp" # ESP32 CSI data ingestion

Then access http://<your-host-ip>:3000 in a browser. If running remotely, use the server's IP, not localhost.

Also see #228 for a similar remote access setup discussion.

[julien-ft-64]

In docker container, the UI doesn't work, websocket issue as it require a secure websocket

[szy833]

I've encountered the same problem. How can I solve and troubleshoot it?

[darkSystemCode]

I've encountered the same problem. How can I solve and troubleshoot it?

The author has already provided a solution; see the comments for details.

[ruvnet]

The UI runs at http://localhost:8080/ui/index.html (not port 3030). Start the server with: cd rust-port/wifi-densepose-rs && RUST_LOG=info cargo run --release -p wifi-densepose-sensing-server -- --source esp32. v0.5.3 includes major UI improvements including client-side lerp smoothing.

[dblues0925]

I configured sensing-server according to the introductory tutorial. The console output was successful, but I could not access the page normally. The page prompted 404. According to the program, the page showing 404 means that the program ran successfully, but the access resource could not be found. Why is this happening?

Here are the logs from my run:

sensing-server --source esp32 --udp-port 5005 --http-port 3000 --ws-port 3001

  2026-03-08T08:24:51.972987Z  INFO sensing_server: WiFi-DensePose Sensing Server (Rust + Axum + RuVector)
  2026-03-08T08:24:51.973099Z  INFO sensing_server:   HTTP:      http://localhost:3000
  2026-03-08T08:24:51.973168Z  INFO sensing_server:   WebSocket: ws://localhost:3001/ws/sensing
  2026-03-08T08:24:51.973275Z  INFO sensing_server:   UDP:       0.0.0.0:5005 (ESP32 CSI)
  2026-03-08T08:24:51.973341Z  INFO sensing_server:   UI path:   ../../ui
  2026-03-08T08:24:51.973402Z  INFO sensing_server:   Source:    esp32
  2026-03-08T08:24:51.973467Z  INFO sensing_server: Data source: esp32
  2026-03-08T08:24:51.973521Z  INFO sensing_server: Vital sign detector sample rate: 10.0 Hz
  2026-03-08T08:24:51.973814Z  INFO sensing_server: Discovered 0 model files, 0 recording files
  2026-03-08T08:24:51.975114Z  INFO sensing_server: UDP listening on 0.0.0.0:5005 for ESP32 CSI frames
  2026-03-08T08:24:51.975153Z  INFO sensing_server: WebSocket server listening on 127.0.0.1:3001
  2026-03-08T08:24:51.975456Z  INFO sensing_server: HTTP server listening on 127.0.0.1:3000
  2026-03-08T08:24:51.975514Z  INFO sensing_server: Open http://localhost:3000/ui/index.html in your browser

Page feedback information：

Request URL:
http://localhost:3000/ui/index.html
Request Method:
GET
Status Code:
404 Not Found
Remote Address:
127.0.0.1:3000
Referrer Policy:
strict-origin-when-cross-origin
What should I do? Or where did I configure it wrong?

I encountered an issue where I couldn't access port 3000 in my environment: Windows + WSL + Ubuntu + v0.5.3-esp32 + Docker Compose.
Root Cause:
The Rust HTTP server (e.g., Axum, Hyper) defaults to binding to 127.0.0.1 when no bind address is specified. This prevents external access even with proper Docker port mapping.
Solution:
Add the SENSING_BIND_ADDR environment variable to your Docker Compose service configuration, binding it to 0.0.0.0

[ruvnet]

Alternative visualization available in v0.5.5

While the HTTP 404 issue for the built-in web UI is still open, v0.5.5 provides a terminal-based RF scanner with real-time spectrum visualization:

# Live RF room scan with ASCII spectrum display
node scripts/rf-scan.js --port 5006 --duration 30

This shows: subcarrier amplitudes, null zones (metal objects), dynamic movement, cross-node correlation, vitals, and RSSI — all in the terminal. No web server needed.

If you have a Cognitum Seed, its built-in API Explorer at https://169.254.42.1:8443/ provides a full web dashboard.

See v0.5.5 release for all new visualization tools.