# Bootstrap failed with exit code 128

**URL:** <https://meta.discourse.org/t/bootstrap-failed-with-exit-code-128/373873>\
**Category:** Self-hosting\
**Created:** [July 11, 2025, 12:39pm UTC](https://meta.discourse.org/t/bootstrap-failed-with-exit-code-128/373873 "2025-07-11T12:39:12Z")\
**Posts on this page:** 1\
**Showing post:** 30

<div class="post-metadata">

**Author:** ![agemo](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@agemo](https://meta.discourse.org/u/agemo)\
**Post date:** [July 25, 2025, 11:58am UTC](https://meta.discourse.org/t/bootstrap-failed-with-exit-code-128/373873/30 "2025-07-25T11:58:54Z")

</div>

Got snagged by this. Did not expect the backup to fail. Thanks for this topic and the plugin one.

A tweak to communications via ADMIN would be good or at least a check on the `./launcher rebuild app` execution, with **stop** output with a y/n break in terminal continue.

Eventually had to remove the **discotoc** plugin to get it to work here but not sure that was listed in the plugin that are now core.

---

_[View the full topic](https://meta.discourse.org/t/bootstrap-failed-with-exit-code-128/373873)._