Admin Panel Broken

scottalanmiller

@scottalanmiller the nodebb is running on 8080. For reason I don' know, the nodebb always runs on port 8080 despite the setting in config.json.

If you are still working on getting NodeBB to run on the correct port as specified by the config file, why do you have the file set to three ports? Start with just getting one working, as only one is working anyway.

scottalanmiller

@julian said in Admin Panel Broken:

That's a little odd, it doesn't sound like you're running a regular VPS then, if you can't control the port? What service are you using?

VPS by definition couldn't cause that problem. A VPS you'd always be able to control the port.

scottalanmiller

@Kinchtwck said in Admin Panel Broken:

What makes it harder to debug is that the log doesn't show up any error.

What does netstat -tulpn tell us when you clean up the ports list and restart NodeBB?

julian

@scottalanmiller Yes indeed, that's why I said it doesn't sound like it was a VPS

Sadly we're fairly limited in terms of AWS experience, so I can't really help there...

scottalanmiller

@julian said in Admin Panel Broken:

Sadly we're fairly limited in terms of AWS experience, so I can't really help there...

Nothing to know there. AWS is "just a server" like any other. That AWS does the hosting doesn't change things at the OS level. It's the same as a physical server.

Kinchtwck

@PitaJ I tried only initiate without SSL but the result was the same

Kinchtwck

@scottalanmiller So previously, before updating, I ran the nodebb on 4567, 4568,4569 and pass the 443 proxy to these 3 with Nginx. Now, despite the config.json, I have to forward to 8080 which is the port that the NodeBB is on. I might try to initiate another AWS instance with the same setting to see how it goes.

tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      3215/nginx      
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      2944/node       
tcp        0      0 127.0.0.1:21            0.0.0.0:*               LISTEN      608/vsftpd      
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      928/sshd        
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      1111/sendmail: MTA:
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      3215/nginx      
tcp        0      0 0.0.0.0:27017           0.0.0.0:*               LISTEN      1294/mongod     
tcp        0      0 127.0.0.1:587           0.0.0.0:*               LISTEN      1111/sendmail: MTA:
tcp6       0      0 :::22                   :::*                    LISTEN      928/sshd        
tcp6       0      0 :::9000                 :::*                    LISTEN      1049/hhvm       
udp        0      0 0.0.0.0:42932           0.0.0.0:*                           544/dhclient    
udp        0      0 0.0.0.0:68              0.0.0.0:*                           544/dhclient    
udp6       0      0 :::59961                :::*                                544/dhclient

scottalanmiller

@Kinchtwck that is SO weird, because that's not a default, and doesn't appear in your config. Maybe do a ...

grep 8080 -R *

Kinchtwck

@scottalanmiller Thanks, I figured out the issue with the dashboard. In the error.log of nginx, it shows that

  /var/lib/nginx/proxy/8/83/0000000838" failed (13: Permission denied) while reading upstream

Even though the permission to this folder is valid, I am still not able to read the file. I have to rename the folder and restart the nginx according to Permission denied while reading upstream. But the port issue remains unresolved.

scottalanmiller

@Kinchtwck said in Admin Panel Broken:

Even though the permission to this folder is valid, I am still not able to read the file. I have to rename the folder and restart the nginx according to Permission denied while reading upstream. But the port issue remains unresolved.

What OS are you on? Perhaps SELinux is an issue for you?

Kinchtwck

@scottalanmiller I am on Ubuntu 16.04. Not sure if that's an issue though but I haven't encountered any reading issue until this update.

scottalanmiller

@Kinchtwck said in Admin Panel Broken:

@scottalanmiller I am on Ubuntu 16.04. Not sure if that's an issue though but I haven't encountered any reading issue until this update.

No SELinux on Ubuntu so can't be the issue unless you added it manually

scottalanmiller

@scottalanmiller said in Admin Panel Broken:

@Kinchtwck that is SO weird, because that's not a default, and doesn't appear in your config. Maybe do a ...
grep 8080 -R *

Back to this... any output?

Kinchtwck

@scottalanmiller Below is the final output from the command

nodebb/node_modules/safe-buffer/README.md:server.listen(8080)
nodebb/node_modules/body/README.md:http.createServer(app).listen(8080)
nodebb/node_modules/body/README.md:}).listen(8080)
nodebb/node_modules/body/README.md:}).listen(8080)
nodebb/node_modules/body/README.md:}).listen(8080)
nodebb/node_modules/body/README.md:}).listen(8080)
nodebb/node_modules/secure-keys/package.json:  "_shasum": "f0c82d98a3b139a8776a8808050b824431087fca",
nodebb/node_modules/async-listener/test/core-asynclistener-nexttick-remove.simple.js:server.listen(8080, function() {
nodebb/node_modules/async-listener/test/core-asynclistener-only-add.simple.js:server.listen(8080, function() {
nodebb/node_modules/jimp/server.js:app.listen(8080);
nodebb/node_modules/jimp/server.js:console.log("Serving on http://127.0.0.1:8080");

julian

Yeah, that's not NodeBB, looks like you're launching jimp, the image manipulation tool...

scottalanmiller

@julian said in Admin Panel Broken:

Yeah, that's not NodeBB, looks like you're launching jimp, the image manipulation tool...

So weird, I wonder how that got installed in there!

scottalanmiller

This is the package that is firing up.

jimp

An image processing library written entirely in JavaScript.. Latest version: 1.6.0, last published: 2 months ago. Start using jimp in your project by running `npm i jimp`. There are 2382 other projects in the npm registry using jimp.

npm (www.npmjs.com)

Kinchtwck

@scottalanmiller @julian I'll try to remove that package. If it's not nodebb, how come that the server can render my website through nginx proxy with port 8080...

scottalanmiller

@Kinchtwck said in Admin Panel Broken:

@scottalanmiller @julian I'll try to remove that package. If it's not nodebb, how come that the server can render my website through nginx proxy with port 8080...

Maybe Jimp's libraries are hijacking something. It's super weird. Jimp does have a config built into server.js that fires it up on port 8080. But that should not be firing up at this time. It should not be activating.

Here is that file...

# cat server.js 
var express = require("express");
var app = express();

app.use(express.static(__dirname + '/browser'));

app.listen(8080);

console.log("Serving on http://127.0.0.1:8080");

scottalanmiller

@Kinchtwck said in Admin Panel Broken:

@scottalanmiller @julian I'll try to remove that package. If it's not nodebb, how come that the server can render my website through nginx proxy with port 8080...

It's present in my installation, too. It should be there, but it should not be running anything. That's the weird part. What is making it turn on its server?