# Unable to start service php8.2-fpm on Ubuntu 24.04.2

**URL:** https://discourse.roots.io/t/unable-to-start-service-php8-2-fpm-on-ubuntu-24-04-2/29371
**Category:** trellis
**Tags:** deploys, trellis, sage10
**Created:** 2025-03-05T23:20:39Z
**Posts:** 2

## Post 1 by @teokk1 — 2025-03-05T23:20:39Z

I’ve been trying to deploy my Sage 10 site for a few days now. It’s my first site made with the framework, and also the first time I’m using Trellis.

It keeps breaking at one of two steps:

1. Unable to start service php8.2-fpm
2. missing nginx config files from h5pb (e.g. cache\_expiration.conf)

I’m able to resolve the first issue by doing:

```
sudo apt purge php8.2-fpm
sudo apt install php8.2-fpm
```

However, frustratingly it happens every time I provision again (which is all the time because of the second issue).

I tried rebooting and updating everything on the server, but it does not help. Since I’m using a relatively unknown cloud provider (Contabo), I decided to follow the official guide and use `trellis droplet create` and bought a completely clean droplet, that was set up by the trellis cli itself. It also failed on the exact same issue:

```
RUNNING HANDLER [common : reload php-fpm] **************************************
fatal: [178.62.201.164]: FAILED! => {"changed": false, "msg": "Unable to start service php8.2-fpm: Job for php8.2-fpm.service failed because the control process exited with error code.\nSee \"systemctl status php8.2-fpm.service\" and \"journalctl -xe\" for details.\n"}
```

I also tried the same thing with a completely blank site, and the same thing happens. I found this thread: [Unable to start php8.2-fpm on Ubuntu 20.04 - #3 by Chriis](https://discourse.roots.io/t/unable-to-start-php8-2-fpm-on-ubuntu-20-04/29056/3), but I’m on the latest LTS (and the user wasn’t able to find a solution even when they upgraded).

---

## Post 2 by @jasperfrumau — 2025-03-07T03:16:30Z

I would check PHP-FPM Status and so run this command on the server:

```
systemctl status php8.2-fpm.service
```

and look for error messages.

also check the detailed Logs

```
journalctl -xe | grep php
```

Commands may need to be run using `sudo`.This will show relevant system logs.

If those logs do not help post them here and perhaps someone can chip in.