@GarrettBryan the domain is correctly routed.
The only problem is at login/registration.
And I tried with the domain only too.

I wonder if is not a problem with the server time @PitaJ
Initially I login on localhost, which works correctly.
Then on Heroku could fail because the server is on a different time zone?

@GarrettBryan it works fine when on
hhub4.herokuapp.com
localhost:4567
But when I add custom domain as in the picture below and proxying with Cloudflare to https://hhub.online, I get that csrf-invalid.

@PitaJ

{
    "url": "https://hhub.online",
    "secret": "some-secret",
    "database": "mongo",
    "mongo": {
        "host": "127.0.0.1",
        "port": 27017,
        "username": "",
        "password": "",
        "database": "nodebb",
        "uri": "mongodb://user:[email protected]:port/db"
    },
    "port": "4567"
}

I'm not using any proxy, because Heroku supplies already custom domains and is used by Cloudflare.

@GarrettBryan thanks for suggestion, but it didn't worked.
The field was missing and even adding it, nothing changed.

Looks like this domain stuff is a dead end for me.

I've tried to setup NodeBB on a subdomain with the help of a proxy.
There was a sockets problem when accessing it with the proxy and I gave up.

I thought that if I place NodeBB on its own domain everything will be okay.
Unfortunately it works locally, but when uploaded to Heroku I can't login anymore due csrf-invalid error.

So I have to give up

After every page visit an item is added to the sessions collection in the database.
It doesn't seem right to me. Is this collection ever cleaned?

@PitaJ tried another install and with the same result.
If the domain is refreshed in the past 48 hours could trigger domain errors?

@PitaJ what happens if I delete all sessions documents from the database?

@PitaJ yes, of course.

Hi, as the title says, I can't login after I changed the domain.
Interestingly, not even when I sign up with a different account I can't login. Not even when the user is redirected after sign up.
Any ideas what could cause this?

And the message is:
We were unable to log you in, likely due to an expired session. Please try again

It looks like is a configuration problem. When I load the page, there is this network error:

socket.io.js:8 WebSocket connection to 'wss://example.com/socket.io/?EIO=3&transport=websocket&sid=zV8kYkx-87ULGIjGAAAF' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR

On Chrome's inspector window it says it was canceled.
But then it works normal.
So all I need is to bypass the first error... or even better, fix it.

Delaying the sockets start didn't solved the problem. So I'm still looking for the solution.

But I managed to start the server as it should.

PS: would've been great to have the option to close the topic.

@PitaJ the thing I never managed to start NodeBB on Heroku with web: node loader.js --no-daemon, but only with web: node app.js and maybe I wouldn't have this issue now.

@PitaJ NodeBB is installed on a server and I'm using a proxy to serve it.
Both servers are on Heroku on free Dynos. If nodeBB is sleeping, the proxy server will wake it up, but when it starts it throws a socket error and the proxy server displays the "Application error" page.
But in reality NodeBB server started okay.

How can I delay the sockets start?
I found this code block on start.js:

function (next) {
  var webserver = require('./webserver');
  require('./socket.io').init(webserver.server);

  if (nconf.get('runJobs')) {
    require('./notifications').startJobs();
    require('./user').startJobs();
  }
  webserver.listen(next);
}

All I want to obtain is to run the server first and 1-3 seconds later to start the sockets.
What I don't want is to rewrite in the src folder.

Alternatively I could overwrite in a plugin the Sockets.init function.
What do you suggest?

Great work @youhosi
I've forked your theme and adapted as needed.
Now I want to add some content on the user card.
I'm using Nicolas Silver's plugin which adds some custom fields to user's profile.
To import the fields, I've used with success in other locations this syntax:
<!-- IMPORT partials/account/custom_fields_flex.tpl -->

But it doesn't work on "templates/modules/usercard.tpl" file.
Any suggestion?

@PitaJ and who else may encounter this issue, here is how I solved it.

The root problem was the image format used for "Site Logo" in general/settings.
I've uploaded a png file and the information was not saved in the database, althoughthe fields remained filled across the sessions.
Once I've changed the site logo with a jpg file, the emails were properly formatted too.

@Nicolas is there a way I could import custom-fields-edit.tpl into user profile edit page?