# Problems starting Ghost 2.25.1 on Debian 9.9

**URL:** <https://forum.ghost.org/t/problems-starting-ghost-2-25-1-on-debian-9-9/7912>\
**Category:** Developer help\
**Created:** [June 23, 2019, 3:09pm UTC](https://forum.ghost.org/t/problems-starting-ghost-2-25-1-on-debian-9-9/7912 "2019-06-23T15:09:49Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![joncojonathan](https://avatars.discourse-cdn.com/v4/letter/j/e9c0ed/32.png) [@joncojonathan](https://forum.ghost.org/u/joncojonathan)\
**Post date:** [June 29, 2019, 8:32am UTC](https://forum.ghost.org/t/problems-starting-ghost-2-25-1-on-debian-9-9/7912/9 "2019-06-29T08:32:12Z")

</div>

Many thanks @jeff - the problem was a path inside the systemd unit for the service following the Node move.

```auto
ExecStart=/usr/bin/node /usr/bin/ghost run

```

Path `/usr/bin/node` no longer existed (confirmed via `ls /usr/bin/node`). In case others have this problem, find node by using `whereis node`:

```bash
manager@server:~$ whereis node
node: /usr/local/bin/node

```

Then use a text editor to correct the config line:

```auto
ExecStart=/usr/local/bin/node /usr/bin/ghost run

```

Systemd then needs to be told about the changes, as the unit has changed on disk, by using `sudo systemctl daemon-reload`.

Ghost can then be started using `ghost start` or `sudo systemctl start ghost_localhost`.

Thanks for the help!

---

_[View the full topic](https://forum.ghost.org/t/problems-starting-ghost-2-25-1-on-debian-9-9/7912)._