Technical Support

This is all dependent on how each server is configured.

Sorry my fault, I have that, just sent the wrong file. When I get home today I can take care of it. I deleted the last post with the error log because of the spam, but require a moderator to remove it.
@PitaJ

Thanks

In nodebb's case it will just need the A (or E... which will be nginx. Don't ask me why the E stands for nginx, as that is how they named the stack. Maybe because it is pronounced engine-x) and the M... for mongodb

@baris said in How to reset the counting of topic and post each categories:

In mongo cli, for each category you have to run the below query replacing the correct values.

db.objects.update({_key: "category:<replace_category_id>"}, {$set: {"topic_count": "<replace_correct_topic_count>", "post_count": "<replace_correct_post_count>"}});

This works like a charm

@baris dude ! thank you very much, it work

@nsuchy said in api encrypt plugin:

Is that all I need just to proxy through nginx, that's what I'm currently doing, I saw that plugin in settings and thought I was doing something wrong. I just wanted to confirm I'm doing everything properly.

Yup! I used the instructions here: https://docs.nodebb.org/configuring/proxies/nginx/

There is an example block with SSL in use there. No plugin needed. I use LetsEncrypt for free certs.

You used the wrong one, this is the right one:

I'd really appreciate if someone could get the dark skin on default theme working perfectly. I'm new to using NodeBB and am not sure how to get started with Skin Development 😕

It's kinda sad that I can't import old content / users. The site is running behind Nginx so apache issues aren't really a thing. All requests are proxied to NodeBB so I'm assuming the importer just doesn't work. Anyone wanna help me import topics and posts manually?

@pitaj thanks again, heres what i've got so far.

0_1506019887827_Screenshot from 2017-09-21 11-48-05.png

Thinking of doing maybe a floating footer but duno how that would work with continuous loading of the posts/threads. Maybe ill do a small marquee with crypto price ticker under the floating menu bar instead.

Hello guys,

Just installed Nodebb to Ubuntu server with Nginx reverse proxy according to the guide (https://docs.nodebb.org/installing/os/ubuntu/).

But on the homepage, I see only three words: "Categories", "Register", "Login". The problem is that I need to create the admin user but registration is impossible due to username validation error. Under username field I can see:

A unique username between and characters. Others can mention you with @username.

And whatever I type, I get:

Username too long

I've tried upgrading and rebuilding assets, nothing seems to help.

No errors seen both in the browser console and in the output of ./nodebb dev

Thank you in advance for your help!

I don't think so. This is something to bring up on the plugin's Github page.

@pitaj vestacp has several nginx.conf. As I mentioned I edited "site-specific" config in /home/admin/conf/web where vestacp keeps configs for all hosts, inculding ssl and lets encrypt.
Maybe you mean global nginx.conf which is located in /etc/nginx ? I did no changes in it.

@razr-world said in GRIPING about upgrade path:

The upgrade path should be changed so that there is a simple upgrade script that we run which will fetch the new code, diff and apply the changes.

You do realise that you just asked us to rewrite git, right? 😄

However, in any case, you're under no obligation to use git if you don't feel like it. You can download the tarballs here and copy them directly into the destination folder, overwriting files as necessary... although this is not really a supported upgrade step and I have no clue what could go wrong here.

I can confirm that npm downgrading to npm@4 solves this issue.
Had the same one.. Maybe it's worth to mention it at the release page.

Thank you @PitaJ

@maxpen Glad to hear it! We'll be here if you run into any other trouble with NodeBB.

@baris Thank you

make sure you have port 80 and/or 443 open on your firewall. I see 80 is open (I get the "Welcome to Nginx" message). So now you need to make a few changes in your nginx config for it to redirect 4567 to your site on 80/443 (http/https), as currently it is set to the nginx page.

The docs has a config you can use, just make the changes like Pitaj has suggested and for https, you will need a certificate. Lets-Encrypt is free

**Edit to add: Don't forget to restart nginx to use the new config

Try using digital ocean instead of open shift as we do not provide support for the latter.

It looks to have fixed after a freshly re run of mongorestore.

Thanks for the support!!