Localhost:1203/proktor ((full)) Online

# config.yaml port: 1203 base_path: /proktor # optional – change if you need a different prefix log_level: info auth: api_key: "CHANGE_ME_12345" jwt_secret: "super‑secret‑jwt-key" storage: type: file # could be `sqlite`, `postgres`, `redis` path: ./data/proktor.db plugins_dir: ./plugins

Add --watch (Node) or --reload (Python) for hot‑reloading during development.

When you see "localhost" in a web address, it means the software is running directly on your own computer or a local server rather than on the public internet. Refers to the local machine. localhost:1203/proktor

| Symptom | Likely cause | Fix | |---------|--------------|-----| | when opening the UI | Server not started or bound to another interface. | Run proktor start (or docker ps to see the container). Ensure port: 1203 in config. | | 404 on /proktor/api/v1/jobs | Wrong base path or API version mismatch. | Verify base_path in config.yaml . Use /proktor/api/v1/... exactly. | | Job stuck in “queued” | No worker loaded for the job’s type . | Check GET /proktor/api/v1/workers . Ensure your plugin is correctly named and implements run . | | Auth errors (401/403) | API‑Key missing or wrong. | Add header X-Api-Key: <key> or a valid JWT. | | Large file uploads fail | Default body size limit (1 MB). | Increase server.max_body_size in config.yaml (e.g., 10mb ). | | Database lock errors (SQLite) | Multiple concurrent writes. | Switch to postgres or redis storage, or enable sqlite.wal: true . |

// Simulate connection metrics data const connectionMetrics = latency: 50, packetLoss: 0.5, jitter: 10, connectionSpeed: 1000 ; # config

To ensure a smooth testing experience, supervisors should follow these steps:

But what exactly is “Proktor”? Why would it run on localhost:1203 ? And should you consider deploying it for your organization? Let’s break it down. | Symptom | Likely cause | Fix |

// API Endpoints app.get('/connection/metrics', (req, res) => res.json(connectionMetrics); );

Change the port in settings or close conflicting background apps. Technical Best Practices for Exam Supervisors