@pitaj great! This is what I am looking for. And you understood it even though I wrote it wrong. Actually I would ask for ./nodebb upgrade --series but a config option is much better. Thank you! It would be great if you could include this option in the documentation.

@baris 1gb ram is a lot.. we are running our forum on a shared host, so I can not increase the amount of ram.

Nodebb is running very smoothly and super fast there and we get a lot of positive feedback from our users. Our complete userbase is about 600 users big and we never had a performance issue in about 3 years.

I assume that the needed ram could be a problem for a lot of nodebb users. Do you think it would be possible to make the --series option available for the build function ./nodebb build --series ? If yes, where should I place this request?

Hi @baris!
Great, the build fininshed with ./nodebb build --series. Thanks!

I will keep this command. After that I tried again ./nodebb upgrade and monitored with top the ram an CPU usage. The build process broke with an error
Error occurred during upgrade: Error: ENOMEM: not enough memory, read
I got this error the first time. In all my other attemps no error occured.

How much ram is recommended for the usage of nodebb?

Hi guys,
I tried to upgrade Nodebb from v1.12.2 to v1.13.3. After ./nodebb upgrade everything is fine except the build process, see screenshot for details. The process never ends after templates. I had a look in the folder and the data is there, but if I stop the process the frontend is broken.

The road to this point was quite bumpy. It took 3-4 attempts to come to this points. I had to clear a few npm-errors with missing dependencies. I tried to roll back completely from a backup, but the result is the same. I tried to upgrade to v1.14.x but the result is still the same.

System data:
OS: CentOS 7
Node v12.19.0
npm 6.14.8

Does anybody know how to resolve this problem?

Thanks for any help!
Christian

Great Idea! I took your solution and added a few lines of CSS to hide the downvote arrow and remove the whitespace.

// Change the icon for votes
span.votes {
    // not voted is outline heart
    .fa-chevron-up:before {
        content: "\f08a";        
    }
    // upvoted is solid heart
    .upvoted .fa-chevron-up:before {
        content: "\f004";
    }
}
// hide the downvote element to remove whitespace
a[component="post/downvote"] {
    display: none;
}
// reduce margin of post-submenue for alignment 
.topic .moderator-tools {
    margin-left: 0px;
}

@PitaJ I have exactly the same Problem. Custom Javascript is gone after updating to 1.7.3. Custom JS und header tab are empty. Is there a possibility to recover that code?

Thank you, guys! npm i was the solution.

Hello everybody,

I'm trying to upgrade nodeBB from 1.6.1 to 1.7.3. After git fetch and git reset --hard origin/v1.7.x I tried to run ./nodebb upgrade, but I get the following error message:

package.json not found.
Populating package.json...
OK
module.js:538
    throw err;
    ^

Error: Cannot find module 'graceful-fs'
    at Function.Module._resolveFilename (module.js:536:15)
    at Function.Module._load (module.js:466:25)
    at Module.require (module.js:579:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/path-to-nodebb/NodeBB/src/file.js:10:16)
    at Module._compile (module.js:635:30)
    at Object.Module._extensions..js (module.js:646:10)
    at Module.load (module.js:554:32)
    at tryModuleLoad (module.js:497:12)
    at Function.Module._load (module.js:489:3)

Thanks for any help!
Christian

Thank you @PitaJ and @baris ! It was the plugin. I had installed the 1.2.1, but it does not worked. I uninstalled the plugin and registration i working fine again.

@pitaj here is the nodebb-log. Actually nodebb crashes after submitting the register form.

17/10 20:53:30 [11178] - error:  TypeError: Cannot read property 'username' of undefined
    at /home/user/nodebb/NodeBB/node_modules/nodebb-plugin-registration-notification/library.js:78:52
    at /home/user/nodebb/NodeBB/node_modules/async/dist/async.js:3861:9
    at /home/user/nodebb/NodeBB/node_modules/async/dist/async.js:421:16
    at iterateeCallback (/home/user/nodebb/NodeBB/node_modules/async/dist/async.js:928:24)
    at /home/user/nodebb/NodeBB/node_modules/async/dist/async.js:906:16
    at /home/user/nodebb/NodeBB/node_modules/async/dist/async.js:3858:13
    at /home/user/nodebb/NodeBB/src/database/mongo/sorted.js:64:5
    at handleCallback (/home/user/nodebb/NodeBB/node_modules/mongodb/lib/utils.js:120:56)
    at /home/user/nodebb/NodeBB/node_modules/mongodb/lib/cursor.js:860:16
    at handleCallback (/home/user/nodebb/NodeBB/node_modules/mongodb-core/lib/cursor.js:171:5)
    at setCursorDeadAndNotified (/home/user/nodebb/NodeBB/node_modules/mongodb-core/lib/cursor.js:505:3)
    at nextFunction (/home/user/nodebb/NodeBB/node_modules/mongodb-core/lib/cursor.js:651:7)
    at Cursor.next [as _next] (/home/user/nodebb/NodeBB/node_modules/mongodb-core/lib/cursor.js:692:3)
    at fetchDocs (/home/user/nodebb/NodeBB/node_modules/mongodb/lib/cursor.js:856:10)
    at /home/user/nodebb/NodeBB/node_modules/mongodb/lib/cursor.js:879:7
    at handleCallback (/home/user/nodebb/NodeBB/node_modules/mongodb-core/lib/cursor.js:171:5)
    at nextFunction (/home/user/nodebb/NodeBB/node_modules/mongodb-core/lib/cursor.js:682:5)
    at /home/user/nodebb/NodeBB/node_modules/mongodb-core/lib/cursor.js:593:7
    at queryCallback (/home/user/nodebb/NodeBB/node_modules/mongodb-core/lib/cursor.js:253:5)
    at /home/user/nodebb/NodeBB/node_modules/mongodb-core/lib/connection/pool.js:469:18
    at _combinedTickCallback (internal/process/next_tick.js:95:7)
    at process._tickCallback (internal/process/next_tick.js:161:9)
17/10 20:53:30 [11178] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
17/10 20:53:30 [11178] - info: [app] Database connection closed.
17/10 20:53:30 [11178] - info: [app] Web server closed to connections.
17/10 20:53:30 [11178] - info: [app] Shutdown complete.
17/10 20:53:37 [8701] - info: Initializing NodeBB v1.6.1 http://my.domain.de
17/10 20:54:03 [8701] - info: [socket.io] Restricting access to origin: http://my.domain.de:*
17/10 20:54:07 [8701] - info: Routes added
17/10 20:54:07 [8701] - info: NodeBB Ready
17/10 20:54:07 [8701] - info: Enabling 'trust proxy'
17/10 20:54:07 [8701] - info: NodeBB is now listening on: 0.0.0.0:63536

Hello everyone,

I have a problem with the registration. No registration could be completed. Everything is fine (inline validation etc.) till the submit-button is pressed. After that, the page reloads and the following error message is shown:

Registrierungsfehler
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>502 Proxy Error</title> </head><body> <h1>Proxy Error</h1> <p>The proxy server received an invalid
 response from an upstream server.<br />
 The proxy server could not handle the request <em><a href="/register">POST&nbsp;/register</a></em>.<p> Reason: <strong>Error reading from remote server</strong></p></p> <hr> <address>Apache/2.2.15 (CentOS) Server at my.domain.de Port 80</address> </body></html>

and this error is in the browser console:

jquery.js:9566 POST http://my.domain.de/register 502 (Proxy Error)
send	@	jquery.js:9566
ajax	  @	  jquery.js:9173
e.fn.ajaxSubmit	@	jquery.form.min.js:7
(anonymous)	@	register.js?v=4r12ck8gj25:1
(anonymous)	@	register.js?v=4r12ck8gj25:1
i.onack	@	socket.io.js:2
i.onpacket	@	socket.io.js:2
(anonymous)	@	socket.io.js:2
i.emit	@	socket.io.js:1
i.ondecoded	@	socket.io.js:1
(anonymous)	@	socket.io.js:2
i.emit	@	socket.io.js:1
f.add	@	socket.io.js:1
i.ondata	@	socket.io.js:1
(anonymous)	@	socket.io.js:2
i.emit	@	socket.io.js:1
i.onPacket	@	socket.io.js:1
(anonymous)	@	socket.io.js:1
i.emit	@	socket.io.js:1
i.onPacket	@	socket.io.js:2
i.onData	@	socket.io.js:2
ws.onmessage	@	socket.io.js:2

and on the serverside i have these errors:

[Tue Oct 17 12:33:59 2017] [error] [client 2003:61:4962:1333:c54c:4556:b5aa:ddac] (20014)Internal error: proxy: error reading status line from remote server localhost, referer: http://my.domain.de/register
[Tue Oct 17 12:33:59 2017] [error] [client 2003:61:4962:1333:c54c:4556:b5aa:ddac] proxy: Error reading from remote server returned by /register, referer: http://my.domain.de/register
[Tue Oct 17 12:38:23 2017] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:63536 (*) failed
[Tue Oct 17 12:38:24 2017] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:63536 (*) failed
[Tue Oct 17 12:38:59 2017] [error] [client 2003:61:4962:1333:c54c:4556:b5aa:ddac] (20014)Internal error: proxy: error reading status line from remote server localhost, referer: http://my.domain.de/register
[Tue Oct 17 12:38:59 2017] [error] [client 2003:61:4962:1333:c54c:4556:b5aa:ddac] proxy: Error reading from remote server returned by /register, referer: http://my.domain.de/register

I'm pretty sure, that the registration was working before I upgraded to 1.6.0 Did you changed there anything in this process?

Everything else is working fine. Creating posts, chat, upload files, upload and change profile images etc.

On the serverside I have to use not the perfect configuration with apache 2.2 (without mod_wstunnel), but it worked pretty well.

Thanks for any help,
Chris

Thank you @PitaJ and @julian for your support! Everything works fine now.

The error was because of a wrong security option in the settings and the speed of sendmail increased by itself. Probably there was a problem on the shared server during my first test.

Keep up the great work! NodeBB is really great!

Hi @PitaJ, I did the Upgrade to 1.6.1 and after a few hickups nodebb can send mails again, but only with the internal mailserver. The external option is still broken. Sending Mails via the internal mailserver is quite slow.

Here is the Error-Message, which I get when I try the externl mailserver option:

io: 2 on [ { type: 2,
    nsp: '/',
    id: 14,
    data: [ 'admin.email.test', { template: 'welcome' } ] } ]
12/10 12:38:27 [18738] - error:  Error: 140483857790752:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../deps/openssl/openssl/ssl/s23_clnt.c:797:

@pitaj thank you for the information and I hope that the fix will work for us, too!

I restarted nodebb and run ./nodebb build before I started again with ./nodebb dev. The initializing-message in the startup-log is correct und it shows the same defined url as in the config.json and not localhost. When I try to send a testmail or try to invite a new user, I get always the same error-message as shown in my initial post.

Why does nodebb act as localhost when sending mails and why does it looks for certificates?

@julian it doesn't matter. The error is the same with built the in email-service or with the new external email server. As external email server we use the custom option with credentials of our emailprovider. The config.json is correct. As url is our complete domain (with http://) specified and not localhost. And as you can see, we are not using https for nodebb.

After solving the problem with the install/uninstall-loop of plugins and the not working new topic button yesterday https://community.nodebb.org/topic/11303/after-upgrade-from-1-5-x-to-1-6-0-new-topic-does-not-work/18 I got a new problem today...

Emails can not be sent anymore. Till yesterday emails worked. Today I got errors when I want to send emails:

4/10 17:10:38 [28675] - error:  Error: Hostname/IP doesn't match certificate's altnames: "Host: localhost. is not in the cert's altnames: DNS:*.internalcname.hoster.de, DNS:internalcname.hoster.de"
    at Object.checkServerIdentity (tls.js:221:17)
    at TLSSocket.<anonymous> (_tls_wrap.js:1104:29)
    at emitNone (events.js:105:13)
    at TLSSocket.emit (events.js:207:7)
    at TLSSocket._finishInit (_tls_wrap.js:628:8)
    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:458:38)

The DNS-Part in the error-message in not the configured url in the config.json of nodebb. It is the internal cname of the webspace.

I have seen that you are working on an Update 1.6.1 for next week and there is a bugfix planned regarding the smtp emailer https://github.com/NodeBB/NodeBB/issues/5951 Will this bugfix adress my issues too or do I have a different problem?

Thanks for any help!

@pitaj yes, I tried ./nodebb build several times, but I always used ./nodebb dev to start.

I tried it once more as you said. ./nodebb start aborted with the message to run ./nodebb upgrade. After the upgrade and another ./nodebb start I can post and answer again!

I don't know why an how, but it works again. hopefully not only for a short time.

Thanks for you help!

Hi @julian, hi @PitaJ ,

finally I could downgrade npm to Version 4.6.1. I reinstalled all plugins and the persona theme, but I can still not open new topics or answer on topics. When I try it with the standard composer plugin I only get a 404 for the composer.tpl, as posted in a former post. With redactor activated I get an error in the browser console:

client.js:105 Uncaught TypeError: Cannot read property 'composeRouteEnabled' of undefined
    at client.js:105
    at dispatch (jquery.js:5206)
    at g.handle (jquery.js:5014)
    at Object.trigger (jquery.js:8201)
    at jquery.js:8269
    at Function.each (jquery.js:362)
    at D.fn.init.each (jquery.js:157)
    at D.fn.init.trigger (jquery.js:8268)
    at postTools.js:222
    at y (postTools.js:374)

Any Idea what I could do? Can I downgrade nodebb to 1.5.3?

Thanks for any help!

@pitaj and what do you think about the issue with new topics and answers? Do you have any idea on that?

@Anjin Did you have the same issues with installing/uninstalling plugins?