3afba0d12d
### Fixing a bug - [x] Related issues linked using `fixes #number` - [x] Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - [x] Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md Closes NEXT- Fixes #55050 Co-authored-by: Steven <229881+styfle@users.noreply.github.com> Co-authored-by: Tim Neutkens <6324199+timneutkens@users.noreply.github.com>
27 lines
541 B
Text
27 lines
541 B
Text
---
|
|
title: Reserved Port
|
|
---
|
|
|
|
## Why This Error Occurred
|
|
|
|
Server was started on a reserved port. For example, `4045` is reserved for the Network Paging Protocol (npp).
|
|
|
|
```
|
|
next start -p 4045
|
|
```
|
|
|
|
or
|
|
|
|
```
|
|
next dev --port 4045
|
|
```
|
|
|
|
Starting the server on a reserved port will result in an error.
|
|
|
|
## Possible Ways to Fix It
|
|
|
|
Change the provided port to ensure it's not listed in the [Port Blocking](https://fetch.spec.whatwg.org/#port-blocking) section of WHATWG's fetch spec.
|
|
|
|
## Useful Links
|
|
|
|
- https://fetch.spec.whatwg.org/#port-blocking
|