Technical Support

UPDATE:

The solution I've found for this problem is to run the following command inside the NodeBB installation folder

git cherry-pick 1f3fa3a90f5fc02b3b2dc950b3a340c361206cef

Doing so automatically merges the fixing commit without any further problems, making the Admin panel usable instantly after a NodeBB restart 🙂

@rod haha, appreciate your help and comments.

Some others have asked about it as well. I tried to do it but was unsuccessful. I think the problem is RequireJS, it might work with the proper configuration of requirejs and angular, but I haven't been able to figure it out.

@Aureney

example.com works fine except www.example.com does not. How do you fix this.

In your DNS. Forward www.example.com to example.com

how long can NodeBB run?

Until it runs out of memory.

What if the computer is shutdown, does the website still run?

No.

Hi everybody!
I want to suggest to upgrade vendor libs (you have old libs versions.). I tested replacement libs to new versions. Here is the result:

public/vendor/ace public/vendor/bootbox/ [update: no] public/vendor/bootstrap/ [update: ok (interface lags? https://github.com/twbs/bootstrap/issues/18777)] public/vendor/buzz/ [update: ok] public/vendor/colorpicker/ [update: no] public/vendor/fontawesome/ [update: ok] public/vendor/mdl/ [update: ok] public/vendor/requirejs/ [update: ok] public/vendor/semver/ [update: no] public/vendor/slideout/ [update: js error] public/vendor/snackbar/ [update: js error] public/vendor/tinycon/ [update: js error] public/vendor/visibility/ [update: ok] public/vendor/xregexp/ [update: js error] public/vendor/jquery/bootstrap-tagsinput/ [update: no] public/vendor/jquery/css/ public/vendor/jquery/deserialize/ [update: ok] public/vendor/jquery/draggable-background/ [update: no] public/vendor/jquery/event/ [update: no] public/vendor/jquery/js/ (jquery - update: ok | jquery.form.min - update: ok) public/vendor/jquery/serializeObject/ [update: no] public/vendor/jquery/sortable/ [update: ok] public/vendor/jquery/textcomplete/ [update: ok] public/vendor/jquery/timeago/ [update: ok] public/vendor/autosize.js [update: no] public/vendor/nprogress.min.js [update: js error]

Hi everyone,

I managed to install and configure nodebb but i got something really weird since i deleted a user yesterday.

I was using this steam login plugin and then found that it doesn't ask steam user to enter mail addresse. So i decided to delete a user created by a friend to try another plugin but now, whenever i try to login / register with a steam account, i got redirected to 502 bad gateway.

Also, seems like this plugin isn't compatible with nodebb 1.0.3, can someone point me out wherre is the latest/stable release of this kind of plugin ?

Also some nginx error logs with hope it could helps:

2016/06/22 08:50:38 [error] 5815#5815: *8405 connect() failed (111: Connection refused) while connecting to upstream, client: <MY.WAN.IP>, server: tempforum.mydomain.com, request: "GET /api/admin/general/dashboard?_=1466545356514 HTTP/1.1", upstream: "http://127.0.0.1:4567/api/admin/general/dashboard?_=1466545356514", host: "tempforum.mydomain.com", referrer: "https://tempforum.mydomain.com/admin/manage/users/latest" 2016/06/22 08:50:38 [error] 5815#5815: *8405 connect() failed (111: Connection refused) while connecting to upstream, client: <MY.WAN.IP>, server: tempforum.mydomain.com, request: "GET /templates/500.tpl?v=6ca952fd-749a-4a45-bbf0-c992b1feaa09 HTTP/1.1", upstream: "http://127.0.0.1:4567/templates/500.tpl?v=6ca952fd-749a-4a45-bbf0-c992b1feaa09", host: "tempforum.mydomain.com", referrer: "https://tempforum.mydomain.com/admin/manage/users/latest" 2016/06/22 08:50:38 [error] 5815#5815: *8405 connect() failed (111: Connection refused) while connecting to upstream, client: <MY.WAN.IP>, server: tempforum.mydomain.com, request: "GET /socket.io/?EIO=3&transport=polling&t=LLst_rT HTTP/1.1", upstream: "http://127.0.0.1:4567/socket.io/?EIO=3&transport=polling&t=LLst_rT", host: "tempforum.mydomain.com", referrer: "https://tempforum.mydomain.com/admin/manage/users/latest" 2016/06/22 08:50:39 [error] 5815#5815: *8405 connect() failed (111: Connection refused) while connecting to upstream, client: <MY.WAN.IP>, server: tempforum.mydomain.com, request: "GET /api/admin/general/dashboard?_=1466545356515 HTTP/1.1", upstream: "http://127.0.0.1:4567/api/admin/general/dashboard?_=1466545356515", host: "tempforum.mydomain.com", referrer: "https://tempforum.mydomain.com/admin/manage/users/latest" 2016/06/22 08:50:39 [error] 5815#5815: *8405 connect() failed (111: Connection refused) while connecting to upstream, client: <MY.WAN.IP>, server: tempforum.mydomain.com, request: "GET /templates/500.tpl?v=6ca952fd-749a-4a45-bbf0-c992b1feaa09 HTTP/1.1", upstream: "http://127.0.0.1:4567/templates/500.tpl?v=6ca952fd-749a-4a45-bbf0-c992b1feaa09", host: "tempforum.mydomain.com", referrer: "https://tempforum.mydomain.com/admin/manage/users/latest" 2016/06/22 08:50:41 [error] 5815#5815: *8271 connect() failed (111: Connection refused) while connecting to upstream, client: 93.31.210.52, server: tempforum.mydomain.com, request: "GET /socket.io/?EIO=3&transport=polling&t=LLsu0Oj HTTP/1.1", upstream: "http://127.0.0.1:4567/socket.io/?EIO=3&transport=polling&t=LLsu0Oj", host: "tempforum.mydomain.com", referrer: "https://tempforum.mydomain.com/" 2016/06/22 08:50:42 [error] 5815#5815: *8405 connect() failed (111: Connection refused) while connecting to upstream, client: <MY.WAN.IP>, server: tempforum.mydomain.com, request: "GET /api/admin/general/homepage?_=1466545356516 HTTP/1.1", upstream: "http://127.0.0.1:4567/api/admin/general/homepage?_=1466545356516", host: "tempforum.mydomain.com", referrer: "https://tempforum.mydomain.com/admin/manage/users/latest" 2016/06/22 08:50:42 [error] 5815#5815: *8405 connect() failed (111: Connection refused) while connecting to upstream, client: <MY.WAN.IP>, server: tempforum.mydomain.com, request: "GET /templates/500.tpl?v=6ca952fd-749a-4a45-bbf0-c992b1feaa09 HTTP/1.1", upstream: "http://127.0.0.1:4567/templates/500.tpl?v=6ca952fd-749a-4a45-bbf0-c992b1feaa09", host: "tempforum.mydomain.com", referrer: "https://tempforum.mydomain.com/admin/manage/users/latest" 2016/06/22 08:50:43 [error] 5815#5815: *8405 connect() failed (111: Connection refused) while connecting to upstream, client: <MY.WAN.IP>, server: tempforum.mydomain.com, request: "GET /socket.io/?EIO=3&transport=polling&t=LLsu13H HTTP/1.1", upstream: "http://127.0.0.1:4567/socket.io/?EIO=3&transport=polling&t=LLsu13H", host: "tempforum.mydomain.com", referrer: "https://tempforum.mydomain.com/" 2016/06/22 08:50:44 [error] 5815#5815: *8405 connect() failed (111: Connection refused) while connecting to upstream, client: <MY.WAN.IP>, server: tempforum.mydomain.com, request: "GET /socket.io/?EIO=3&transport=polling&t=LLsu1Io HTTP/1.1", upstream: "http://127.0.0.1:4567/socket.io/?EIO=3&transport=polling&t=LLsu1Io", host: "tempforum.mydomain.com", referrer: "https://tempforum.mydomain.com/admin/manage/users/latest"

EDIT: More logs gathered from launching nodebb in dev env.
https://gist.github.com/jffz/f95bee54e06082b66924e69f545157bc

@julian
Querying mongodb,

I had a stray category 15 that looked like the following:
{
"_id" : ObjectId("56bd923fc113b09c466f9055"),
"_key" : "category:15",
"parentCid" : 0
}
I removed that entry from mongo and now the API returns a 'NULL' at the end of my categories API.

Is there something else I should delete?

Just linking this related issue.

Link Preview Image ability to edit skin colors · Issue #3886 · NodeBB/NodeBB

I think it would be cool, but might take a little bit, if you made it so that admins could make custom skins by just changing the colors, and setting if it is a round or square skin, so like the Cerulean skin VS. the Cosmo theme. I know ...

favicon

GitHub (github.com)

yeah, no issues here either running node v4.4.5LTS with nodebb 1.0.3
I wonder if it is maybe a plugin causing it?

@pichalite That fixed it. Thanks for your help!

Link to that forum disabled for now 😄

Problem was solved by leaving blank the Cookie Domain field in Admin -> Settings -> Advanced

@Alexander-Craggs MongoDB, version 2.6 or greater is required

Thanks, I'll work on it and report here.

I think I got it pushed to the Heroku app because it did the building process it does with my own app, and I can see nodeBB in the Heroku logs starting up, but it crashes right away now. I am thinking it might have something to do with the MongoDB connection? (It's a Sandbox MongoLabs connection, but it works for my other app and when I run NodeBB locally it makes changes to to the online MongoLab DB as confirmed through their administrative tools)

These are my Heroku logs:
2016-06-15T00:00:56.420459+00:00 app[web.1]:
2016-06-15T02:54:01.203018+00:00 app[web.1]: > [email protected] start /app
2016-06-15T02:54:01.203024+00:00 app[web.1]: > node loader.js
2016-06-15T02:54:03.280111+00:00 heroku[web.1]: Process exited with status 0

I might have done something horribly wrong when building but I am at a loss for what it could be. After cloning the NodeBB from your git, and then trying to push it to my app with a fresh repo clone, it tells me what the srcref for master isn't there when I try "git push heroku master", however if I try what the tutorial says "git push -u heroku v1.x.x:master" it says that it's up to date instead and nothing gets pushed. This is when I tried setting my git heroku branch to master and pushing anyway (it uploaded and the app crash)

EDIT: I am going to try and do a fresh clone later when I get back from work and create a new Heroku app to attempt this from Step 1, and I will detail my process for you guys so that you have a better understanding of what I might be doing wrong.

Thats nice, support in native language is good 🙂

solved

can anyone add it to official documentation?
https://docs.nodebb.org/en/latest/configuring/proxies/apache.html

Thanks

Thanks, guys! I got it to work.

Fixed in latest master, the labels were swapped, so "Access" was actually controlling "Create", and vice versa.

@yariplus said in NGINX config problem ?:

If a location is defined by a prefix string that ends with the slash character, and requests are processed by one of proxy_pass, fastcgi_pass, uwsgi_pass, scgi_pass, or memcached_pass, then the special processing is performed.

... this explains so much 😓