Sorry for necroposting, but it looks like the spoiler plugin got a problem with lists at the current versionof nodebb.

:::

- some
- items
- here

:::

Issue confirmed - good catch.

As far as I can see nginx doesn't touch the headers (if not explicitly told to do so) as it's just proxying stuff...

Update:

Got around the issue using:

 location ~ \.jst {
                add_header              Content-Type    application/javascript;
                proxy_pass              http://board;
        }

Not nice, but for now it's a solution I am able to live with on that vhost even with
nginx.conf having set add_header X-Content-Type-Options nosniff;

@julian it actually worked.

Thanks a ton. Lesson learned: 3 o' clock in the morning isn't good for migration stuff.

Hi guys,

I got a nasty problem with nodebb and nginx reverse proxying as nodebb logs every IP as 127.0.0.1
Any ideas what I'm doing wrong?

config.json

{
   "url":"http://board.domain.com",
   "use_port": false,
   "secret":"some secret",
   "mongo":{
      "username":"",
      "host":"databasehost",
      "password":"mypw",
      "port":"27017",
      "database":"nodebb"
   },
   "database":"mongo"
}

nginx:

server {
        listen 80;

        server_name board.domain.com;
        return 301 https://$host$request_uri;
}

upstream board {
        server 127.0.0.1:4567;
}

server {
        listen 443 ssl http2;
        gzip off;

        ssl on;
        ssl_certificate /path/to/fullchain.pem;
        ssl_certificate_key /path/to/privkey.pem;
        ssl_dhparam ssl/dhparam-board.pem;

        server_name board.domain.com;

        access_log syslog:server=syslog:12301 graylog2_format;
        error_log syslog:server=syslog:12302;


        location / {
                proxy_set_header                X-Real-IP $remote_addr;
                proxy_set_header                X-Forward-For $proxy_add_x_forwarded_for;
                proxy_set_header                X-Forward-Proto http;
                proxy_set_header                Host $http_host;
                proxy_set_header                X-Nginx-Proxy true;

                proxy_pass                      http://board;
                proxy_redirect off;

                # Socket.IO
                proxy_http_version              1.1;
                proxy_set_header                Upgrade $http_upgrade;
                proxy_set_header                Connection "upgrade";

        }


}

Okay guys, I got a solution that works somehow: I managed to dig out an old docker image vpetersson/nodebb which actually is 1.0.3
Using an external mongodb I could set up a running version compatible with the importer mentioned above and actually do the import. After having the import done, I could throw away the container and using a new/fresh install writing config.json by hand and running the updater (./nodebb upgrade)

Sounds like some dirty work right? But it's the easiest/fastest way I found.

I'm a bit lost here as it looks like there is no sane way of migration possible.

@Giggiux NodeBB 1.0.3 seems to need some older version of nodejs or some socket.io jazz being messed up as it denies login complaining about an invalid csrf token. Couldn't resolve that so far.

Hi guys,

I am currently running some myBB board which is a bit old-fashioned and I'd like to replace it with nodeBB as it seems like nodeBB fits my needs a bit better than the old board;

Is there some way to import the myBB data in some way?

All I have found was some outdated importer that requires some version 1.0.3 of nodeBB which I couldn't get to work.

Cheers
Rei