We got ours fixed, ignore me 🙂
Nothing to do with AWS, someone had changed our nGinx config and not told me.
When I try to connect with http://myip:4567 , I get the sign in [https://gyazo.com/8434361344875e688851246b5be39f87] but my username and password doesnt work even after 3 reinstalls. I dont even get errors in putty console.
Please assist me.
[Run on Ubuntu 16.04]
[Run with Redis]
Could you clarify something. Why are you saying putty console? Is this installation running on your local machine or is it running on a remote machine?
Also why are you running NodeBB 1.6.1 and not a more up-to-date one like 1.10.1?
 Its running on a vps that I rent on a monthly basis that I access thru putty/bitverse
 I upgraded nodebb and I still cannot connect.
So I used the docs instead of a 3rd party website, with redis as well as the database.
When I go to my url that I want to go to I get this.
Did you set up nginx? Does :4567 do anything?
No I havent set up nginx because I want to get nodebb working first with the port.
And yes I have added the port behind it. I am just really confused and just want to use this software.
@Apollo have you confirmed that the DNS is set up correctly?
For my Domain? If so yes, because first of all local host doesnt work either, and second I have sub directorys set up in my FTP of my webserver that is set up with name servers and works perfectly fine. I recently had MyBB setup but looking to switch over to NodeBB.
@Apollo ok I was just checking. You mentioned localhost doesn't work either. Is that using curl or something on the server itself?
There's a way to log out all ports and what processes are listening to them, can you try that and see if NodeBB shows up? Are you running NodeBB in dev mode, and in that case can you check for errors?
Im not running it in dev mode cause I dont even know how I would do that. And in that picture it states that nodebb is listening on 0.0.0.0:4567. I just dont understand, even after 5 reinstalls this doesnt work.
@Apollo this kind of thing happens pretty often, and usually it's not the fault of NodeBB. I can understand your frustration, and I'm trying to help you. Please bear with me.
Every question I ask, I ask for a reason. So please, try to answer all of my questions.
You can use
./nodebb dev to start NodeBB in dev/debug mode, but you will need to run
./nodebb stop first to shut down the existing process. You can use
./nodebb status to see if NodeBB is currently running. All of these commands are documented with
The command to list out processes and ports is
From what I can see there are no errors showing and under all ports its state is listen.
You mentioned localhost doesn't work either. What are using you test that? Please provide the exact command.
Can you post the output of the netstat command, the important information to gather from it is the processes that ports correspond to, not the listen state.
Never mind I resolved it myself.
@Apollo what was the issue?