Repository navigation
server.py: error: port 8080 is already in use #769
Description
Todays update... I checked and there is nothing using port 8080, was fine yesterday aswel
usage: server.py [-h] [--engine {mock,strata}] [--config CONFIG] [--host HOST]
[--script SCRIPT] [--port PORT] [--gpu GPU] [--tokenizer TOKENIZER] [--open]
[--fit-max-tokens] [--api-key API_KEY] [--mcp-config MCP_CONFIG] [--lazy]
[--api-monitor] [--idle-unload SECONDS]
[--min-free-vram-mib MIN_FREE_VRAM_MIB] [--before-load BEFORE_LOAD]
server.py: error: port 8080 is already in use - is Strata (or another server) already running? Close it, or start this one with a different --port
Press any key to continue . . .
even changing it with --port 8081 doesn't work
Activity
Guslletas commentedon Oct 5, 2026
Try with higher numbers, I had this issue and tried with ports in the 50000+ range and it worked. Asked AI and might be related to WSL2 and/or HyperV reserving a pretty big range of ports or something like that.
serve: vision temp files, Smart App Control message, engine start lin…
docs: TROUBLESHOOTING for Smart App Control, the port error, the engi…
Niko1221 commentedon Oct 6, 2026
A reserved port block (WSL2 / Hyper-V) is one known cause on Windows, as you suggest:
netsh int ipv4 show excludedportrange protocol=tcplists the blocks, and a --port outside them (50000+ usually is) works. Server-side, setup's start error names that command only for the 'access denied' form of the failure; whether the 'already in use' wording can come from a reserved block too is being checked. If a port outside the listed ranges also fails, please post whatnetstat -ano | findstr :8080shows.serve: vision temp files, Smart App Control message, engine start lin…
docs: TROUBLESHOOTING for Smart App Control, the port error, the engi…
serve: vision temp files, Smart App Control message, engine start lin…
docs: TROUBLESHOOTING for Smart App Control, the port error, the engi…
serve: vision temp files, Smart App Control message, engine start lin…
docs: TROUBLESHOOTING for Smart App Control, the port error, the engi…
Niko1221 commentedon Oct 13, 2026
Thanks for the report. To keep the tracker current we are closing issues older than three days: 0.1.44 is out with a long list of fixes, and many older reports are covered by it or by 0.1.43.1.
If this still happens on 0.1.44, please leave a comment here with your engine log (and the version line it prints), and we will reopen it. A new issue that links this one works too.