Technical Support

To be honest I think that the actual issue here is a plugin or a poor setup overall, if not even a custom javascript interefering with one of NodeBB's internals. As of now I had no longs from 0.7.x and up.

How about adding additional info:

NodeJS version Cluster? How do you start NodeBB?

Is it possible to use NodeBB as an OAuth2 provider? I searched for the answer to this, but all I found were lots of topics on connecting to other providers.

Hello!!
I want to authenticate my local mongodb server by using springmongoconfig i.e authenticating spring data of mongodb server.

@danielflippance

Have a look at the following post. I do not know if this is precisely the same as your issue but it seems to be in the same family.

@julian said in 'Category Privileges' does not seem to work:

I can confirm that the "Access Topics" privilege is not functioning correctly, so will need to look into that.

However, with "Create Topics" disabled, the "New Topic" button is not present, and the category itself is not present in the composer dropdown, so that privilege is working as intended.

Link Preview Image If a user does not have the "topics:create" privilege in a category, they are denied read access to topics in that category · Issue #4753 · NodeBB/NodeBB

favicon

GitHub (github.com)

Specifically:
@julian said in 'Category Privileges' does not seem to work:

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

I had to remove mine for now as it works, but in IE and FF it would cutoff the picture, but worked pretty well in Chrome.

Looking to get some NodeBB consulting at the API level, mostly around reality checks on architecture de

I followed the setting from here and got it fixed https://community.nodebb.org/topic/6525/invited-future-users-can-t-register/5

@UncleSam Yep @pichalite is right.. Its lavender with a few html side widgets.

These are the only css changes I have so far :

Changed font by doing this :

@import url(http://fonts.googleapis.com/css?family=Oswald:300,400);

body {
font-family: "Oswald", sans-serif !important;
}

Changed some colors :

a {
color:#346634;
}

a:hover {
color:#234423;
}

.category-box {
background: #f2f2f2;
}

.panel-default {
border-top-color: #6bb85c;
}

.btn-primary {
color: white;
background-color: #346634;
border-color: #234423;
}

.btn-primary:hover {
color: white;
background-color: #234423;
border-color: #234423;
}

.btn-default {
color: #346634;
background-color: white;
border-color: #234423;
}

.btn-default:hover {
color: #346634;
background-color: white;
border-color: #234423;
}

.open>.dropdown-toggle.btn-default {
color: #346634;
background-color: white;
border-color: #234423;
}

.topic .posts>li .topic-title {
color:#346634;
}

.btn-info {
color: white;
background-color: #6bb85c;
border-color: #234423;
}

.btn-info:hover {
color: white;
background-color: #6bb85c;
border-color: #234423;
}

.open>.dropdown-toggle.btn-info {
color: white;
background-color: #6bb85c;
border-color: #234423;
}

.topic .post-bar {
border-left: 2px solid #6bb85c;
}

.tag-topic-count {
border: solid 1px #6bb85c;
background-color: #6bb85c;
}

Changed upvote/downvote to be weed leafs rather than chevron :

.upvote {
background-image: url("http://420.vawta.com/wp-content/uploads/2016/06/2000px-Cannabis_leaf.svg_.png");
background-size: 20px;
}

.fa-chevron-up {
display:none;
}

.downvote {
background-image: url("http://420.vawta.com/wp-content/uploads/2016/06/red-leaf-md.png");
background-size: 20px;
}

.fa-chevron-down {
display:none;
}

Added Custom Background to display on desktop only:

@media only screen and (min-width: 768px) {
body {
background: url("http://www.all-sweets.com/images/white-gradient-5-1920x1080.jpg");
background-size: cover;
background-attachment: fixed;
}
}

Made is so recent post/comments doesn't display on mobile on home page:

@media only screen and (max-width: 950px) {
.category-item .post-preview:last-child {
border-bottom: none;
display: none;
}
}

(This last change makes it look really clean on mobile so it is not so messy)

Hello, after upgrade from 0.8 to 1.0 i have issue with launching forum in the cloud.
It crash with message:
2016-06-30T08:15:39.868567+00:00 app[web.1]: 30/6 11:15 [3] - error: Error: ENOENT: no such file or directory, scandir '/app/public/uploads/sounds'

For image upload im using: "nodebb-plugin-amazons3": "^0.2.4"

@scottalanmiller said in 503 - temporarily unavailable due to excessive load:

So our daily views (as reported by NodeBB) is 32K - 98K.

It sounds like I should be a little amazed that 512 MB of memory works...

I'll have to scale up my Digital Ocean tonight...

@jeff contact him through GitHub. If you find a bug, report it there.

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?