You'll want to find the pid (process id) of the running NodeBB process. Use ps aux | grep node to see all process that are node based.
Then kill it by pid.
julian@laptop ~/nothingtoseehere (master) $ ps aux | grep node
julian 11381 5.5 1.3 959772 53680 ? Ssl 18:25 0:00 /home/julian/.nvm/versions/node/v4.4.0/bin/node /home/julian/nothingtoseehere/loader.js
julian 11396 3.7 0.9 910404 37308 pts/5 Sl+ 18:25 0:00 node ./nodebb log
julian 11405 44.0 3.8 1303708 153892 ? Rl 18:25 0:05 /home/julian/.nvm/versions/node/v4.4.0/bin/node app.js
julian 11483 0.0 0.0 15192 2260 pts/6 S+ 18:25 0:00 grep --color=auto node
Looks like the NodeBB app is on pid 11405, and the loader is 11381. kill 11381 will kill both (as the app is a child of the loader)
I've noticed over the past week on Mangolassi.it and now here when making another report that when I am surfing around the site, or clicking a button, frequently my browser will hang for a moment (up to several seconds). Then occasionally the browser will white out and say Not Responding.
@jimmyc2018 said in Issue naming the root of NodeBB install:
@pitaj I did, I could see it live at http://myipaddress:4567
Is your domain set to resolve to that IP address?
Your nginx config also looks like it is missing a lot. The documentation has a lot of info. A full example block with all the recommendations lives here: https://docs.nodebb.org/configuring/scaling/ but at a minimum you should follow the guide on this page: https://docs.nodebb.org/configuring/proxies/nginx/
@abhinov-singh If you are using Nginx on Ubuntu, the configuration files or symlinks (including ports, etc.) are at /etc/nginx/sites-enabled/
See also which ports are left open by your firewalls (server, PC).