# Issue with new update: debugging options

**URL:** https://meta.discourse.org/t/issue-with-new-update-debugging-options/323972
**Category:** Self-hosting
**Created:** [August 29, 2024, 1:16pm UTC](https://meta.discourse.org/t/issue-with-new-update-debugging-options/323972 "2024-08-29T13:16:02Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![Isambard](https://avatars.discourse-cdn.com/v4/letter/i/858c86/32.png) [@Isambard](https://meta.discourse.org/u/Isambard)
#### Post date: [August 29, 2024, 1:16pm UTC](https://meta.discourse.org/t/issue-with-new-update-debugging-options/323972/1 "2024-08-29T13:16:02Z")

</div>

I noticed some issues with the recent update. I just updated from 3.4.0 beta1 to the latest (3.4.0.beta2-dev) and the site seems to work and then after a while (within 2 hours) the site stops responding (I get a host error via cloudflare). I have the old docker still up (split app/db) so pointed the proxy back the old docker container which still works.

I’m trying to figure out how best to debug it. Is there a way to assign a temporary different hostname to the docker to debug the instance separately (without re-writing the database to the new entries)?

---

_[View the full topic](https://meta.discourse.org/t/issue-with-new-update-debugging-options/323972)._