ca.srl stays root-owned after a privileged proxy start
#578
A replay after a reset on a pooled socket can land on another reset socket and return a 502
#576
After an early answer to an upload, the next request on the same HTTP/1.1 connection gets no answer
#573
Proposal: trust the CA on a phone by scanning a QR code (`portless trust --device`)
#564
--unprivileged --https proxy comes back as plain HTTP after it stops
1
#535
proxy status --json, for launchers that share a proxy
#534
A route keeps serving after its owner is killed
#533
Concurrent starts can get the same app port; a child that survives EADDRINUSE leaves its route pointing at another app
2
#531
502s with an empty error message on page loads: the proxy opens one uncapped upstream socket per request, and a busy backend's listen queue (128 on macOS) resets the rest
1
#526
`portless trust` asks for authorization again when the CA is already trusted
#523
Feature request: a hook for the proxy's own pages (404, 502, 508)
#522
Community tools section in the README?
#521
proxy start -p starts an untracked second proxy and overwrites proxy.pid, so proxy stop kills the wrong one
#519
portless mcp advertises 2025-03-26 but never answers a JSON-RPC batch
#482
Plain HTTP mode (--no-tls) forwards the backend's `Connection: close`, so clients never reuse connections
#469
HTTPS under Bun: nested hosts get the *.localhost cert because Bun ignores SNICallback
1
#459
Proposal: appPortStrategy and appPortRange, so an app's port can be stable or sequential instead of random
#457
Proposal: let portless.json pin the proxy settings, so one file configures the proxy for every checkout
#436
App startup retries proxy on occupied Portless port and times out
#433
feat: add an optional Vite plugin for Portless-aware startup URLs
#418
TLS SNI accepts arbitrary hostnames and performs unbounded certificate generation
#415
Feature Request: Look Up a Route’s Port
1
#408
Inject Portless URLs into environment variables
#399
Allow non-LAN proxy binding for Docker host-gateway clients
#393
service install pins the absolute node path, so removing that node version disables the proxy at the next boot