@teh_g Have your reporter try using the chat page vs the chat modal... ideally the modal should only ever be used on desktop (though I don't think we've made the transition yet)
Cannot connect to my nodebb on local host.
@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 devto start NodeBB in dev/debug mode, but you will need to run
./nodebb stopfirst to shut down the existing process. You can use
./nodebb statusto 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?