# Render app deploy stuck on in progress

> Learn how to fix a Render deploy stuck forever on in progress, caused by binding to 127.0.0.1, by starting your app on host 0.0.0.0 instead.

Author: [Flavio Copes](https://flaviocopes.com/about/) | Published: 2023-10-29 | Topics: [Services](https://flaviocopes.com/tags/services/) | Canonical: https://flaviocopes.com/render-app-deploy-stuck-on-in-progress/

I was trying to deploy an app on Render but stuck in a forever cycle of “in progress” build, the build never ended processing:

![Render deploy log shows no open HTTP ports on 0.0.0.0 while npm start runs Astro dev server bound to 127.0.0.1:4321](https://flaviocopes.com/images/render-app-deploy-stuck-on-in-progress/1.webp)

Notice 127.0.0.1? That’s the problem.

Render doesn’t “pick it up”.

You have to run it on port 0.0.0.0 instead of 127.0.0.1 

In this way for Node scripts, prepending `HOST=0.0.0.0`:

```javascript
HOST=0.0.0.0 node app.js
```

I used this in package.json, and used `npm run start` in my Render site setting "Start Command” for an [Astro](https://flaviocopes.com/astro-introduction/) site:

```javascript
{
  ...
  "scripts": {
    "dev": "astro dev",
    "start": "HOST=0.0.0.0 node ./dist/server/entry.mjs",
    "build": "astro build",
    "preview": "astro preview",
    "astro": "astro"
  },
  ...
}
```

![Render Start Command settings page explaining it launches app processes, with npm run start entered in the command field](https://flaviocopes.com/images/render-app-deploy-stuck-on-in-progress/2.webp)