# 504 Gateway Time-out errors with 2 million post migrated vBulletin forum

**URL:** <https://meta.discourse.org/t/504-gateway-time-out-errors-with-2-million-post-migrated-vbulletin-forum/105665>\
**Category:** Self-hosting\
**Created:** [4 בינואר,‏ 2019,‏ 1:06am UTC](https://meta.discourse.org/t/504-gateway-time-out-errors-with-2-million-post-migrated-vbulletin-forum/105665 "2019-01-04T01:06:22Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [4 בינואר,‏ 2019,‏ 1:50am UTC](https://meta.discourse.org/t/504-gateway-time-out-errors-with-2-million-post-migrated-vbulletin-forum/105665/3 "2019-01-04T01:50:14Z")

</div>

You should be on an “optimized” droplet. Cpu speed will be important for your level of traffic.

After you resize you should run

```
./discourse-setup

```

Again. It’ll adjust the memory settings. You can control-c after its first message and then

```
./launcher destroy app
./launcher start app

```

Rather than letting it rebuild. (a two container installation will reduce downtime during rebuilds)

Things are likely slow due to lots of sidekiq jobs.

If you’d like hands on help tuning your installation my contact information is in my profile.

---

_[View the full topic](https://meta.discourse.org/t/504-gateway-time-out-errors-with-2-million-post-migrated-vbulletin-forum/105665)._
