# Een upgrade heeft mijn site offline gehaald; hoe lang duurt het tot deze hersteld is?

**URL:** https://meta.discourse.org/t/an-upgrade-knocked-my-site-offline-how-long-until-its-restored/373394
**Category:** Self-hosting
**Created:** [8 juli 2025 om 15:48 UTC](https://meta.discourse.org/t/an-upgrade-knocked-my-site-offline-how-long-until-its-restored/373394 "2025-07-08T15:48:17Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [8 juli 2025 om 16:33 UTC](https://meta.discourse.org/t/an-upgrade-knocked-my-site-offline-how-long-until-its-restored/373394/7 "2025-07-08T16:33:41Z")

</div>

This should be your next step:

> [@JammyDodger](#):
>
> Though as it’s an ‘oops’ page you may also find more detail in your `/logs` if there’s a conflict somewhere.

If even this doesn’t work, you can watch the logs via e.g.:

```plaintext
docker exec app ls -l /shared/log/rails/
docker exec -it app tail -f /shared/log/rails/production.log

```

---

_[View the full topic](https://meta.discourse.org/t/an-upgrade-knocked-my-site-offline-how-long-until-its-restored/373394)._