domino-debug-proxy

/domino-debug-proxy Command

Diagnose and fix common Domino proxy and routing issues for web applications.

Usage

/domino-debug-proxy

What This Command Checks

1. Port Configuration

• Verifies port 8888 is used
• Checks for hardcoded ports in config files
• Validates strictPort settings

2. Base Path Configuration

• For React/Vite: Checks base: './' in vite.config.js
• For other frameworks: Checks relative path usage

3. Host Binding

• Verifies host: '0.0.0.0' (not localhost or 127.0.0.1)
• Checks server configuration in all frameworks

4. app.sh Analysis

• Checks for correct working directory
• Verifies build commands
• Validates serve configuration

5. Asset Loading

• Checks for hardcoded absolute paths
• Verifies relative asset references

Common Issues Detected

Issue: Wrong Port

Symptom: App shows "Connection refused"

Detection:

❌ Found port 3000 in vite.config.js
   Expected: 8888

Fix:

server: {
  port: 8888,
  strictPort: true
}

Issue: Absolute Base Path

Symptom: 404 errors on CSS/JS files

Detection:

❌ vite.config.js has base: '/' or no base specified
   This causes asset 404s behind Domino proxy

Fix:

export default defineConfig({
  base: './',
  // ...
})

Issue: Localhost Binding

Symptom: App not accessible from browser

Detection:

❌ Server bound to localhost/127.0.0.1
   Domino proxy cannot reach the app

Fix:

server: {
  host: '0.0.0.0',
  // ...
}

Issue: Missing SPA Fallback

Symptom: Direct URL access returns 404

Detection:

❌ app.sh uses 'npx serve dist' without -s flag
   Client-side routing will fail

Fix:

npx serve -s dist -l 8888

Issue: Build Not Running

Symptom: Blank page or old content

Detection:

❌ app.sh missing 'npm run build' step
   App may be serving stale or no content

Fix:

#!/bin/bash
set -e
cd /mnt/code
npm ci
npm run build  # Add this line
npx serve -s dist -l 8888