Frequently Asked Question
Container Station says a port is already in use. Which port should I change?
QUICK ANSWER
A published port belongs to the NAS host side of the mapping. Two services cannot normally bind the same host address, port and protocol at once. The application’s internal container port may remain unchanged.
Applies to: Container Station with Docker-style published ports; host and bridged networking behave differently.
Work through these checks
- Read the deployment error and record the host port, protocol and selected network mode. Check existing containers and NAS applications for an intentional use of that port. Do not stop an unrelated production service.
- Compare host and container fields in the port mapping. For example, an app listening internally on 80 can be published on a different unused host port; changing only the internal value can make the app unreachable.
- Assign a deliberately chosen free host port and update the corresponding shortcut or reverse-proxy destination. Review the app’s own documented port requirements rather than changing several numbers at random.
- Start only the affected container and test it from the intended local network. Review firewall scope and host bindings; publishing a service is not permission to forward it through the internet router.
Confirm the result
The container starts without the bind error and its application responds at the intended address while existing NAS services still work.
Before going further: Do not turn on privileged mode or delete container volumes to fix a port collision. Save the deployment configuration and persistent data first.
If you need help
Include these details in your ticket: Container Station version, image/tag, network mode, redacted port mappings and exact bind error.
Updated 261107