Windows and WSL
On Windows, Buggregator runs three ways: as a Windows program, in Docker Desktop, or inside WSL. Pick the one that sits next to your app. Then your app reaches it as 127.0.0.1 or by a service name, with no network tricks.
| Your app runs… | Run Buggregator… | Your app sends to |
|---|---|---|
| on Windows (e.g. PHP from Laragon, Node, .NET) | as a Windows program | 127.0.0.1 |
| in Docker Desktop (compose, Sail) | as a compose service | the service name, e.g. buggregator |
| inside WSL (Ubuntu and others) | inside WSL, the Linux binary | 127.0.0.1 |
In every case you open the UI in your Windows browser at http://localhost:8000.
As a Windows program
In PowerShell, install a fixed version:
$env:BUGGREGATOR_VERSION = "v2.11.0"
irm https://raw.githubusercontent.com/buggregator/server/master/scripts/install.ps1 | iex
& "$env:LOCALAPPDATA\Programs\buggregator\buggregator.exe"Or download buggregator-windows-amd64.exe (ARM: buggregator-windows-arm64.exe) from the v2.11.0 release. If Windows says «Windows protected your PC», see Install → If your system blocks it.
In Docker Desktop
Add the service to your compose.yaml or docker-compose.yml:
services:
buggregator:
image: ghcr.io/buggregator/server:2.11.0
ports:
- "127.0.0.1:8000:8000"Containers in the same compose file reach it as buggregator. Stack guides: Laravel Sail, Symfony, Django, Node.js, Spring Boot.
A container that must reach a Buggregator running as a Windows program uses host.docker.internal instead of 127.0.0.1, e.g. MAIL_HOST=host.docker.internal. Windows Firewall must let buggregator.exe in: allow it when Windows asks on the first start. If you clicked «Cancel», containers cannot reach it.
Inside WSL
Open your WSL terminal and install the Linux binary there:
curl -fsSL https://raw.githubusercontent.com/buggregator/server/master/scripts/install.sh \
| BUGGREGATOR_VERSION=v2.11.0 sh
~/.local/bin/buggregatorYour app inside WSL sends to 127.0.0.1. WSL 2 forwards localhost ports to Windows, so the Windows browser opens the UI at http://localhost:8000.
Do not mix: a Windows program on one side and the app inside WSL on the other is harder to connect. Run one copy, next to the app.
Check it
curl http://127.0.0.1:8000/api/version
# {"version":"2.11.0"}In PowerShell, use curl.exe instead of curl. Then send something from your app; the stack guides say what you should see.