@pitaj

Got it figured out. Basically, you have to form a "redirect chain" kinda. I think I was creating an infinite loop of redirection or excluding a specific case (www. for 443 and for 80 separately) in my above nginx config. I ended up having to redirect 80 http://www.domain.com, 80 http://domain.com AND 443 https://www.domain.com all to 443 https://domain.com and then that third block is where all the master logic for the activity goes, if that makes sense.

In my original post, I was combining too many of these cases into just 2 blocks. In addition, I also added location / {} and wrapped that around my return 301 statements.

This fixed the problem entirely with both the domain and the forum malfunctioning. Last but not least, I wanted to mention that I also added proxy_set_header X-Forwarded-Proto $scheme; to the main logic block near the other proxy_set settings, which fixed a csrf error as well. So we're all good now!

Very exciting stuff. I appreciate the quick replies and help. Happy to use NodeBB for my new site!

Hello,

I am considering NodeBB for a brand new forum website. It will be a true forum-based site for discussion on my field of work. There aren't many of this type for my field so I'm excited. I have 3 questions concerning NodeBB and please excuse my ignorance but I develop using C, assembly, and sometimes Python and have been out of the JS/Node space for some time:

1. Can you recommend me some hosting services which provide decent/reliable service where I could easily install NodeBB or that already have NodeBB as a pre-loaded option? I can find a ton of PHP hosts but I'm in the dark about Node hosts. This is going to be a small site funded by me at first which will probably grow but I currently cannot afford AWS/Azure.

2. How does NodeBB handle attachments? My forum will need to have the ability to upload zips, 7zs, and image files. Can NodeBB handle a good amount of attachments?

3. Is there an easy way to turn on or install a plugin for syntax highlighting in-post such as for a software dev community?
   Thank you. I've used this software before as I user and I think it looks and feels a lot better than phpBB and those older style of forums.

@yli-sazze Sweet mother of God, thank you so much for posting this for the Mongo folks!

I installed emailer-sendgrid plugin by julianlam on my NodeBB versions 1.12.2 which says its compatible with this version. However, when I go to the Plugins -> Emailer (Sendgrind) and click it, the /admin/plugins/emailer-sendgrid page just loads indefinitely and never actually comes up, ever. Do you know what could cause this and some troubleshooting steps? One thing I did try is I restarted NodeBB after I installed it and logged out and logged back in. I DID NOT do a rebuild/restart though.

Ok thanks everyone. Good news is I made a lot of progress on this today. This was both a version and permission issue.

It was a version issue because thats what was causing the syntax error itself.

It was a permission issue because I should not have needed sudo in order to run the upgrade process and since I was running sudo, it was using an alternate version of Node rather than the one that I had selected using nvm.

So, I was able to fully upgrade.

@PitaJ Thanks for your reply. Unfortunately this occurs with either 8 or 10.16.3. I use nvm so I just do a quick switch between them and I just tried 10.16.2 again and I get the same error.

By the way, is there a way to purge out the stuff that occurred in the upgrade script prior to it crashing? Im wondering if since I ran the original upgrade script on node 8 and it got a lot of the work done, then I hit the error, now I'm trying 10 but its after a bunch of the script already executed on 8, etc...

Or does the script just do a fresh start over every time it's executed?

I followed the update instructions using git from the official support page to update my NodeBB by doing git fetch, and then resetting to the master branch and so on...

Upon running the upgrade script ./nodebb upgrade , Tons of this happened all with success messages, then I finally got:

2019-10-20T07:24:49.049Z [4567/19137] - error: [build] Encountered error during build stepEACCES: permission denied, rmdir '/var/www/nodebb/myforums/build/public/plugins/nodebb-plugin-emoji-extended' {"errno":-13,"code":"EACCES","syscall":"rmdir","path":"/var/www/nodebb/myforums/build/public/plugins/nodebb-plugin-emoji-extended","stack":"Error: EACCES: permission denied, rmdir '/var/www/nodebb/myforums/build/public/plugins/nodebb-plugin-emoji-extended'"}
Error occurred during upgrade: Error: EACCES: permission denied, rmdir '/var/www/nodebb/myforums/build/public/plugins/nodebb-plugin-emoji-extended'
2019-10-20T07:24:49.053Z [4567/19137] - error: uncaughtException: EACCES: permission denied, rmdir '/var/www/nodebb/myforums/build/public/plugins/nodebb-plugin-emoji-extended'
Error: EACCES: permission denied, rmdir '/var/www/nodebb/myforums/build/public/plugins/nodebb-plugin-emoji-extended' {"error":{"errno":-13,"code":"EACCES","syscall":"rmdir","path":"/var/www/nodebb/myforums/build/public/plugins/nodebb-plugin-emoji-extended"},"stack":"Error: EACCES: permission denied, rmdir '/var/www/nodebb/myforums/build/public/plugins/nodebb-plugin-emoji-extended'","exception":true,"date":"Sun Oct 20 2019 07:24:49 GMT+0000 (UTC)","process":{"pid":19137,"uid":1000,"gid":1000,"cwd":"/var/www/nodebb/myforums","execPath":"/home/gonia119/.nvm/versions/node/v8.16.2/bin/node","version":"v8.16.2","argv":["/home/gonia119/.nvm/versions/node/v8.16.2/bin/node","/var/www/nodebb/myforums/nodebb","upgrade"],"memoryUsage":{"rss":169865216,"heapTotal":124071936,"heapUsed":90725128,"external":19303888}},"os":{"loadavg":[1.15283203125,0.48291015625,0.27099609375],"uptime":5773},"trace":[]}
2019-10-20T07:24:49.054Z [4567/19137] - error: [build]          requirejs modules  build failed
2019-10-20T07:24:49.058Z [4567/19137] - error: [build]                  templates  build failed
2019-10-20T07:24:49.060Z [4567/19137] - error: [build]                  languages  build failed
2019-10-20T07:24:54.127Z [4567/19137] - error: [build]                     sounds  build failed

Now, when I do sudo ./nodebb upgrade I get:

admin@forums:/var/www/nodebb/myforums$ sudo ./nodebb upgrade
/var/www/nodebb/myforums/src/cli/package-install.js:23
        var packageContents = { ...oldPackageContents, ...defaultPackageContents, dependencies: { ...oldPackageContents.dependencies, ...defaultPackageContents.dependencies } };
                                ^^^

SyntaxError: Unexpected token ...
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:374:25)
    at Object.Module._extensions..js (module.js:417:10)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Module.require (module.js:354:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (/var/www/nodebb/myforums/src/cli/index.js:8:22)
    at Module._compile (module.js:410:26)
    at Object.Module._extensions..js (module.js:417:10)

I cannot get past this issue....

ENVIRONMENT INFORMATION:

Ubuntu 16.04.6 LTS
Node.js 8.16.2
Current NodeBB: Not sure because I cannot access my admin panel anymore... How can I get this info from the binary? I try ./nodebb version doesn't work...

Trying to upgrade to: Latest NodeBB stable.

I don't even know how to view my current version... Looked in the admin panel and on ssh I type ./nodebb --version or version and nothin.

After that, I can establish whether I need any further upgrades or not but as it stands, I did a ./nodebb upgrade which was successful.

I'm going to also have to check and see if I had used GitHub to get NodeBB to begin with, I can't remember if I did.

@PitaJ ok that's useful info thanks... Question... User @Trulore said this:

@trulore said in Skin display issue (noskin):

Thanks guys!

Changing the bootstrap url from "/latest" to "/3.3.7" in two places (src/client/account/settings.js and src/middleware/header.js) gave us an immediate fix to this problem.

And just random kudos for how easy it is to find and fix things in NodeBB. Definitely my favorite forum software!

I didn't have a /src/client/account/settings.js file but I did change my src/middleware/header.js file and its FIXED!!

Now, is this a hackish workaround that's going to break soon or is this actually a good fix for the problem? Thanks.

I've upgraded and am still having this issues. Can you please elaborate on "skins messing up" because that is not enough info for me to troubleshoot this. I tried switching skins and that didn't help, upgrade and restarting the forum, that didn't help. I'm just not sure what the problem is since I never customized anything related to themes or skins....

Hello,

So I came to my site one day and suddenly, the entire header/navbar area is completely out of whack. I have no idea how this happened because I didn't even touch any code up there or change any settings at all. Can someone point me to how to fix this? All it is is the default header with the small forum name... No images or anything. I do have Twitter cards code up there but I tried taking it out and that wasn't the problem.

You can see the problem on the forum: https://malwareanalysisforums.com/ Thanks.

Apologies if it's something simple... Been a while since I did web dev stuff.

@pitaj

Got it figured out. Basically, you have to form a "redirect chain" kinda. I think I was creating an infinite loop of redirection or excluding a specific case (www. for 443 and for 80 separately) in my above nginx config. I ended up having to redirect 80 http://www.domain.com, 80 http://domain.com AND 443 https://www.domain.com all to 443 https://domain.com and then that third block is where all the master logic for the activity goes, if that makes sense.

In my original post, I was combining too many of these cases into just 2 blocks. In addition, I also added location / {} and wrapped that around my return 301 statements.

This fixed the problem entirely with both the domain and the forum malfunctioning. Last but not least, I wanted to mention that I also added proxy_set_header X-Forwarded-Proto $scheme; to the main logic block near the other proxy_set settings, which fixed a csrf error as well. So we're all good now!

Very exciting stuff. I appreciate the quick replies and help. Happy to use NodeBB for my new site!

Hello,

So I'm on a fresh NodeBB install. DigitalOcean Droplet and I have configured Nginx as proxy server. Like several others, I'm receiving the above stated error as soon as I visit the board. I am no longer able to write anything to the boards basically but they do sorta half-work in that I can navigate and read stuff. I cannot save any settings or create new threads.

This is what I got:
Nginx Config:

# Default server configuration
#
server {
        listen 80;
        #listen 443;
        #listen [::]:80;
        server_name myforums.com www.myforums.com;
        return 301 https://myforums.com$request_uri; #NOTE: Also tried #scheme and other variants
}
server {
        # SSL configuration
        #
         listen 443 ssl;
         server_name myforums.com www.myforums.com;
        # listen [::]:443 ssl default_server;
        include snippets/letsencrypt.conf;
        include snippets/ssl.conf;
        root /var/www/nodebb/myforums;

        # Add index.php to the list if you are using PHP
        index index.html index.htm index.nginx-debian.html;




        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                # try_files $uri $uri/ =404;
                # Uncomment to enable naxsi on this location
                # include /etc/nginx/naxsi.rules
                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_pass http://127.0.0.1:4567/;
                proxy_redirect http://127.0.0.1:4567 https://myforums.com;

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

My config.json:

{
    "url": "https://myforums.com",
    "secret": "somesecret",
"bindaddress": "localhost",
    "database": "mongo",
    "port": 4567,
    "use_port":false,
    "mongo": {
        "host": "127.0.0.1",
        "port": "27017",
        "username": "myforums",
        "password": "somepass123",
        "database": "forumsdb"
    }
}

I have 2 problems:

1. No matter if I type in https://myforums.com or http://myforums.com , it redirects the user to https://www.myforums.com . I do not want the www.

2. The error message in the subject is happening when I go to my boards. I saw a StackOverflow response where the guy said to add listen port 443 to the first server block but for me, that makes the entire site go down completely.

I'm not sure what needs to be fixed here but something screwy is going on between my SSL, Nginx config, and NodeBB config. Thanks for any assistance. What I'm trying to accomplish here is have a HTTPS-ALWAYS NodeBB. Everything should be https. I dont care about www.