# Discourse instance stops running in every midnight

**URL:** https://meta.discourse.org/t/discourse-instance-stops-running-in-every-midnight/347795
**Category:** Support
**Tags:** unsupported-install
**Created:** [January 18, 2025, 4:15am UTC](https://meta.discourse.org/t/discourse-instance-stops-running-in-every-midnight/347795 "2025-01-18T04:15:39Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![keithkhl](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@keithkhl](https://meta.discourse.org/u/keithkhl)
#### Post date: [January 18, 2025, 4:15am UTC](https://meta.discourse.org/t/discourse-instance-stops-running-in-every-midnight/347795/1 "2025-01-18T04:15:39Z")

</div>

I have recently copied a discourse instance to another folder in my server and assigned a new domain.

The new one has nearly identical settings, but runs with different logo, categories, and policy, but other than that, both are the same.

The old instance’s name is ‘app’, as for all ordinary Discourse instances, and the new one is ‘app2’. I have changed the ‘app.yml’ in /containers/ to ‘app2.yml’, and run rebuild, when I initially set up this copy website.

But the new site stops running in every midnight. The command ‘./launcer rebuild app2’ makes it working until the day’s midnight.

I initially thought it is due to backup, but even after I killed all backups, I still experience the same issue.

It could be Redis, as I can see that, inside the container, the processor cannot find redis.

I can certainly try re-installing from scratch or make the original one a multisite, but would like to find a way to resolve this.

---

<div class="post-metadata">

### Author: ![NateDhaliwal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/natedhaliwal/32/313494_2.png) [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [January 18, 2025, 4:28am UTC](https://meta.discourse.org/t/discourse-instance-stops-running-in-every-midnight/347795/2 "2025-01-18T04:28:21Z")

</div>

I would make it a multisite installation. The processes terminate at the end of the day, but multisite should make them stay up.

> [@Multisite configuration with Docker](https://meta.discourse.org/t/multisite-configuration-with-docker/14084):
>
> warning While multisite is supported in the Discourse application, this is an advanced sysadmin setup. If you don’t know what you’re doing, do not set up multisite. The Discourse team is unable to provide multisite configuration support. If you wish to host multiple domains on a singled Docker setup, you’ll need a multisite configuration. Here are the basic building blocks for one. Understand hooks Multisite is a fairly advanced topic. Before attempting a multisite build, spend some time…

---

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [January 19, 2025, 2:51pm UTC](https://meta.discourse.org/t/discourse-instance-stops-running-in-every-midnight/347795/3 "2025-01-19T14:51:22Z")

</div>

> [@NateDhaliwal](#):
>
> The processes terminate at the end of the day, but multisite should make them stay up.

🤔 why would that make a difference?
