Web Dashboard

HarborNode provides a local web dashboard for managing services and monitoring runtime state.

The dashboard runs on the port defined in your configuration:

listen_port = 3080

By default, access it at:

http://<your-ip>:3080

If running locally:

http://localhost:3080

If mDNS is available:

http://<hostname>.local:3080

Hosted portal (public UI):

https://harbor-node-ports.vercel.app/

Use the hosted portal only after configuring its API base URL to your live HarborNode backend.

Purpose

The web dashboard is the primary management interface for HarborNode.

It allows you to:

  • Register new services
  • View running services
  • Restart or stop services
  • Monitor runtime status
  • Inspect logs

The dashboard is designed for local or controlled environments.

Service Overview

The main view displays:

  • Registered services
  • Current process status
  • Uptime information
  • Port assignments
  • Restart state

Each service is supervised directly by HarborNode. If a service exits unexpectedly, HarborNode applies its restart policy.

Registering a Service

When adding a new service through the dashboard, you typically define:

  • Service name
  • Path to the binary
  • Working directory
  • Port (if required)
  • Restart behavior

HarborNode launches the binary as a host process and begins supervising it.

There is no container isolation. Services run directly on the host system.

Logs

The dashboard provides access to runtime logs for managed services.

For deeper debugging, use systemd logs:

journalctl -u harbornode -f

Restarting Services

Services can be restarted individually from the dashboard.

Restarting a service does not restart HarborNode itself.

To restart the entire runtime:

sudo systemctl restart harbornode

Security Considerations

The web dashboard does not implement built-in authentication by default.

If exposing HarborNode beyond localhost:

  • Use a reverse proxy
  • Enable HTTPS
  • Restrict access via firewall rules
  • Avoid exposing management ports directly to the public internet

HarborNode is intended for trusted environments.

Network Binding

HarborNode binds to the host network stack directly.

It does not create virtual networking layers or overlay networks.

Port conflicts must be avoided at the system level.

If HarborNode fails to start due to port conflicts, check:

ss -tuln | grep <port>

Future Improvements

Planned improvements may include:

  • Authentication support
  • Access control configuration
  • Improved logging visibility
  • Runtime metrics

The dashboard will evolve while keeping the runtime minimal.