Localhost 8080 что это

What is localhost:8080?

On the Internet, everything connected has an IP address which uniquely identifies Internet devices. A TCP/IP connection is always made to an IP address and a specific port on that address.

What does localhost:8080 mean?

1. localhost is the machine name or IP address of the host server.
2. 8080 is the address of the port on which the host server is listening for requests.

What is a port?

A port is a virtual point where network connections start and end. Ports are software-based and managed by a computer’s operating system. Ports are standardized across all network-connected devices, with each port assigned a number. In total , the system has 65535 ports to be used for providing services. Port numbers 0 to 1024 are reserved for privileged services and designated as well-known ports. This list of port numbers are specified in RFC 1700.

Usually one port is coupled to a specific process or «service» on the target computer. Some port numbers are standardized, like 80 for http , 20 and 21 for File Transfer Protocol (FTP) and so on. Because of that standardization you usually don’t need to put port numbers into your web addresses.

localhost:8080

Localhost is always your own computer. Your computer is talking to itself when you call the local host. Operating systems will normally resolve the hostname localhost to 127.0.0.1, your loop back interface. When running a web server on your computer, you need to access that server somehow — and since port 80 is already busy, you need to use a different port to successfully connect to it. Although any open port is fair game, usually such a server is configured to use port 8080, hence when accessing your server you type in:

So if in a browser, if http://localhost:8080 is entered, it simply means to server web-pages from local web-server which is listening for web-requests on 8080 port. The machine might not be connected to internet at all and still web-pages can be rendered in browser from local hard-drive.

Port 8080

Port 8080 is typically used for a personally hosted web server, when the ISP restricts this type of usage for non-commercial customers. But there is nothing that stops a process to listen for http requests on another port, like 98765, 1234 or 8080. Usually this is used for debugging purposes to not intermingle with another process (like IIS) already listening to port 80 on the same machine.

To get around this, you can use whatever port you like. You could use port 12345 if you wanted to. Port 8080 is the just the default second choice for a webserver.

Unable to serve on http://localhost:8080

When we are talking about “HTTP,” we always assume port 80 of your device is in play. By default, your internet browser will automatically use that port when you type in an address, unless you specify a different port.

When you are running a web server on your computer, you obviously will need to access that server somehow—and since port 80 is already busy, you will need to use a different port to successfully connect to it. For this reason, your server is usually pre-configured to use port 8080.

So, when you are attempting to access your server, you would type in:

http:// (protocol) localhost (your computer) :8080 (port 8080) / (path pointing to the root of the public folder of your server)

What Does This Look Like for Ether Apps?

Before diving in, it’s important to note that all ether apps run inside of an ethers “container.” For reference, there is an ethers container running at http://ethers.io, which was provided by ethers author, Richard Moore. The developer documents help shed some light behind the “container” infrastructure.

Issues involving localport:8080, typically involve some issue with the user not receiving the “ethers ready now!” message. This will prevent you from accessing your app inside the local running instance of the ethers container and will serve your app at http://ethers.io.

• Before proceeding, please make sure that you have included the ethers-app.js script is included in your HTML.
• Your HTML may contain a syntax error, such as not correctly closed with a pointy bracket. Something this minimal will create the error preventing you from seeing the “ethers ready now!” message
• If you get the following message or a variation of sorts, this may prevent you from serving locally, due to some problem with the local port 8080.

One user-solution presented is that you can access your app locally by visiting:

All you need to do with yours is REPLACE “ethers.io” in the URL above with “localhost:8080”.

This will force serve your app inside the locally running instance of the ethers container, rather than the container running at http://ethers.io

For more assistance on this, please visit Blockgeeks for a live thread on this issue.

serving content from file:///Users/username/blockgeeks/3_decentralisedApps/explorerapp

Listening on port: 8080

Local Application Test URL:

Why Am I Getting This Message?

If you are getting a local server failure, you will need to look at:

1. Whether the server started
2. Was the server started at the expected port?

Did the Server Start?

If the console window is still open, the expected message is:

Domain domain Started, where domain is the name of the default domain. This indicates that the default domain was started successfully.

If the console window is already closed, check for messages in the log file:

If startup was successful, the expected message is similar to that on the console, and appears at the end of the log file:

[INFO][. ][..][date&time][Application server startup complete .]

Was the Server Started at the Expected Port?

The server might be running at a different port number than expected, either because it was intentionally installed there, or because another server was already running on the default port when the server was installed.

Oracle has a great guide on this.

In determining which port number the server is actually using:

1. Examine the server’s configuration profile

2. Find the http-listener element

3. Inspect the value of the port attribute, and be sure to enter the correct port number when invoking the server.

Remember, the server’s default port number is 8080. So how can that expected value change?

localhost

Если вы хотите перейти на http://localhost, то воспользуйтесь быстрыми ссылками для входа:

• http://localhost
• http://localhost:8080
• http://localhost:8081
• http://localhost/phpmyadmin
• http://localhost/WordPress
• http://localhost:3000
• http://localhost/php
• http://localhost/index
• http://localhost/index.php
• http://localhost/server
• http://localhost/bonfire

Что такое localhost

localhost — это универсальное имя хоста, которое всегда указывает на этот же самый компьютер. Точнее говоря, это имя указывает на IP адрес 127.0.0.1, а данный IP уже является специальным адресом, всегда принадлежащий локальному компьютеру.

Если открыть адрес http://localhost в веб-браузере, то будет выполнено подключение к локальному веб-серверу. По этой причине localhost обычно ассоциируется с веб-сервером, но на самом деле localhost можно использоваться самыми разными сетевыми службами: программами для обмены данными между собой, MySQL, SSH, FTP и пр.

Вы можете даже пинговать localhost:

Пинги будут самыми лучшими из всех, какие вы когда-либо видели, поскольку проверяется соединение до этого же самого компьютера, на котором выполняется пинг.

Про loopback будет чуть ниже — на случай, если вам интересна теория, а сейчас рассмотрим, почему не работает localhost.

Как включить localhost

Возможно вы и так знали, что localhost это локальный веб-сервер, но при попытке открыть

http://localhost у вас возникает ошибка, например такая:

Не удается получить доступ к сайту

Сайт localhost не позволяет установить соединение.

Попробуйте сделать следующее:

Проверьте подключение к Интернету.

Проверьте настройки прокси-сервера и брандмауэра.

ERR_CONNECTION_REFUSED

Причин может быть несколько, самая популярная — вы просто не установили веб-сервер. Если это действительно так, то переходите к инструкции «Как установить веб-сервер Apache c PHP, MySQL и phpMyAdmin на Windows».

После завершения указанной инструкции localhost заработает!

Веб-сервер установлен, но localhost не открывается

В этом случае причины могут быть следующие:

• веб-сервер установлен, но его служба не запущена (особенно если раньше работало, а после перезагрузки перестало работать) — вернитесь к инструкции по установке, запустите службу веб-сервера и добавьте её в автозагрузку;
• неправильно настроены права доступа в веб-сервере, либо ошибка в конфигурации — вернитесь к настройке веб-сервера или переустановите его.

127.0.0.1

127.0.0.1 — это специальный IP адрес, который имеет loopback интерфейс. В любой операционной системе имеется поддержка 127.0.0.1, поскольку этот специальный IP описан в протоколе.

Суть работы 127.0.0.1 (а следовательно и localhost, который является именем для указания на этот IP) состоит в том, что пакет, отправленный на адрес 127.0.0.1 на самом деле никуда не отправляется, но при этом система начинает считать, что этот пакет пришёл из сети. То есть образно можно представить так: пакет отправляется на сетевую карту компьютера, там разворачивается и возвращается с сетевой карты обратно в компьютер.

Несмотря на кажущуюся бесполезность, такой подход очень популярен и используется для взаимодействия с самыми разными программами.

http://localhost:8080

Чтобы подключиться к localhost на 8080 порту перейдите по ссылке http://localhost:8080

localhost php

Чтобы использовать PHP на своём компьютере нужно установить веб-сервер. Пошаговую инструкцию смотрите в статье «Как установить веб-сервер Apache c PHP, MySQL и phpMyAdmin на Windows».

localhost phpmyadmin

Аналогично, для получения phpMyAdmin установите веб-сервер.

localhost error

Ошибки могут возникнуть в случае неправильной установки веб-сервера или приложений. Смотрите «Ошибки при настройке и установке Apache, PHP, MySQL/MariaDB, phpMyAdmin».

What does localhost:8080 mean? [closed]

This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.

Closed 1 year ago .

The community reviewed whether to reopen this question 1 year ago and left it closed:

Original close reason(s) were not resolved

What is the difference between localhost/web vs. localhost:8080/web?

6 Answers 6

A TCP/IP connection is always made to an IP address (you can think of an IP-address as the address of a certain computer, even if that is not always the case) and a specific (logical, not physical) port on that address.

Usually one port is coupled to a specific process or "service" on the target computer. Some port numbers are standardized, like 80 for http, 25 for smtp and so on. Because of that standardization you usually don’t need to put port numbers into your web adresses.

So if you say something like http://www.stackoverflow.com, the part "stackoverflow.com" resolves to an IP address (in my case 64.34.119.12) and because my browser knows the standard it tries to connect to port 80 on that address. Thus this is the same as http://www.stackoverflow.com:80.

But there is nothing that stops a process to listen for http requests on another port, like 12434, 4711 or 8080. Usually (as in your case) this is used for debugging purposes to not intermingle with another process (like IIS) already listening to port 80 on the same machine.

Note from 2021: When I made this post, I used port 80 as example because even though the OP didn’t specify a protocol, http was the usual web request standard back then and 80 ist the standard for http. Nowadays pretty much everything runs on https and the standard port for that is 443.