Admin Panel Broken

scottalanmiller

@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.

https://www.npmjs.com/package/jimp

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?

julian

Probably executed it by mistake... @Kinchtwck how are you starting NodeBB?