Technical Support

@julian I confirm. It is fixed.

@sanatisharif said:

/css/font/BBCNassim

this code fix my issue:

@font-face { font-family: "BBCNassim"; src: url("/fonts/bbc-nassim-regular.eot"); src: local("☺"), url("/fonts/bbc-nassim-regular.woff") format("woff"), url("/fonts/bbc-nassim-regular.ttf") format("truetype"); font-weight: normal; font-style: normal; } @font-face { font-family: "BBCNassim"; src: url("/fonts/bbc-nassim-bold.eot"); src: local("☺"), url("/fonts/bbc-nassim-bold.woff") format("woff"), url("/fonts/bbc-nassim-bold.ttf") format("truetype"); font-weight: bold; font-style: normal; } body, p, h1, h2, h3, h4, h5, h6, .button, input[type="button"], input[type="submit"], input[type="text"], input[type="password"], input[type="email"], textarea, select, button, body, div, span, applet, object, p, blockquote, pre, a, abbr, acronym, address, big, cite, code, del, dfn, em, img, ins, kbd, q, s, samp, small, strike, strong, sub, sup, tt, var, b, u, center, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td, article, aside, canvas, details, embed, figure, figcaption, footer, header, hgroup, menu, nav, output, ruby, section, summary, time, mark { font-family: "BBCNassim",Tahoma,"Open Sans", "HelveticaNeue", "Helvetica Neue", Helvetica, Arial, sans-serif !important; }

You can edit the global footer from ACP>Extend>Widgets

0_1450440782070_upload-6a03f414-7666-4a8a-b1c9-2438fe719792

@djcyry Under ACP -> Settings -> General change site title

@djcyry you don't have to change proxy_pass http://127.0.0.1:4567 to add your IP... leave it as it is

if you add the server block in a .conf file under /etc/nginx/conf.d, then you don't need to add it in /etc/nginx/sites-available/default and
/etc/nginx/sites-enabled/default

Fixed as of https://github.com/NodeBB/NodeBB/commit/0af11c5c0c08e226ea155e84d3a8e09866ee7ca4

Never mind... I narrowed it down to a plugin that i made 😄 Nodebb stopped restarting when i disabled it.

@UncleSam Check your DNS settings. This has nothing to do with NodeBB. Your domain doesn't seem to be pointing to the IP address. Pinging your domain is not resolving to the IP address.

post your apache/nginx conf

@AOKP okay, will keep an eye on CPU load...

@pichalite [![CPU-Z] "" (http://valid.x86.fr/cache/banner/m6vn6f-5.png)] < No quotes will add banner in signature click on your profile on top right, then your name, that will bring you to profile page then click settings its at the bottom

Hello nodeBB ,
I have a question :

Right now i have a vps server :
OS : Ubuntu 14.04 LTS with Plesk panel .
6 vCores
8 GB + 4GB ram burst
200 GB SSD
100 Mbit/s

On this vps server i have another 10 websites wich all runs apache-mysql-plesk .

The question is :
Can i install nodeBB on this server without any problem for other sites ?

Thanks 👍

@ron_jeremy said:

I'm not 100% sure.

I have "failed" to install NodeBB on a DigitalOcean Droplet about 25 times by now. Seriously, I'm not exaggerating. The people at DO must have wondered "wtf is this guy doing?" because I was creating and destroying Droplets non-stop for days.

I think what made the difference for me this time was not installing redis or nodejs as per the official NodeBB install document. Instead, I only installed the Chris Lea files.

I was so tired to trying different methods of installation I actually started keeping a log of what I was doing. I got it down to where only a few lines would change, and I am pretty sure this is what finally worked for me (remember, this is on a DO Droplet running Ubuntu 14.04 x64):

add-apt-repository ppa:chris-lea/redis-server apt-get update apt-get install redis-server apt-get update apt-get install git apt-get install build-essential apt-get install imagemagick apt-get install python-software-properties add-apt-repository ppa:chris-lea/node.js apt-get update && apt-get dist-upgrade mkdir nodebb git clone git://github.com/designcreateplay/NodeBB.git nodebb cd nodebb npm install node app --setup
- only modify first line where I enter my server's address http://your.server.ip.address (without the port) and hit 'Enter' for all other options node app
- Now you can go to http://your.server.ip.address:4567 to see the forum

I have try this but when i go to npm install
i get this :
E: Unable to correct problems, you have held broken packages.

PD.
Got fixed with :

apt-get remove --purge nodejs npm
curl -sL https://deb.nodesource.com/setup_5.x | sudo -E bash -
apt-get install nodejs

For Azure, perhaps this helps?

Otherwise, our standard point of reference: https://docs.nodebb.org/en/latest/configuring/proxies.html

@pichalite Thank you so much! I did it.

I follow this :
https://docs.nodebb.org/en/latest/configuring/proxies/nginx.html#configuration

But I get error each time refresh (F5).

Browser console output :

WebSocket connection to 'ws://188.166.229.163/socket.io/?EIO=3&transport=websocket&sid=272_fqLIM0WJupWXAAA1' failed: Error during WebSocket handshake: Unexpected response code: 400

Please help.

@yariplus Thanks. Works like a charm.

ok I've just seen this working properly, good. My oh my what was going on.. no idea :squirrel:

I threw in an if(found) just in case - but I am always amazed by how little code is required.
That seem to happen a lot with Node.js and a well written software entitled NodeBB 👍