Technical Support

@PitaJ v16.13.0 obviosuly very old 😞 Ooops..installed latest version and now it is all ok..

Thanks for the gentle reminder.

@hnipps said in Invalid CSRF token when authenticating via third-party app:

I'm trying to use NodeBB as a headless forum (i.e. just a REST API with a separate front end) but keep getting an "invalid csrf token" error when I try to authenticate.

I've confirmed I can authenticate via the NodeBB UI on the same instance.

I've also tried getting the NodeBB config and using the csrf token from there in my requests but it still does not work.

My frontend is a NextJS app that rewrites all /api/:path* requests to http://<MY-NODE-BB-INSTANCE>/api/:path*. It also rewrites the auth paths.

I can see the requests reach NodeBB but always get "invalid csrf token".

I've verified that I can successfully call GET endpoints from my app, e.g. I can get the user list from /api/users.

This is a 2 yr old thread, but @hnipps have you gone any further with the React/NextJS frontend with a headless nodebb?
If you have made any progress I would love to contribute on the frontend build. It is daunting to start as a new project but if any foundations were laid I would love to jump in and build upon it.

Thank you @julian you always respond and seem motivated in helping the community. By proprietary I meant no effort has been made to provide clean working examples for the latest nodebb, as in maintenance of such documentation for people jumping into nodebb to replace their old system.

You have a great product here, with so much more potential and I understand you may not have resources and funding to provide so much documentation and maintain working example of a plugin that does CRUD with custom fields/custom data, but it becomes harder for new adopters if they're unable to figure out cost effective way to replace their old platforms which have plethora of 3rd party add-ons and plugins especially dealing with custom fields and custom data.

I take the blame as well, as part of the community it is partly our job to help keep a set of quickstart plugins, documentation, help available to enhance and optimize the process for new adopters. I hope the community gets together and makes something like a curated directory of available plugins, and tags and tracks what versions each supports, and tries to keep a version that supports the latest major version updates.

Thank you for the wonderful product, I keep trying and finding an excuse to adopt it and hopefully I will get there sooner or later.

@baris thank you very much. 👍

@baris said in codes for the skins:

The css for these are coming from https://bootswatch.com/, you can find them in nodebb/node_modules/bootswatch/dist

Thank a lot... I searched the GitHub and found them here:

Link Preview Image bootswatch/dist at v5 · thomaspark/bootswatch

Themes for Bootstrap. Contribute to thomaspark/bootswatch development by creating an account on GitHub.

favicon

GitHub (github.com)

Replied in the other linked topic.

@julian yeah, database in the same VM. I already did re-indexing using this commands.

@B-738 spiders are bots, web crawlers, etc.

You can restrict access to them for certain categories, for example.

As you named your postgres container db, you should use db as database host.

@julian I tried that route, and it still didn't work:
-rw-r--r--. 1 redis redis 63122 Mar 6 13:56 /path/to/redis/redis.conf
redis.service: (changed the path to my redis.conf)
ExecStart=/usr/bin/redis-server /path/to/redis/redis.conf --supervised systems

After changing the redis service file:
systemctl daemon-reload
systemctl start/restart redis
● redis.service - Redis persistent key-value database
Loaded: loaded (/usr/lib/systemd/system/redis.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/redis.service.d
└─limit.conf
Active: failed (Result: exit-code) since Thu 2024-03-07 16:18:06 EST; 7s ago
Process: 3672598 ExecStop=/usr/libexec/redis-shutdown (code=exited, status=0/SUCCESS)
Process: 3672869 ExecStart=/usr/bin/redis-server /path/to/redis/redis.conf --supervised systemd (code=exited, status=1/FAILURE)
Main PID: 3672869 (code=exited, status=1/FAILURE)

Mar 07 16:18:06 my-lab systemd[1]: Starting Redis persistent key-value database...
Mar 07 16:18:06 my-lab redis-server[3672869]: 3672869:C 07 Mar 2024 16:18:06.355 # Fatal error, can't open config file '/path/to/redis/redis.conf'
Mar 07 16:18:06 my-lab systemd[1]: redis.service: Main process exited, code=exited, status=1/FAILURE
Mar 07 16:18:06 my-lab systemd[1]: redis.service: Failed with result 'exit-code'.
Mar 07 16:18:06 my-lab systemd[1]: Failed to start Redis persistent key-value database.

In case anyone else might be intrested, I fixed this color problem using these codes:

.category-1 , .category-70 , .category-120 { .category-children-item .fa-caret-right { color: #ff9800 !important ; } } .category-111 { .category-children-item .fa-caret-right { color: #e91e63 !important ; } } .category-2 , .category-77 , .category-78 , .category-126 , .category-127 , .category-132 , .category-93 , .category-115 { .category-children-item .fa-caret-right { color: #4caf50 !important ; } }

Basically I had to name each category separately... So, if there is any suggestion to shorten the code, I would love to hear... 🤣

I've updated this plugin to nodebb 3.2 and up, new version is 3.0.0.

You would have to run a custom script like below. Place it in your nodebb folder, change the group name your special access group and run it with node myscript.js. It will add all users who have 10 posts or more into that group.

'use strict'; const nconf = require('nconf'); nconf.file({ file: 'config.json', }); nconf.defaults({ base_dir: __dirname, views_dir: './build/public/templates', upload_path: 'public/uploads', }); const db = require('./src/database'); const groupName = '<Replace with your groupname>'; db.init((err) => { if (err) { console.log(`NodeBB could not connect to your database. Error: ${err.message}`); process.exit(); } addUsersToGroup((err) => { if (err) { console.error(err); process.exit(); } console.log('done'); process.exit(); }); }); async function addUsersToGroup(callback) { const user = require('./src/user'); const groups = require('./src/groups'); const batch = require('./src/batch'); // check if target group exists const exists = await groups.exists(groupName); if (!exists) { return callback(new Error('group does not exist')); } try { const now = Date.now(); await batch.processSortedSet('users:joindate', async (uids) => { const userData = (await user.getUsersData(uids)) .filter(u => u && u.postcount >= 10); await db.sortedSetAdd( `group:${groupName}:members`, userData.map(() => now), userData.map(u => u.uid) ); }, { batch: 500, }); const memberCount = await db.sortedSetCard(`group:${groupName}:members`); console.log('total count', memberCount); await db.setObjectField(`group:${groupName}`, 'memberCount', memberCount); await db.sortedSetAdd( 'groups:visible:memberCount', memberCount, groupName, ); callback(); } catch (err) { callback(err); } }

@ursyaathi You'd be better placed using SSO for that - see https://community.nodebb.org/topic/17484/a-more-standardised-sso-implementation/2?_=1709300209014

Thanks!, I was able to debug the issue.

@baris i know it is nothing urgent, but looking forward to having this addition 😄

Link Preview Image Targeted Multi-User tagging · Issue #244 · julianlam/nodebb-plugin-mentions

I suggest the usage of @everyone and @here to notify all users in the forum and on the topic respectively... please see this: https://community.nodebb.org/topic/17283/targeted-multi-user-tagging

favicon

GitHub (github.com)

Thanks @baris that option worked like a charm.

@baris Thank you for the quick fix! It works now.