---
title: "Could not deployAvailableApplications Jetty server Failed to bind to /0.0.0.0:8080 Address already in use"
description: "If you are trying to run Elements, or your custom [Element](https://namazustudios.com/glossary/element/) project, directly in your IDE, and you see an exception like this: ![](https://namazustudios.com/wp-content/uploads/2026/01/Screenshot-2026-01-30-at-10.31.52-AM-1024x412.png) the important parts are: ``` Exception in thread \"main\" dev.getelements.elements.sdk.model.exception.InternalException: Could not deployAvailableApplications Jetty server. ...…"
url: "https://namazustudios.com/docs/troubleshooting-guide/community-edition/running-in-the-ide/could-not-deployavailableapplications-jetty-server/"
updated: "2026-08-13"
category: Troubleshooting / Namazu Elements Community Edition / Running in the IDE
---

# Could not deployAvailableApplications Jetty server Failed to bind to /0.0.0.0:8080 Address already in use

If you are trying to run Elements, or your custom [Element](https://namazustudios.com/glossary/element/) project, directly in your IDE, and you see an exception like this:

![](https://namazustudios.com/wp-content/uploads/2026/01/Screenshot-2026-01-30-at-10.31.52-AM-1024x412.png)

the important parts are:

```
Exception in thread "main" dev.getelements.elements.sdk.model.exception.InternalException: Could not deployAvailableApplications Jetty server.
...
Caused by: java.io.IOException: Failed to bind to /0.0.0.0:8080
...
Caused by: java.net.BindException: Address already in use
...
```

Then the likely culprit is that you are already running another instance of Elements locally. If you look at your running containers in [Docker](https://namazustudios.com/glossary/docker/) Desktop (or using `Docker ps` in the terminal), and you see that a ws container is running (ws-1 in this case), then it will already be using the address that the IDE will attempt to bind to. Shutting down this container will allow you to run in the IDE again. You can use the stop button in [Docker](https://namazustudios.com/glossary/docker/) Desktop, or via command line using `docker stop <container name>`, e.g. `Docker stop Docker-compose-main-ws-1` (use `Docker ps -a` to see all containers and their names - use the [name](https://namazustudios.com/glossary/name/) of the container to stop it).

![](https://namazustudios.com/wp-content/uploads/2026/01/Screenshot-2026-01-30-at-10.25.23-AM-1024x247.png)
[Docker](https://namazustudios.com/glossary/docker/) Desktop containers

![](https://namazustudios.com/wp-content/uploads/2026/01/Screenshot-2026-01-30-at-10.28.53-AM-1024x23.png)
[Docker](https://namazustudios.com/glossary/docker/) ps -a result

Reminder!

Bear in mind that you'll still want the mongo container running, even when running in the IDE.