Because Replit runs your projects on a cloud environment, ports work differently on Replit than on your local computer. (If you need a more basic explanation of what TCP ports are, start here.) On a computer, you only have one layer of port management: your programs define a port that they listen to, and when traffic hits that port on your computer from the internet, they get routed to the appropriate process.
computer
The 0.0.0.0 part is the address, or host. If a process is listening on 0.0.0.0, that means it should listen on every network interface — which means that if another computer (on the internet) sends a request to your computer’s IP address, it will see it. So, listening on 0.0.0.0 means those processes are accessible to the public internet (if your computer is connected.) Most programming frameworks will not listen on 0.0.0.0 when you’re developing, because you don’t necessarily want your work exposed to the public while you’re working on it, for privacy & security. Instead, they’ll listen on a different address — 127.0.0.1, otherwise known as localhost. This means only that computer can make requests to that port.
Localhost ports are only visible on the computer that is hosting them.
On Replit, for a process you’re running to be accessible in the webview or via an external request, it has to have an external port defined. This is because the “internal port” that processes typically use is only visible from inside the sandboxed cloud environment that Replit provides. We have to connect that internal port to an externally accessible port to send the right traffic to your programs. Even if your process listens on a port typically available to the public like 0.0.0.0, we still need to bind that port to an external port.
External ports forward traffic to internal ports, which programs listen to.
We do this by binding external ports to specific internal ports — for example, in the diagram above, the external port :80 is bound to the internal port :3000. That means any traffic that Replit App gets on port 80 will go to the internal port 3000. This configuration is captured in the [[ports]] section of the .replit config file. By default, we will bind the first port you open to the default external port 80, which will allow that process to be available at the domain without a port address (e.g. customdomain.com/ instead of customdomain.com:3000/). Additional internal ports that are opened will be bound to other available external ports (see a full list below.)

​
Preview

In the Preview tool, you can change which external port the webview is rendering by clicking the domain and selecting a different port. You can also open the networking tool from the “gear” icon for more details.
Clicking the domain in the webview will let you choose what port to view.

​
Default port

Port :80 is the “default port” for http traffic, so http traffic sent to the root domain will automatically be routed to port 80. We don’t show the port path in the url for port 80 for that reason. Ports other than :80 will show up in the domain path (e.g. customdomain.com:4200/). (We provide TLS by default, so it will technically be over port 443, which is the default port for https. For all intents and purposes, you can treat them as interchangeable.)

​
Networking tool

For more details about port config and networking, you can open the networking tool. It shows the status of ports open in your Replit App, what external port they’re bound to, and lets you add or remove configuration.
The networking tool shows your port configuration.

​
Publishing

Autoscale and Reserved VM deployments only support a single external port being exposed, and for the corresponding internal port not to be using localhost. If you expose more ports, or expose a single port on localhost, your published app will fail. An easy way to make sure your Autoscale deployments work as expected is to remove all the externalPort entries for the ports in your config except the port for the service you want to interact with from the internet.

​
Debugging

A common reason something might not be working as you’d expect is that while your port config looks right, your program is actually looking at a different port. For example, if your config is: 
[[ports]]
internalPort = 3000
externalPort = 80
Then internet traffic to port 80 will go to internal port 3000. However, if your program is actually not listening on port 3000, but rather something else (like 8080), it will appear as if no traffic is getting through. This can happen if you switch the port in your code without switching the corresponding port in your config, or copy-paste config from one project to another.
Programs can change the ports they listen to.
Each framework has different default ports it listens to — for example, Flask is 5000, react is 3000, and laravel is 8000. Make sure the right port is configured!

​
Preferences

We will automatically bind ports that are opened in your Replit App to available external ports when they are opened, and record that binding in the .replit config file. However, we don’t do this by default for internal ports that open on localhost, because services that usually run on localhost typically assume that they will only be accessible on the same computer as the process that’s running (localhost ports are only visible to the same computer running the process.) This means those services are often not as secure as services built under the assumption that they’ll be available to the public internet. You can always override this by setting the exposeLocalhost config option to true for the port you want to expose. If you want to always expose localhost ports by default, you can set your “automatic port forwarding” setting in the User Settings tool to “All ports”. If you want to never create config for ports that are opened, and manually control the port config for all your Replit App, you can set that to “never”.

​
Supported ports

Replit App will define port 80 as the external port by default when the first port opens. A Replit App can expose 3000, 3001, 3002, 3003, 4200, 5000, 5173, 6000, 6800, 8000, 8008, 8080, 8081, as extra external ports. Ports 22 and 8283 are not forwardable, as they are used internally.

​
[[ports]] .replit config

Type: {localPort, externalPort, exposeLocalhost} The [[ports]] config Allows you to configure which HTTP port to expose for your web output. By default, any exposed HTTP port with host 0.0.0.0 will be exposed as your Replit App’s web output. Extra ports can be served without overriding the default port by adding a new [[ports]] entry to your .replit file. You are required to specify both a localPort and externalPort entry. You can add multiple extra ports by adding multiple [[ports]] entries to your .replit file as defined below.

​
localPort

Determines which port Replit will bind to an external port.

​
externalPort

Determines which port should be exposed for that local port’s publicly accessible port. 
[[ports]]
localPort = 3000
externalPort = 80
If you want to never expose a particular port, you can leave the localPort config but just not add an externalPort: 
[[ports]]
localPort = 3000

​
exposeLocalhost

Determines whether an internal port using localhost can be bound to an external port. Can be true, false, or null. 
[[ports]]
localPort = 3000
externalPort = 80
exposeLocalhost = true