# Web Server is available at //localhost:24439?

**URL:** <https://discourse.gohugo.io/t/web-server-is-available-at-localhost-24439/36177>\
**Category:** support\
**Created:** [December 23, 2021, 6:23am UTC](https://discourse.gohugo.io/t/web-server-is-available-at-localhost-24439/36177 "2021-12-23T06:23:18Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![baker](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/baker/32/15845_2.png) [@baker](https://discourse.gohugo.io/u/baker)\
**Post date:** [December 23, 2021, 6:23am UTC](https://discourse.gohugo.io/t/web-server-is-available-at-localhost-24439/36177/1 "2021-12-23T06:23:18Z")

</div>

Suddenly today I see random server ports rather than the familiar `:1313/`

Why is that?

Not a major issue, just didn’t happen before and it’s a new port every time I restart.

---

<div class="post-metadata">

**Author:** ![alexandros](https://avatars.discourse-cdn.com/v4/letter/a/ecc23a/32.png) [@alexandros](https://discourse.gohugo.io/u/alexandros)\
**Post date:** [December 23, 2021, 6:32am UTC](https://discourse.gohugo.io/t/web-server-is-available-at-localhost-24439/36177/2 "2021-12-23T06:32:03Z")

</div>

Most likely the hugo process is already running.

If there is an instance of the local server running and another one is initiated, then the second instance receives a random address.

Have a look at your activity monitor.

---

<div class="post-metadata">

**Author:** ![davidsneighbour](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/davidsneighbour/32/24507_2.png) [@davidsneighbour](https://discourse.gohugo.io/u/davidsneighbour)\
**Post date:** [December 23, 2021, 1:47pm UTC](https://discourse.gohugo.io/t/web-server-is-available-at-localhost-24439/36177/3 "2021-12-23T13:47:22Z")

</div>

On a linux system run:

```auto
killall -9 hugo

```

and retry.

On Windows: “Did you reboot yet?”

---

<div class="post-metadata">

**Author:** ![baker](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/baker/32/15845_2.png) [@baker](https://discourse.gohugo.io/u/baker)\
**Post date:** [December 24, 2021, 5:43am UTC](https://discourse.gohugo.io/t/web-server-is-available-at-localhost-24439/36177/4 "2021-12-24T05:43:56Z")

</div>

I am on Windows, and when this happens I have another instance of `hugo.exe` running.

I have tailwind 3.0 running at the same time and I guess the `Ctrl+c` stops Tailwind, but not `Hugo Server`. Not really a major issue, I can stopp the `hugo.exe` manually. Also it’s not happening all the time.

```auto
    "start": "concurrently npm:watch:*",
    "watch:tw": "tailwindcss -i ./assets/css/main.css -o ./assets/css/style.css --watch",
    "watch:hugo": "hugo server",
    "build": "hugo --minify"

```

---

<div class="post-metadata">

**Author:** ![davidsneighbour](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/davidsneighbour/32/24507_2.png) [@davidsneighbour](https://discourse.gohugo.io/u/davidsneighbour)\
**Post date:** [December 24, 2021, 7:54am UTC](https://discourse.gohugo.io/t/web-server-is-available-at-localhost-24439/36177/5 "2021-12-24T07:54:34Z")

</div>

> [@baker](#):
>
> I am on Windows, and when this happens I have another instance of `hugo.exe` running.

That basically is the explanation why another port is used. A port can only be used by one single instance of a program. That’s a limit of the concept of ports. Start hugo twice and the second instance selects a different port. If you want to rule what port to use check the documentation about CLI parameters. There is one (probably --port, but I didn’t check) that allows you to define which port hugo uses.

Stopping your concurrent runs should stop both tailwind and hugo. If in doubt, you can create a shellscript for hugo that you call via watch:hugo and that explicitly kills all instances on CTRL-C. I don’t know how to do that for Windows, here is my Linux line:

```auto
trap "{ killall -9 hugo; }" SIGINT
# then run hugo
hugo server...

```