@psychobunny Sure. I'll gather some data and make an issue now. Thanks for looking into this!

Hi
I'm trying to get this plugin created by @psychobunny to work with the latest nodebb 1.6.1

It appears to be semi-abandoned -- working with an old 0.4.3 nodebb version. Has anyone had success with a more recent build?

I have used nvm to install the plugin, and modified the page.hbs however this doesn't appear to have changed anything.

Suggestions on how to accomplish comments with latest node for latest ghost?

Thanks for the welcome back Something must have been wonky with my system, I was having weird issues with mongo so I reinstalled.

Everything went smoothly this time.

Still, the service will not work as simple with --no-daemon I tried it again. With forking I don't have to omit --no-daemon it works with this single change.

All is well now, but the doc needs to get cleaned up for that.

AH! the docs show -no-daemon not --no-daemon let me try sec

No dice. Keeping to forking

I reinstalled mongodb, and did the setup again. It did spit out a password this time. So 1/2 is fixed.

It still shows the:

connection to NodeBB has been lost, attempting to reconnect...

Weird. I was able to login a single time, then it kicked me out, now the same pw does nothing... this is kinda ridiculous

Hi
I installed nodebb a while back without issue, now on a new server trying out latest version & having issues.

so some info:

nodebb version: 1.6.1
nodejs version: 6.11.4
nginx version: 1.10.3

I followed the guide for my OS ubuntu 16.04.2 from here.

note: the systemd service type is incorrectly assumed as simple. It should be forking instead because the process forks a child. I modified and have the processes running.

Cool, execpt two problems

On: ./nodebb setup I see that admin acct creation is skipped... how do I login as admin?

Also: I see connection to NodeBB has been lost, attempting to reconnect... on the homepage and the spinning blobs in nav bar. How to fix?

I have standard nginx config file:

server {
    listen 80;

    server_name shout.frommyserver.com;

    location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Host $http_host;
        proxy_set_header X-NginX-Proxy true;

        proxy_pass http://127.0.0.1:4567;
        proxy_redirect off;

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

    location ~ /.well-known {
        allow all;
    }
}

What am I missing here?

Buddy I'm not following at all. The letsencrypt files are in the .well-known which are inside of the /var/www/nodebb webroot.

I added the try_files $uri =404;

It says "The client lacks sufficient authorization"

I've been through this procedure at least a dozen times now. Minutes prior to attempting with nodebb, I used it with discourse & flarum without issue. There's some sort of goof, but I'm not seeing it yet.

Thanks for the reply.

addition:

Okay it's fixed. The verification fails if using a symlink. I should have realized that wouldn't work. Just another goof. Removed the symlink and moved the folder.

Yep , so now I'm on SSL support.

I have this in my serverblock:

location /.well-known/acme-challenge {
root /var/www/nodebb;
}
}

& issue this command at /opt/letsencrypt

./letsencrypt-auto certonly -a webroot --webroot-path=/var/www/nodebb -d node.mydomainaddy.com

I get this error:

Domain: node.mydomainaddy.com
Type:   unauthorized
Detail: Invalid response from http://node.mydomainaddy.com/.well-
known/acme-challenge/-GpRyhKl3iHOn7CPvo-y8495N-VMBgmboTHGK28TngY
[711.211.717.413]: 403

nginx log says:
failed permission denied.

xenial beta 2

Yes, I installed mongodb. I've got it all sorted. Thanks for replying.

Hi,

I'm trying to install on ubuntu I went through the install guide, but am having issues connecting to the mongodb. I've issued this command:

> db.createUser( { user: "nodebb", pwd: "<Enter in a secure password>", roles: [ "readWrite" ] } )

However there is no success when attempting to connect.

I type:

mongo -u user -p password

and it will not authenticate

I've also tried starting the

node app --setup

& it fails to authenticate.

After creating a nginx vhost, and creating a symbolic link to the directory /var/www/nodebb, chown: to webuser, this is the error in nginx logs

/var/www/nodebb/" failed (13: Permission denied)

So it seems this is related to the lack of database connection. I have parsed the conf files of mongodb & nodebb but nothing is popping out.

Any clues?

Thanks

addition:

I noticed with the webinstaller it defaults to creation of database (0), I kept this default. Was I supposed to replace this with anything else? When I run the node app --setup it shows the same (0) default, so I didn't think that was an issue.

Here is the output from that command

This looks like a new installation, so you'll have to answer a few questions about your environment before we can proceed.
Press enter to accept the default setting (shown in brackets).
URL used to access this NodeBB (http://node.mydomainaddy.com)
Please enter a NodeBB secret (ec0fa747-0fa5-4e83-acf3-d1e470a0122a)
Which database to use (mongo)

2/4 13:11 [7771] - info: Now configuring mongo database:
Host IP or address of your MongoDB instance (127.0.0.1)
Host port of your MongoDB instance (27017)
MongoDB username (webeindustry)
Password of your MongoDB database
Which database to use (0)
Configuration Saved OK
2/4 13:12 [7771] - error: NodeBB could not connect to your Mongo database. Mongo returned the following error: auth failed
2/4 13:12 [7771] - warn: NodeBB Setup Aborted.
MongoError: auth failed
at Function.MongoError.create (/root/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/error.js:31:11)
at commandCallback (/root/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:1136:66)
at Callbacks.emit (/root/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:116:3)
at null.messageHandler (/root/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:291:23)
at Socket.<anonymous> (/root/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:285:22)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
at readableAddChunk (_stream_readable.js:153:18)
at Socket.Readable.push (_stream_readable.js:111:10)
at TCP.onread (net.js:531:20)

Okay it was my goof, I replaced the (0) with "mongo" it's now success in process of creating admin user.

I'm still getting the 404 error, the root directory ~/nodebb is the webroot, or is this not correct?

So it resolves when using the 4567 port, I must setup a reverse proxy to push this through 80? Something must be amiss.

Apparently that is standard behavior for nodebb, so I added the reverse proxy.

All issues resolved.