Hi @yariplus ,

the forum runs on a subdomain, because there is a Wordpress-Site on the "normal" domain, which is by a different hoster, who is the DNS-Host (http://checkdomain.de), too. The nodeBB installation is hosted by http://uberspace.de and the SSL certificate is providec by letsencrypt. As a proxy I have to use Apache 2.2. This is the reason for the private Port, because Apache 2.2 can not handle websockets. Everything worked fine till i tried to switch to https. Here is the .htaccess of the Apache:

RewriteEngine On
RewriteRule ^(.*)$ http://localhost:63542/$1 [NC,P,L]

When I to switch zu https, there is a http an a https (socket.io) to the same Port. That is the reason why i want to use a separate port for socket.io, if this is possible.

Hope there is enough information now, if not, please tell me what you need.

thanks for your help!
best,
chris

@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?

Hi nodeBB-Community,

I want to provide my forum via https. In my hosting environment I have to use a direct connetion to a private opened port (e.g. 63542) for socket io to establish stable websocket-connection. I did this in the nodebb config.json in this way:

"socket.io": {
    "address": "subdomain.tld.com:63542"
}

Everything works fine and fast with http. When I switch to https I get for all requests to /socket.io/ net::ERR_CONNECTION_CLOSED
I still can use the forum and do a login but I always have the notification visible that the connection was lost and the forum is trying to re-establish the connection.

Has anybody a idea what I can do for a consistent SSL-Connection?

Thanks,
Chris

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 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