Weird, that fixed it. I assumed that since the URL was exactly the same whether I ran it with ./nodebb start or ./nodebb dev, it couldn't be related to cache. I suppose I just don't know enough about how caches work.
Thanks anyways
Weird, that fixed it. I assumed that since the URL was exactly the same whether I ran it with ./nodebb start or ./nodebb dev, it couldn't be related to cache. I suppose I just don't know enough about how caches work.
Thanks anyways
UPDATE:
I'm stupid. It was a cache issue.
I've recently installed nodebb. I find the nodebb vanilla theme to be looking pretty good:
But then, whenever I go to some category and back again, I'm met with this mess:
Reloading the page fixes it.
This happens both when running behind an apache2 proxy and when running behind an nginx proxy. However, it doesn't seem to happen when accessing it directly instead of through a proxy. It also doesn't seem to happen when running nodebb with ./nodebb dev
instead of ./nodebb start
, even when running behind an apache or nginx proxy. The ./nodebb dev
output is also clean.
Does anyone have any clue what may be going on?
Ya, an outdated redis was the issue. Updated it, and now everything works nicely
Here's the log from running ./nodebb dev
:
http://pastebin.com/LL5ChDLV
When I refresh the page, I return to the login view, prompting me for a username and password. However, trying to log in again, it gives me this error:
Failed login attempt, please try again.
account-locked
I get the no data received
message when accessing nodebb directly on port 4567. When running behind nginx reverse proxy, trying to log in gives me a 502 bad gateway
, though the rest of the site seems to work fine. When running behind Apache, trying to log in gives me a "proxy error":
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request POST /login.
Reason: Error reading from remote server
I assume nginx and apache are complaining because nodebb isn't working, so that shouldn't be relevant now.
Looking at the output from ./nodebb dev
, it seems like some "pexpire" command is missing from redis. Maybe that was added to a later version than what I have? redis-server --version
claims redis is in version 2.4.14, while the website claims 2.8.17 is the latest version. Hang on, I'll try updating...
update:
Turns out my redis-server was outdated. Grabbing the newest version from their website fixed it.
Hi!
I'm trying to set up nodebb on Debian. I've followed the installation guide for Debian, and everything seems to be mostly working. However, when trying to log in, my browser simply tells me that no data was received. Does anyone have any idea what could be causing this?