mirror of
https://github.com/LukeHagar/vercel.git
synced 2025-12-06 12:57:46 +00:00
56c8af51b2
We renamed the GitHub repository from `zeit/now` to `vercel/vercel` so this PR updates all references to the repo URL. There were also a few remaining references to Now CLI that have been updated to Vercel CLI.
37 lines
1.2 KiB
Markdown
37 lines
1.2 KiB
Markdown
# `@vercel/static-build` Failed to detect a server running
|
|
|
|
#### Why This Warning Occurred
|
|
|
|
When running `vercel dev`, the `@vercel/static-build` builder proxies relevant HTTP
|
|
requests to the server that is created by the `dev` script in the
|
|
`package.json` file.
|
|
|
|
In order for `vercel dev` to know which port the server is running on, the builder
|
|
is provided a `$PORT` environment variable that the server _must_ bind to. The
|
|
error "Failed to detect a server running on port" is printed if the builder fails
|
|
to detect a server listening on that specific port within five minutes.
|
|
|
|
#### Possible Ways to Fix It
|
|
|
|
Please ensure that your `dev` script binds the spawned development server on
|
|
the provided `$PORT` that the builder expects the server to bind to.
|
|
|
|
For example, if you are using Gatsby, your `dev` script must use the `-p`
|
|
(port) option to bind to the `$PORT` specified from the builder:
|
|
|
|
> _In Windows environments, reference the `PORT` environment variable with `%PORT%`_
|
|
|
|
```
|
|
{
|
|
...
|
|
"scripts": {
|
|
...
|
|
"dev": "gatsby develop -p $PORT"
|
|
}
|
|
}
|
|
```
|
|
|
|
Consult your static builder program's `--help` or documentation to figure out what
|
|
the command line flag to bind to a specific port is (in many cases, it is one of:
|
|
`-p` / `-P` / `--port`).
|