# Discourse down. Certificaat bijgewerkt, app opnieuw opgebouwd, maar werkt nog steeds niet

**URL:** https://meta.discourse.org/t/discourse-down-updated-certificate-rebuilt-app-but-still-not-working/300569
**Category:** Self-hosting
**Tags:** two-container
**Created:** [22 maart 2024 om 17:48 UTC](https://meta.discourse.org/t/discourse-down-updated-certificate-rebuilt-app-but-still-not-working/300569 "2024-03-22T17:48:47Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [22 maart 2024 om 18:58 UTC](https://meta.discourse.org/t/discourse-down-updated-certificate-rebuilt-app-but-still-not-working/300569/6 "2024-03-22T18:58:18Z")

</div>

If you’re not an experienced linux sysadmin, or if you’re happy to just spend a little more on hosting, then using the hosting provider’s interface to resize to an instance with more RAM is going to be easiest.

If you want to try adding swap, perhaps see my post [over here](https://meta.discourse.org/t/failed-to-bootstrap-on-first-install/295475/16) for some info and a link.

Edit: I see no indication that you’re short of disk space, so there’s no particular need to tidy up.

Edit: perhaps see also

> [@3.1.x to 3.2.0 upgrade hangs/fails on 1GB instance](https://meta.discourse.org/t/3-1-x-to-3-2-0-upgrade-hangs-fails-on-1gb-instance/293743/33):
>
> my list of standard instant diagnostics

---

_[View the full topic](https://meta.discourse.org/t/discourse-down-updated-certificate-rebuilt-app-but-still-not-working/300569)._