Latest Install

[webeindustry]

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?

[PitaJ]

So you're installing fresh? If so, when you run ./nodebb setup, it should ask you for DB info, URL, and admin username and password. The only case where it doesn't is if config.json already exists. In that case, it should run everything, and generate an admin username and password which it prints out after everything else is done, including the build.

[webeindustry]

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

[PitaJ]

You need to make sure that url in config.json is set to exactly the url at which you access the site.

[julian]

@webeindustry said in Latest Install:

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

Welcome back @webeindustry

The service type can be simple so long as you execute loader.js with --no-daemon. If you want to use forking you can, you can then omit --no-daemon. Logging is tougher then, as it wouldn't be managed by systemd.

[webeindustry]

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

[julian]

Is the systemd script starting app.js, or loader.js? Should be loader.js...