@pichalite said:
git rev-parse HEAD
0b35c81586d85bb916e9336daf52694f51b182c9
I just started a DigitalOcean server tonight and its a new install of everything.
I started the server in dev, uninstalled the problem plugin, ran ./nodebb upgrade and I'm getting the same problem. Even in package.json it says ''nodebb-rewards-essentials": "^0.0.8" the exact version that its saying to upgrade too.
I removed soundpack from package.json and now its telling me that I have another plugin out of date:
3/3 16:09 [4837] - info: Time: Thu Mar 03 2016 16:09:45 GMT-0500 (EST)
3/3 16:09 [4837] - info: Initializing NodeBB v1.0.0
3/3 16:09 [4837] - info: [database] Checking database indices.
[outdated] nodebb-rewards-essentials installed v0.0.6, package.json requires ^0.
3/3 16:09 [4837] - warn: One or more of NodeBB's dependent packages are out-of-d
3/3 16:09 [4837] - warn: ./nodebb upgrade
[cluster] Child Process (4837) has exited (code: 0, signal: null)
I've tried to update it, but I get the same error.
Why does A fresh install of NodeBB come with outdated packages that wont let it run?
@pichalite said:
./nodebb upgrade
I've done that several time:
./nodebb upgrade
Bringing base dependencies up to date... OK
Updating NodeBB data store schema.
3/3 15:51 [4436] - info: [database] Checking database indices.
3/3 15:51 [4436] - info: Beginning database schema update
3/3 15:51 [4436] - info: [2015/09/30] Converting default Gravatar image to default User Avatar skipped
3/3 15:51 [4436] - info: [2015/11/06] Gravatar removal skipped
3/3 15:51 [4436] - info: [2015/12/15] Chats upgrade skipped!
3/3 15:51 [4436] - info: [2015/12/23] Chats room hashes upgrade skipped!
3/3 15:51 [4436] - info: [2015/12/23] Adding theme to active plugins sorted set skipped!
3/3 15:51 [4436] - info: [2016/01/14] Creating user best post sorted sets skipped!
3/3 15:51 [4436] - info: [2016/01/20] Creating users:notvalidated skipped!
3/3 15:51 [4436] - info: [2016/01/23] Creating Global moderators group skipped!
3/3 15:51 [4436] - info: [2016/02/25] Social: Post Sharing skipped!
3/3 15:51 [4436] - info: [upgrade] Schema already up to date!
OK
NodeBB Upgrade Complete!
[email protected] :/var/www/nodebb# ./nodebb start
Starting NodeBB
"./nodebb stop" to stop the NodeBB server
"./nodebb log" to view server output
"./nodebb restart" to restart NodeBB
[email protected] :/var/www/nodebb# ./nodebb restart
NodeBB could not be restarted, as a running instance could not be found.
The following is the output. I'm guessing the last line is my problem, just not sure how to fix it?
Clustering enabled: Spinning up 1 process(es).
3/3 14:40 [4137] - info: Time: Thu Mar 03 2016 14:40:11 GMT-0500 (EST)
3/3 14:40 [4137] - info: Initializing NodeBB v1.0.0
3/3 14:40 [4137] - info: [database] Checking database indices.
[outdated] nodebb-plugin-soundpack-default installed v0.1.5, package.json requires 0.1.6
3/3 14:40 [4137] - warn: One or more of NodeBB's dependent packages are out-of-date. Please run the following command to update them:
3/3 14:40 [4137] - warn: ./nodebb upgrade
[cluster] Child Process (4137) has exited (code: 0, signal: null)
said:
a facebo
You can revoke your Facebook access token by logging into Facebook, clicking the little down arrow in the main nav and going to settings.
Then find 'Apps' in the menu on the left. Find your app, hover over it and click the X. Alternatively, click the app and open its settings. and down the very bottom you will see a link to remove app.
You can then login with Facebook and it will ask you to authorise again.
I did a fresh install of Nodebb, to 1.0.0 and I am having trouble getting the application to start.
It will run fine if I run ./nodebb dev
However, if I run ./nodebb start it will print the usual:
'Starting NodeBB
"./nodebb stop" to stop the NodeBB server
"./nodebb log" to view server output
"./nodebb restart" to restart NodeBB
If I then type ./nodebb restart, it prints:
NodeBB could not be restarted, as a running instance could not be found.
I have started the application in dev mode and disabled all the plugins.
I'm not sure what else to try?
Tom
'
@nhl.pl Okay, so I've been testing for the last couple of days and it works, sometimes.
I can login with Instagram and Facebook with my own account. I used the Instagram account that I made the API with and another one, they worked. I then used my girlfriends account and that didn't work.
I tried Google authentication, that did the same thing. It made the user and redirected to the homepage without logging in.
I tried Twitter API and that just wouldn't save my API credentials.
I'm lost as to what I should try next? I'm guessing that there is a common reason why none of them are working.
Should I be using PLEASE in front of queries for Mongodb?
@Kowlin Yeah, I turned HTTPS off. I was using CloudFlare SSL.
HTTPS wasn't my issue but, it was Facebook logins.
@nhl.pl Okay, so I stopped nodebb and restarted in dev. I logged in with my personal Facebook account (the one that the app was made with) and it seems to be working.
I used someone elses and I got the same problem as before. I can't see any errors in the logs when a user logs in.
I"m going to try with a Twitter app and see if I can get that to work. If it also doesn't work, I'll assume its a problem with routing.
Tom
@nhl.pl So I deactivated all plugins and uninstalled sso-Facebook. I reinstalled sso-Facebook and restarted nodebb.
I changed every record of https to http and removed CloudFlare, the domain is now pointing directly at the sever.
Facebook logins are still redirecting back to the home page without logging the user in.
Is there a log file that I can have a look at?
Tom
@nhl.pl I reloaded, restarted and restarted nginx.
I'm still getting the same issue.
Could the error be with my redirect URL in the Facebook app?
@nhl.pl I've disabled CF and https. The error in the console has disappeared.
However, I'm still having the same problem with Facebook logins. I'm not sure where to look to try and resolve the issue?
I've had a look at my nginx config and config.json and can't find a problem. I've tried it with http and https, with and without https set in CloudFlare.
My config.json looks like:
{
"url": "https://aussiesupover.com",
"secret": "",
"database": "mongo",
"port": 4567,
"mongo": {
"host": "127.0.0.1",
"port": "27017",
"database": "0"
}
}
I set the callback URL in Facebook to domain.com/auth/facebook/callback
I'm really confused as to why its not working? Can you suggest anything else that I should check?
I have installed the nodebb-plugin-sso-facebook plugin, created a Facebook app and input my client ID + secret.
I have tried several times to register a user with Facebook and I keep getting the same problem. The user allows the app and is then redirected back to the index of the website.
When the user clicks 'login with Facebook', they are redirected back to the index and are not logged in.
In Admin>manager>users, the user appears to have an account.
I'm not seeing any on-page errors, is there an error log that I can look at?
Tom
Sorry about the lack of detail. I think I realised what was wrong as I was typing and I've fixed it.
I had no web server :O.
I followed this guide: https://docs.nodebb.org/en/latest/installing/os/ubuntu.html
I can access the forum using the ip address and port. I have pointed the IP address at the server.I have also changed the domain in config.json to my domain name.
When I visit the domain I get an error 521. I don't think that nginx was installed.
Do I need to install Nginx and then point the domain at the nodeBB folder?
Tom
