What I expect:
That the category tiles behave like this, showing latest posts whenever people visit the home page:

What Works as expected:
It behaves the way I want it when one opens the site from the browser or refreshes the home page.

What doesn't work as expected:
When clicking on the "Siegefridge" forum title to the upper left or "Home" in the navigation bar, the tiles on the home page don't show a preview. It then looks like this:

As you can see, the footer also shifted up towards the top of the page, looking all jumbled (Lavender theme). If I cannot find a way to resolve this issue, I will have to look for a place other than the footer to house the copyright notice.

The footer shift doesn't happen with the vanilla theme. However, there are no previews at all, no matter how the page is entered. Just tiles.

Plugins:

• Default Sound Pack
• Markdown ParserNodeBB BBCode to Markdown
• NodeBB Category Info (disabled)
• NodeBB Emoji Extended
• NodeBB Essential Widgets
• NodeBB Youtube Lite
• NodeBB Editor Plus
• Username Mentions
• Various themes

Potential Sources of Problems
I have tried a few plugins, some of which have caused problems and needed to be removed from the command line (especially updating DBSearch caused a cascade of issues as it seems).

However, from the moment on I worked with the install the category preview didn't seem to show all the time. I am also quite sure I saw the jumbled footer for the first time quite early in the setup process. Thus, it might not be that likely that these problems have been caused by these events.

Setup details:

• NodeBB version: GIT clone from yesterday. Says 0.5.4 and that I am up to date on the panel. At the same time, the plugin panel seems to offer updates to newer plugin versions and complains in some cases that the newer versions aren't compatible with my version of NodeBB.
• Currently used theme: Lavender.
• Distribution: debian wheezy, Linux 2.6.32
• Database: Redis 2.8.17
• Database ID: 1
• Web server (reverse proxy): nginx 1.6.2
• npm version: 2.1.8
• Peculiarities: The server is set up to host two NodeBB instances. I've done this by rsync -avHAX-ing (it's possible I used cp -a for one of them) the contents of the git clone over to their respective installs. Each instance has a script that wraps their respective nodebb executables and runs them in their respective directories with their own config.json in them. Each instance also has its own system user in the current setup and is owned by that user.

NodeBB config.json:

{
    "base_url": "http://example.com",
    "port": "8082",
    "secret": "example",
    "bind_address": "127.0.0.1",
    "database": "redis",
    "redis": {
        "host": "127.0.0.1",
        "port": "6379",
        "password": "example",
        "database": "1"
    },
    "bcrypt_rounds": 12,
    "upload_path": "/public/uploads",
    "use_port": false,
    "relative_path": ""
}

nginx virtual server reverse proxy definition:

server {
        server_name example.com www.example.com;

        location / {
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header Host $http_host;
                proxy_set_header X-NginX-Proxy true;

                proxy_pass http://127.0.0.1:8082/;
                proxy_redirect off;

                # Socket.IO Support
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
	}