Technical Support

I'm having exactly the same problem.
The solution of @yariplus does not help me, since then it generates an error when I login to the forum with Google, it tells me ops! an error has happened, our umpa loompas are working to fix it, and it won't let me login, the problem is that the forum is already in production

@oplik0 yeah we are having a loadbalancer before nginx!

using nodebb without SSL works perfectly using load balancer -> nginx -> nodebb

I would need to do some more testing but I saw that when using SSL , it redirect to www.domain.tld instead of domain.tld!

I just modify the nginx config for this vhost to send www. to non-www. and I will re-active the SSL!

The other thing is, I tried to add

"socket.io": { "origins": "https://community.nodebb.org:* https://nodebb.org:*" }

to the config.json and I got an error when starting nodebb

That solved my problem. Thank you so much!!!!

@Mickola Feel free to send a pull request to https://github.com/julianlam/nodebb-plugin-emailer-sendgrid, if fromname isn't supported in the sengrid nodejs api that should be removed as well.

@PitaJ shame on me. I missed somewhere that we need to rebuild/restart when we add plugin!

Hi,

Is there a way that our moderator/super moderator can create category and sub-category ?

Are they the owners of their groups (identified by star next to their name in group members list in Persona)? Because even if they're not moderators I believe group owners are able to add people to their group.

@jac see https://github.com/julianlam/nodebb-plugin-archiver

sudo apt-get install build-essential will fix it.

Thanks you so much!

I still don't know what caused everything to turn bad.

The funny thing here is that I just noticed that I broke my page rule for bypassing cache on accident some time ago (made a typo) and it wasn't working, and here I am helping someone deal with a problem I didn't actually solve until now XD

Hey there,

Recently I've been working on my forum and I have been adding a lot of things to the overall look / feel of the forum and my overrides in the admin section are just becoming a bit too much. I've been looking to start moving these into the theme itself when possible, but it appears as though a lot of the overrides are controlled by the skin rather than the theme itself, and while I can put things into .less files and override with !important, I'd rather modify slate to have the correct values and not have to override them -- this ensures that things are rendered properly.

Is there a way that I can access these skin files somewhere and build them properly?

Thanks,

I'm using NodeBB 1.13.2 and used the write API to upload a bunch of messages from another software into NodeBB. I needed to update the date so I modified the date of each post (using mongodb). The dates for each post are showing the correct date but when I try to sort via newest or oldest it doesn't sort by date order?
Is there something else I can do to get it to sort the posts in a topic by order? I've already deleted the indexes in mongodb and restarted nodebb to rebuild them but that didn't fix the problem.

Any ideas?

Thanks,
Kyle

thanks all.. admin disabled a plugin which was trying to send a notification to another system (discord) as part of posting message to bb topic

Link Preview Image Fresh installation seems broken

Use npm i [email protected] until the issue is fixed in jquery. Issue for tracking https://github.com/jquery/jquery/issues/4665

favicon

NodeBB Community (community.nodebb.org)

You can find some info about the topic/post structures here https://github.com/NodeBB/NodeBB/wiki/Database-Structure.

For plugin development info you can take a look at https://docs.nodebb.org/development/plugins/

You can look into the hook filter:topic.build which already has the tags of the topic in the tags field. Then you can add the additional data in that hook for the template to use. Sample hook:

myPlugin.filterTopicBuild = async function (hookData) { if (hookData.templateData.tags.includes('marvel') { hookData.templateData.posts[0].content += '<br/>this user likes marvel'; } }

This is just a simple example feel free to modiyy & improve.

Forgive me if this is a very obvious question. I just can't find the solution for the life of me.

I've installed and activated the following plugin: nodebb-plugin-category-notifications (https://github.com/NodeBB/nodebb-plugin-category-notifications#readme)
I then rebuilt & restarted the forum. I was able to get into the admin screen.

According to the description, my users should now have the ability to subscribe to categories. How do they do so? I don't see a button or option anywhere in proximity to the categories.

Thanks
Patrick

The entire error below. I've been searching for some clues, but coming up empty handed and hoping someone can help. This is a fresh install on a debian 10 server.

2020-04-17T16:33:02.636Z [26376] - error: [build] admin control panel styles build failed 2020-04-17T16:33:02.639Z [26376] - error: resource 'https://fonts.googleapis.com/css?family=Roboto:300,400,500,700' gave this Error: Error: socket hang up {"type":"File","filename":"/var/www/nodebb/nodebb/public/less/admin/paper/bootswatch.less","index":87,"line":5,"column":0,"callLine":null,"extract":["","@import url(\"https://fonts.googleapis.com/css?family=Roboto:300,400,500,700\");",""]} ==================================================================================================================================== 2020-04-17T16:33:02.647Z [26376] - error: resource 'https://fonts.googleapis.com/css?family=Roboto:300,400,500,700' gave this Error: Error: socket hang up {"type":"File","filename":"/var/www/nodebb/nodebb/public/less/admin/paper/bootswatch.less","index":87,"line":5,"column":0,"callLine":null,"extract":["","@import url(\"https://fonts.googleapis.com/css?family=Roboto:300,400,500,700\");",""]} (node:26376) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:26376) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@gotwf I truly miss zfs

@qxpd Possible and maybe even likely if your uninstall was incomplete. What platform are you on? How are you sending mail? Are you running your own smtp relay? If so, what are you using? Exim? Postfix? Or using third party SMTP relay service? Cuz those types of small details really do make a big difference.

As to the error message above, port 587 is the "well known" Submission port for SMTP. 127.0.0.1 is the local host's "loop back" interface which your machine favors for moving bits about whilst talking to itself. In this case: NodeBB is trying, unsuccessfully, to relay mail to the world via an SMTP server running on your local host. Is there one? If you do not know, you should not be running your own mail server as there be lots of security related dragons lurking thereabouts for even seasoned sysadmins.

Hence, unless you want to shoulder the responsibility of running your own SMTP server I'd suggest using a third party relay. Now, one thing that IS relatively simple to set up is a Null Client Relay, that ONLY accepts mail from the trusted local host and then relays that mail via SMTP protocol to your upstream internet facing smtp relay. Faster than the nodejs built in. And it is nice to have a "mail spool" in event outbound mail gets backed up for some reason. But that built-in works too. And a non issue with smaller sites. At least last time I looked at it.

Hope this helps some.

Sharp seems to have a bit of history for being somewhat of a thorn in the side....

Link Preview Image 1.10.1 → 1.10.2 libvips + whole X server dependency?

@rfc2822 Yes, sharp replaced jimp in 1.10.2 to fix some bugs. See: https://github.com/NodeBB/NodeBB/pull/6774 As far as I can tell libvips only need those X1...

favicon

NodeBB Community (community.nodebb.org)

It was confusing to me as well when I first tried taking NodeBB for a test drive. Great support here though for getting such glitches sorted. 👍