@julian said in Session Mismatch:

sort of like nginx captures it and removes it from the url as it proxies it.

That can't be the case, because NodeBB doesn't respond without the /forums. For example, if I put the IP and port into my address bar (http://192.168.0.10:4567/), I get a connection refused error, but http://192.168.0.10:4567/forums responds. Edit: This isn't to say that the sub-folder installation couldn't be the cause of the problem - just that NginX seems to be passing the URL correctly.

I'm kind of wondering if this has something to do with SSL.

@julian Also ... the location block is because I serve the URL from /forums on the reverse proxy. It is included in the proxy pass because NodeBB is also configured to respond to /forums (so, accessing it by the IP and Port directly from my network also requires appending "/forums"). I found that it must be set that way for various resource paths (CSS and script files, I think) to get served correctly.

@PitaJ

{
    "url": "https://www.example.net/forums",
    "secret": "88888888-8888-8888-8888-888888888888",
    "database": "redis",
    "port": 4567,
    "redis": {
        "host": "127.0.0.1",
        "port": "6379",
        "database": "0"
    }
}

@PitaJ I will grab the whole thing for you, tomorrow, if I remember, but the "url" value is "https://www.example.com/forums" and I think that's the only value that should have an impact, here.

@julian it was required to make this configuration work back in 1.0.x. Is there one or another of the two you would recommend removing? My only other option at this point seems to be to revert to the VM snapshot I made of 1.0.3, but that's going to mean losing about a week's worth of new posts, since I didn't notice this was broken after the upgrade.

@julian I'm getting this error. The forums work for people who were logged in before I upgraded (went from 1.0.3 to 1.2.1) but no one who wasn't logged in can do so and no new users can register. And as far as I can tell, I can't even temporarily disable the CSRF token as a work-around, which is pretty frustrating.

1. CONFIG.JSON URL value is correct, but involves a subdomain installation (/forums) and an HTTPS URL.

2. COOKIEDOMAIN was already blank, but I ran the redis script to clear it anyway.

3. This value was not present (because it was not in the original NGINX configuration document), but I added it and nothing changed. The NGINX config I use is given below. It's probably important to note that I use SSL for all incoming connections, and the URL value from my config.json includes https:// at the beginning. NGINX and NodeBB are run on the same server, so SSL is not used between them.

   location /forums {
           client_max_body_size 20M;
           proxy_set_header X-Real-IP $remote_addr;
           proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
           proxy_set_header Host $http_host;
           proxy_set_header X-NginX-Proxy true;
           proxy_set_header X-Forwarded-Proto $scheme;
   
           proxy_pass http://127.0.0.1:4567/forums;
           proxy_redirect off;
   
           # Socket.IO Support
           proxy_http_version 1.1;
           proxy_set_header Upgrade $http_upgrade;
           proxy_set_header Connection "upgrade";
   }
   

@julian Yeah, it's minified, obviously, but I figured the "ctrl+f" binding would be enough to locate the function in the full version.

And I thought 1.0.3 was the latest? Do you mean the weekly or master branch or something?

I noticed that threads weren't automatically retrieving new posts, so I checked the console and found these errors:

Uncaught TypeError: Cannot read property 'bind' of undefined (nodebb.min.js). The prettified function causing this error is below and the error occurs on the line with t.bind()

    function p() {
        require(["search", "mousetrap"], function(e, t) {
            $(".topic-search").on("click", ".prev", function() {
                e.topicDOM.prev()
            }).on("click", ".next", function() {
                e.topicDOM.next()
            });
            t.bind("ctrl+f", function(e) {
                if (config.topicSearchEnabled) {
                    var t = ajaxify.currentPage.match(/^topic\/([\d]+)/), n;
                    if (t) {
                        e.preventDefault();
                        n = t[1];
                        $("#search-fields input").val("in:topic-" + n + " ");
                        app.prepareSearch()
                    }
                }
            })
        })
    }

I just did a fresh server rebuild, so maybe I screwed something up, or maybe this has been happening for a while and I didn't notice.

@pichalite Thanks ... I should probably learn to check those.

My forum is installed in /forums and the subcategory links omit the primary directory, resulting in 404 errors.

@ViolentCrumble I just upgraded my NodeBB to 1.0.2 and updated the Imgur plugin as well and it's working fine for me, now. I don't think it will work with stock NodeBB (see @julian's comment about their backend). You need to use an external image image host via a plugin like the Imgur one.

@julian Definitely fixed for me. As always, thanks for all the effort you guys put into this project.

No announcement thread in the announcements section?

Congratulations, guys! NodeBB has come a long way.

So ... this forum is exhibiting exactly the behavior one of my users found on my own forum. First, large uploads result in this:

This one is an Nginx problem, and can be solved by setting client_max_body_size in your Nginx config. Unfortunately, that still leaves this one:

Both of these are from screenshots I just took on this forum, both also happen on my own (0.9.3), even after installing the imagemagick plugin that was suggested by @psychobunny.

Not sure exactly when this problem started, but it's happening with images that used to work on the same forum, prior to some upgrades (maybe 0.9.3, maybe 0.9.x in general).

@julian No. Not really sure what else I can do except to maybe rebuild the whole server. I'm just running the upstart script with ./nodebb start for now. IIRC, the major drawback to that was that it doesn't write the PID to a file and so you can't make an orderly stop to the process, which is not ideal, but it will work for me for now.

@julian deleted log file, rebooted, same error and log file does not exist.

Manual ./nodebb start creates log file.
Manual node loader.js --no-silent --no-daemon also creates log file.

It just wont do it from upstart for some reason.

Edit: Doesn't work even with chmod 777 on the output.log file and the containing directory. Really doesn't make any sense to me. Though on further consideration, it might have been broken by a package update from apt-get and I just didn't notice because I hadn't rebooted in a while.

@julian But that's not really possible. I can start it under my user account, even using the same command and it starts from the startup script after I changed it to ./nodebb start ... and it was working for months before I upgraded to 0.7.2 and just suddenly stopped because of it. And starting it from any other method does write output to /opt/nodebb/logs/output.log:

nodebb@NodeBB:/opt/nodebb/logs$ ls -la
total 20
drwxrwxr-x  2 nodebb nodebb 4096 Aug  4 06:55 .
drwxr-xr-x 10 nodebb nodebb 4096 Aug  4 07:28 ..
-rw-rw-r--  1 nodebb nodebb 6 Aug  4 06:51 .gitignore
-rw-rw-r--  1 nodebb nodebb 5021 Aug  4 07:28 output.log

I ran into so many problems after this upgrade that I just threw the whole instance away (mv /opt/nodebb /opt/nodebb_old) made a new directory and installed using the steps from https://docs.nodebb.org/en/latest/installing/os/ubuntu.html starting with the repository clone:

git clone -b v0.7.x https://github.com/NodeBB/NodeBB.git nodebb
cd nodebb
npm install --production
./nodebb setup

I ended up copying the old config.json file back into the new directory because I was too lazy to copy and paste the secret, but I am otherwise now running a brand spankin' new install of v0.7.2 and I hit the same problem. same EROFS error in /var/log/upstart/nodebb.log after I put the old /etc/init/nodebb.conf back.

I also have a minor problem with the persona theme (.taskbar CSS class has a width of 50% specified in stylesheet.css even after updating the theme to the latest from the ACP), a plugin that completely breaks the service whenever a topic is loaded (nodebb-plugin-topic-badges) and a plugin that tries to turn every link that starts with http:// into a YouTube embed (nodebb-plugin-youtube-lite).

The clean install did fix a problem I was having with the chat windows.

Nevermind. Updating the theme in the ACP broke the chat windows again, so that's the problem with that one.

I just updated to 0.7.2 and this plugin is throwing errors at me:

4/8 06:06 [1752] - error: TypeError: undefined is not a function
    at Object.TopicBadges.addThreadTools [as method] (/opt/nodebb/node_modules/nodebb-plugin-topic-badges/library.js:29:15)
    at /opt/nodebb/src/plugins/hooks.js:89:12
    at /opt/nodebb/node_modules/async/lib/async.js:269:13
    at iterate (/opt/nodebb/node_modules/async/lib/async.js:146:13)
    at Object.async.eachSeries (/opt/nodebb/node_modules/async/lib/async.js:162:9)
    at Object.async.reduce (/opt/nodebb/node_modules/async/lib/async.js:268:15)
    at fireFilterHook (/opt/nodebb/src/plugins/hooks.js:81:9)
    at Plugins.fireHook (/opt/nodebb/src/plugins/hooks.js:62:5)
    at Object.threadTools (/opt/nodebb/node_modules/async/lib/async.js:653:23)
    at /opt/nodebb/node_modules/async/lib/async.js:580:25

This happens when any topic is loaded with the addon enabled. Control panel reports 0.1.1 installed.

start on startup
stop on runlevel [016]

respawn

setuid nodebb
setgid nodebb

script
    cd /srv/www/mywebsite/nodebb
    node loader.js --no-silent --no-daemon
end script

This script (from https://docs.nodebb.org/en/latest/running/index.html) has been working for me forever on 0.6.x but is no longer starting NodeBB on startup. /var/log/upstart/nodebb.log contains this, repeated over and over again:

events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: EROFS, open '/opt/nodebb/logs/output.log'
    at Error (native)
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: EROFS, open '/opt/nodebb/logs/output.log'
    at Error (native)

Anyone have a clue what might be broken?
sudo start nodebb works as expected, as does ./nodebb start and node loader.js --no-silent --no-daemon works when I log in to the console. I replaced that line with ./nodebb start and it seems to work. Is this just a case of the docs being out of date or is this something I should be concerned about?

I noticed on 0.6.1 that moving a post into a different topic does not move that topic into the appropriate position on the recent page. I updated to 0.7.2 to make sure it's still a problem there. It does actually correctly list the last post time (e.g., "<avatar> replied 1 minute ago") but it keeps the topic that the reply was originally posted to above the new topic (so the first item in the list says "1 hour ago" and the second item says "2 hours ago" but the third item says "1 minute ago").

Not a really big deal, but I think it should promote the topic that the response was moved to, since that's actually where the new post is.

I haven't logged in for a while, but when I did I found a notification waiting. But when I click on the notification area, it kind of flashes and says there are no notifications:

It kind of seems like it's finding a notification for me and then possibly realizing it's old and removing it when I try to view it.