# Weird issue when ghost behind an loadbalancer

**URL:** <https://forum.ghost.org/t/weird-issue-when-ghost-behind-an-loadbalancer/2082>\
**Category:** Developer help\
**Created:** [July 20, 2018, 2:54pm UTC](https://forum.ghost.org/t/weird-issue-when-ghost-behind-an-loadbalancer/2082 "2018-07-20T14:54:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![zozo](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/zozo/32/574_2.png) [@zozo](https://forum.ghost.org/u/zozo)\
**Post date:** [July 20, 2018, 2:54pm UTC](https://forum.ghost.org/t/weird-issue-when-ghost-behind-an-loadbalancer/2082/1 "2018-07-20T14:54:17Z")

</div>

Hello,

I have a weird issue. I am running ghost on two nodes behind haproxy as a loadbalancer. When we create a post the node on which the post is created will instantly see new content however the other node will not show the newly added content until the ghost service is reloaded. Both nodes are connecting to the same database therefore the issue with the data not be replicated between the nodes does not exist.

I am using the latest ghost version. I get the same behaviour no matter the browser I use.

Thank you in advance.

---

<div class="post-metadata">

**Author:** ![Kevin](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kevin/32/32_2.png) [@Kevin](https://forum.ghost.org/u/Kevin)\
**Post date:** [July 20, 2018, 2:56pm UTC](https://forum.ghost.org/t/weird-issue-when-ghost-behind-an-loadbalancer/2082/2 "2018-07-20T14:56:03Z")

</div>

@zozo from the big warning in the [install guide](https://docs.ghost.org/docs/install):

> **Node/Docker clustering and other multi-server setups**  
> Ghost does not support clustering or multi-server setups of any description, there should only be one Ghost instance per blog. The recommended scaling and performance approach is to put a cache and/or CDN in front of your blog; pages generated by Ghost are essentially static so there should be very little traffic hitting your Ghost server with a well configured cache.

---

<div class="post-metadata">

**Author:** ![zozo](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/zozo/32/574_2.png) [@zozo](https://forum.ghost.org/u/zozo)\
**Post date:** [July 20, 2018, 2:59pm UTC](https://forum.ghost.org/t/weird-issue-when-ghost-behind-an-loadbalancer/2082/3 "2018-07-20T14:59:59Z")

</div>

> [@Kevin](#):
>
> **Node/Docker clustering and other multi-server setups**  
> Ghost does not support clustering or multi-server setups of any description, there should only be one Ghost instance per blog. The recommended scaling and performance approach is to put a cache and/or CDN in front of your blog; pages generated by Ghost are essentially static so there should be very little traffic hitting your Ghost server with a well configured cache.

Is there any intention of adding this kind of support in the future?

---

<div class="post-metadata">

**Author:** ![Kevin](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kevin/32/32_2.png) [@Kevin](https://forum.ghost.org/u/Kevin)\
**Post date:** [July 20, 2018, 3:00pm UTC](https://forum.ghost.org/t/weird-issue-when-ghost-behind-an-loadbalancer/2082/4 "2018-07-20T15:00:41Z")

</div>

See:

> [@External in-memory cache option](https://forum.ghost.org/t/external-in-memory-cache-option/1140):
>
> An option to use an external in-memory data store like Redis or Aerospike by using an adapter. This would help in allowing users to scale ghost horizontally behind load balancers.

Please use the search before opening topics ;-)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex015/uploads/ghost2/original/2X/b/ba9ce5100b8bb264586f4f572545596b2ce3f081.png) [@system](https://forum.ghost.org/u/system)\
**Post date:** [August 3, 2018, 3:00pm UTC](https://forum.ghost.org/t/weird-issue-when-ghost-behind-an-loadbalancer/2082/5 "2018-08-03T15:00:44Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.