Skip to content
Sudonix

NodeBB 3.0 alpha1 : Error on install

Solved Configure
  • DownPWundefined

    Hello @phenomlab

    I want to test alpha1 for V3 for test JS, theme switcher, css themes, etc.

    I have upgraded my dev environnement to 2.8.1
    I follow this link : https://community.nodebb.org/post/89581

    So, hop !

    cd /path/to/your/nodebb
git rev-parse HEAD  # save this value in case you need to roll back  --- 727f879e5b1698fcf9bdbaca5181b28d0e9497fd
git fetch && git checkout bootstrap5
git reset --hard v3.0.0-alpha.1
./nodebb upgrade -mi

    But 😞

    nodebb@node:~$ cd /home/nodebb/nodebb/
nodebb@node:~/nodebb$ git rev-parse HEAD
727f879e5b1698fcf9bdbaca5181b28d0e9497fd
nodebb@node:~/nodebb$ git fetch && git checkout bootstrap5
error: impossible d'ouvrir .git/FETCH_HEAD: Permission non accordée
nodebb@node:~/nodebb$ su -
Mot de passe : 
root@node:~# cd /home/nodebb/nodebb/
root@node:/home/nodebb/nodebb# git fetch && git checkout bootstrap5
remote: Enumerating objects: 5, done.
remote: Counting objects: 100% (5/5), done.
remote: Total 5 (delta 4), reused 5 (delta 4), pack-reused 0
Dépaquetage des objets: 100% (5/5), 441 octets | 73.00 Kio/s, fait.
Depuis https://github.com/NodeBB/NodeBB
   cf7aa1941..71743affc  bootstrap5 -> origin/bootstrap5
La branche 'bootstrap5' est paramétrée pour suivre la branche distante 'bootstrap5' depuis 'origin'.
Basculement sur la nouvelle branche 'bootstrap5'
root@node:/home/nodebb/nodebb# git reset --hard v3.0.0-alpha.1
HEAD est maintenant à 4f70d19e1 chore: v3.0.0-alpha.1 :tada:
root@node:/home/nodebb/nodebb# ./nodebb upgrade -mi
Dependencies outdated or not yet installed.
Installing them now...

npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: nodebb@3.0.0-alpha.1
npm WARN Found: nodebb-plugin-emoji@4.0.6
npm WARN node_modules/nodebb-plugin-emoji
npm WARN   nodebb-plugin-emoji@"5.0.2" from the root project
npm WARN   2 more (@nodebb/nodebb-plugin-reactions, nodebb-plugin-emoji-android)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer nodebb-plugin-emoji@"^4.0.0" from @nodebb/nodebb-plugin-reactions@1.0.2
npm WARN node_modules/@nodebb/nodebb-plugin-reactions
npm WARN   @nodebb/nodebb-plugin-reactions@"^1.0.2" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: nodebb@3.0.0-alpha.1
npm WARN Found: nodebb-plugin-markdown@10.1.1
npm WARN node_modules/nodebb-plugin-markdown
npm WARN   nodebb-plugin-markdown@"11.0.2" from the root project
npm WARN   1 more (nodebb-plugin-extended-markdown)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer nodebb-plugin-markdown@"^10.0.0" from nodebb-plugin-extended-markdown@1.6.0
npm WARN node_modules/nodebb-plugin-extended-markdown
npm WARN   nodebb-plugin-extended-markdown@"^1.6.0" from the root project
npm ERR! code 128
npm ERR! An unknown git error occurred
npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/makeusabrew/bootbox.git
npm ERR! Warning: Permanently added 'github.com,140.82.121.3' (ECDSA) to the list of known hosts.
npm ERR! git@github.com: Permission denied (publickey).
npm ERR! fatal: Impossible de lire le dépôt distant.
npm ERR! 
npm ERR! Veuillez vérifier que vous avez les droits d'accès
npm ERR! et que le dépôt existe.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2023-01-05T21_47_28_777Z-debug-0.log
Error installing dependencies!
message: Command failed: npm install --omit=dev
stdout: null
stderr: null
/home/nodebb/nodebb/src/cli/package-install.js:138
                throw e;
                ^

Error: Command failed: npm install --omit=dev
    at checkExecSyncError (node:child_process:841:11)
    at Object.execSync (node:child_process:912:15)
    at Object.pkgInstall.installAll (/home/nodebb/nodebb/src/cli/package-install.js:129:9)
    at Object.<anonymous> (/home/nodebb/nodebb/src/cli/index.js:51:18)
    at Module._compile (node:internal/modules/cjs/loader:1126:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1180:10)
    at Module.load (node:internal/modules/cjs/loader:1004:32)
    at Function.Module._load (node:internal/modules/cjs/loader:839:12)
    at Module.require (node:internal/modules/cjs/loader:1028:19) {
  status: 128,
  signal: null,
  output: [ null, null, null ],
  pid: 1251,
  stdout: null,
  stderr: null
}

    An idea ?

    PW and WS Spirit alive

    0
  • phenomlabundefined

    @DownPW you should remove the plugins quoted in that list - for example

    nodebb-plugin-emoji@4.0.6

    Then try the upgrade process again.

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    0
  • DownPWundefined

    @phenomlab

    npm remove nodebb-plugin

    ?

    PW and WS Spirit alive

    DownPWundefined phenomlabundefined 2 Replies
    0
  • DownPWundefined

    @phenomlab

    test with npm remove nodebb-plugin-emoji@4.0.6

    npm remove nodebb-plugin-emoji@4.0.6
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: nodebb@3.0.0-alpha.1
npm WARN Found: nodebb-plugin-emoji@4.0.6
npm WARN node_modules/nodebb-plugin-emoji
npm WARN   peer nodebb-plugin-emoji@"^4.0.0" from @nodebb/nodebb-plugin-reactions@1.0.2
npm WARN   node_modules/@nodebb/nodebb-plugin-reactions
npm WARN     @nodebb/nodebb-plugin-reactions@"^1.0.2" from the root project
npm WARN   2 more (nodebb-plugin-emoji-android, the root project)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer nodebb-plugin-emoji@"^4.0.0" from @nodebb/nodebb-plugin-reactions@1.0.2
npm WARN node_modules/@nodebb/nodebb-plugin-reactions
npm WARN   @nodebb/nodebb-plugin-reactions@"^1.0.2" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: nodebb@3.0.0-alpha.1
npm WARN Found: nodebb-plugin-markdown@10.1.1
npm WARN node_modules/nodebb-plugin-markdown
npm WARN   peer nodebb-plugin-markdown@"^10.0.0" from nodebb-plugin-extended-markdown@1.6.0
npm WARN   node_modules/nodebb-plugin-extended-markdown
npm WARN     nodebb-plugin-extended-markdown@"^1.6.0" from the root project
npm WARN   1 more (the root project)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer nodebb-plugin-markdown@"^10.0.0" from nodebb-plugin-extended-markdown@1.6.0
npm WARN node_modules/nodebb-plugin-extended-markdown
npm WARN   nodebb-plugin-extended-markdown@"^1.6.0" from the root project
npm ERR! code 128
npm ERR! An unknown git error occurred
npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/makeusabrew/bootbox.git
npm ERR! git@github.com: Permission denied (publickey).
npm ERR! fatal: Impossible de lire le dépôt distant.
npm ERR! 
npm ERR! Veuillez vérifier que vous avez les droits d'accès
npm ERR! et que le dépôt existe.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2023-01-05T22_23_12_150Z-debug-0.log

    PW and WS Spirit alive

    phenomlabundefined 2 Replies
    0
  • phenomlabundefined

    @DownPW yes, exactly. You can then install the updated (and compliant) v3 versions after the upgrade process completed successfully.

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    0
  • phenomlabundefined

    @DownPW looks like a permissions issue?

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    0
  • DownPWundefined

    @phenomlab I’m on root maybe that

    EDit: nope idem on non root user

    PW and WS Spirit alive

    0
  • phenomlabundefined

    @DownPW can you try with just

    npm remove nodebb-plugin-emoj

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    0
  • DownPWundefined

    @phenomlab said in NodeBB 3.0 alpha1 : Error on install:

    npm remove nodebb-plugin-emoj

    nope

    PW and WS Spirit alive

    0
  • phenomlabundefined

    @DownPW can you provide an output of the currently installed plugins before upgrade?

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    0
  • DownPWundefined

    @phenomlab https://community.nodebb.org/topic/16721/nodebb-v3-0-0-alpha-1-an-alpha-release/29

    maybe a problem with depot permissions.
    I wait a answer by Pitag or other nodebb staff

    PW and WS Spirit alive

    0
  • phenomlabundefined

    @DownPW yes, I saw that this morning. You could still try and remove those plugins which aren’t compliant though.

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    0
  • DownPWundefined

    @phenomlab

    Hourra I’m on V3 🙂

    here the solution for installation :

    cd /path/to/your/nodebb
git rev-parse HEAD  # save this value in case you need to roll back  --- 727f879e5b1698fcf9bdbaca5181b28d0e9497fd
git fetch && git checkout bootstrap5
git reset --hard v3.0.0-alpha.3
npm config set legacy-peer-deps true
./nodebb upgrade -mi
./nodebb build
./nodebb start

    A lot of things doesn’t work with new Personna Bootstrap 5 like theme Switcher selector for example

    –> Could I count on you to help me evolve the things we created together for Persona5 or Harmony? Like footerbar, theme Switcher selector, welcome message with image change ?

    –> Other things, Harmony theme not include on alpha ?

    PW and WS Spirit alive

    0
  • phenomlabundefined

    @DownPW said in NodeBB 3.0 alpha1 : Error on install:

    A lot of things doesn’t work with new Personna Bootstrap 5 like theme Switcher selector for example

    It does work, but needs minor tweaks as the existing listener doesn’t work under bootstrap 5 as it did under bootstrap 3. Nothing major to fix.

    Of course you can count on me. I’ll be in the same journey 🙂

    Harmony isn’t available yet from what I’ve read - not until beta releases I think.

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    1
  • DownPWundefined

    @phenomlab said in NodeBB 3.0 alpha1 : Error on install:

    Of course you can count on me. I’ll be in the same journey

    ✈

    haha that doesn’t surprise me. Thank you again for that my friend 👍 ♥

    I still hesitate between staying under Persona 5 or Harmony.

    I will decide when I can test it

    PW and WS Spirit alive

    0
  • DownPWundefined DownPW has marked this topic as solved on
  • phenomlabundefined

    @DownPW I’m going to test harmony. I quite like the look. However, I did start a topic to discuss this. Would appreciate input

    https://sudonix.com/topic/397/nodebb-v3-and-harmony-theme

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    0
  • DownPWundefined

    @phenomlab

    37565bc6-3136-4ff4-b476-280934c48663-image.png

    PW and WS Spirit alive

    0
  • phenomlabundefined

    @DownPW very odd. I don’t recall setting permissions there but try now.

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    0
  • DownPWundefined

    @phenomlab Work now 😉

    PW and WS Spirit alive

    1

Did this solution help you?
Did you find the suggested solution useful? Why not buy me a coffee? It's a nice gesture, and a great way to show your appreciation 💗

  • DownPWundefined

    NodeBB socket with CloudFlare

    Unsolved Performance
    23
    1 Votes
    23 Posts
    2k Views
    phenomlabundefined

    @DownPW it’s your only realistic option at this stage.

  • mventuresundefined

    NodeBB: Opening the Composer for replies

    Solved Configure
    2
    0 Votes
    2 Posts
    122 Views
    phenomlabundefined

    @mventures Quick reply is basically exactly that. However, it’s possible to trigger the full composer as below

    82ca1209-31be-4a51-a641-9887b5a238b8-image.png

    Failing that, you’ll need to use the reply button in the sticky toolbar

    1d230bcb-ff8e-4756-94f7-6e2fb7a94bc4-image.png

  • DownPWundefined

    NodeBB Global Tchat : Forum with many users performance issues

    Solved Configure
    13
    5 Votes
    13 Posts
    497 Views
    DownPWundefined
    'use strict'; const winston = require('winston'); const user = require('../user'); const notifications = require('../notifications'); const sockets = require('../socket.io'); const plugins = require('../plugins'); const meta = require('../meta'); module.exports = function (Messaging) { Messaging.notifyQueue = {}; // Only used to notify a user of a new chat message, see Messaging.notifyUser Messaging.notifyUsersInRoom = async (fromUid, roomId, messageObj) => { let uids = await Messaging.getUidsInRoom(roomId, 0, -1); uids = await user.blocks.filterUids(fromUid, uids); let data = { roomId: roomId, fromUid: fromUid, message: messageObj, uids: uids, }; data = await plugins.hooks.fire('filter:messaging.notify', data); if (!data || !data.uids || !data.uids.length) { return; } uids = data.uids; uids.forEach((uid) => { data.self = parseInt(uid, 10) === parseInt(fromUid, 10) ? 1 : 0; Messaging.pushUnreadCount(uid); sockets.in(`uid_${uid}`).emit('event:chats.receive', data); }); if (messageObj.system) { return; } // Delayed notifications let queueObj = Messaging.notifyQueue[`${fromUid}:${roomId}`]; if (queueObj) { queueObj.message.content += `\n${messageObj.content}`; clearTimeout(queueObj.timeout); } else { queueObj = { message: messageObj, }; Messaging.notifyQueue[`${fromUid}:${roomId}`] = queueObj; } queueObj.timeout = setTimeout(async () => { try { await sendNotifications(fromUid, uids, roomId, queueObj.message); } catch (err) { winston.error(`[messaging/notifications] Unabled to send notification\n${err.stack}`); } }, meta.config.notificationSendDelay * 1000); }; async function sendNotifications(fromuid, uids, roomId, messageObj) { const isOnline = await user.isOnline(uids); uids = uids.filter((uid, index) => !isOnline[index] && parseInt(fromuid, 10) !== parseInt(uid, 10)); if (!uids.length) { return; } if (roomId != 11) { // 5 Is the ID of the ID of the global chat room. Messaging.getUidsInRoom(roomId, 0, -1); // Proceed as normal. } else { user.getUidsFromSet('users:online', 0, -1); // Only notify online users. } const { displayname } = messageObj.fromUser; const isGroupChat = await Messaging.isGroupChat(roomId); const notification = await notifications.create({ type: isGroupChat ? 'new-group-chat' : 'new-chat', subject: `[[email:notif.chat.subject, ${displayname}]]`, bodyShort: `[[notifications:new_message_from, ${displayname}]]`, bodyLong: messageObj.content, nid: `chat_${fromuid}_${roomId}`, from: fromuid, path: `/chats/${messageObj.roomId}`, }); delete Messaging.notifyQueue[`${fromuid}:${roomId}`]; notifications.push(notification, uids); } };
  • cagatayundefined

    Gettin Erors NodeBB

    Solved Configure
    7
    0 Votes
    7 Posts
    327 Views
    cagatayundefined

    @phenomlab no forum is working goods.
    there is no eror message since yestarday.

  • Sampo2910undefined

    NodeBB Mess / Mongo DB

    Solved Configure
    8
    4 Votes
    8 Posts
    341 Views
    phenomlabundefined

    @Sampo2910 🙂 You’ll get that error if the .json file isn’t updated for latest release compliance - but you can still install from the CLI by using npm install nodebb-plugin-whateveritis

  • phenomlabundefined

    NodeBB slow after DB recovery

    Solved Performance
    1
    5 Votes
    1 Posts
    249 Views
    No one has replied
  • JACundefined

    [NodeBB] custom Gravatar image not showing

    Solved Customisation
    6
    1 Votes
    6 Posts
    977 Views
    JACundefined

    @jac said in [NodeBB] custom Gravatar image not showing:

    @phenomlab said in [NodeBB] custom Gravatar image not showing:

    @jac are you using Custom ?

    Sure am mate 👍🏻

    Confirmed Fixed

  • JACundefined

    WordPress & NodeBB

    Solved WordPress
    6
    0 Votes
    6 Posts
    524 Views
    phenomlabundefined

    @jac That won’t matter. You just redirect at nginx or apache level and it’ll work. The generally accepted standard though is to use a subdomain.