L
@nhl.pl said:
Please look again on all those nginx conf files quoted by me and correct your own.
P.S. all your problems comes from wrong nginx configuration, lack of socket.io lines for example
Thanks for all you're help NHL, I'm gonna pay someone to solve these issues, I'm getting no-where fast, is very frustrating for my users, getting lots of complaints about not being able to post and too many emails to cope with cos the forums aren't working.
@nhl.pl said:
Could please post it here? I mean what you're trying to do with nginx config.
nginx default
# Make site accessible from http://localhost/
server_name wikievolved.org;
location / {
proxy_pass http://127.0.0.1:4567;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
config.json
{
"url": "http://wikievolved.org",
"secret": "2",
"database": "redis",
"redis": {
"host": "127.0.0.1",
"port": "6379",
"password": "",
"database": "0"
}
}
@nhl.pl said:
You have wrong configuration.
In relation to;
@nhl.pl said:
Sorry, it's late here in GMT+1.
You should try a config from an experienced user and replace IP in proxy_pass with localhost.
Bye, bye for now.
Enjoy you're sleep 
Ok well after a little investigation the line below can't be wrong, I tried a few alternatives and upon restarting nginx it failed throwing up an error "invalid URL prefix in /etc/nginx/sites-enabled/default:31"
proxy_pass http://localhost:4567;
The localhost:4567 proxy pass was the only one I was able to use and restart nginx with. So assuming default is right, I guess that means .json might be wrong instead?
{
"url": "http://wikievolved.org",
"secret": "",
"database": "redis",
"redis": {
"host": "127.0.0.1",
"port": "6379",
"password": "",
"database": "0"
}
}
I know I'm a little dippy when it comes to Nodebb but shouldn't the port setting above be 4567, or should the nginx default file be 6379?
@nhl.pl said:
They do not know you're running NodeBB.
You can check user profile for tracked IP address. It will be localhost displayed as IP.
So you should also add this to your nginx config.
Sadly none of that has helped, I restarted nginx and Nodebb.
Just one final check for the default file, is this right?
# Make site accessible from http://localhost/
server_name localhost;
location / {
proxy_pass http://localhost:4567;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
Just out of interest how did you know I had the settings wrong?
@nhl.pl said:
Yes, I know. You have wrong configuration.
Mmmm yeah, if you look at the Digital Ocean advice given, it was me that asked that question, so my setting are already correct, - I think;
Though I don't have this in my nginx default file
server {
listen 80;
server_name ideocracycommunity.com;
location / {
proxy_pass http://localhost:4567;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
}
Mine looks like this;
server {
listen 80 default_server;
listen [::]:80 default_server ipv6only=on;
root /usr/share/nginx/html;
index index.html index.htm;
# Make site accessible from http://localhost/
server_name localhost;
location / {
proxy_pass http://localhost:4567;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
}
@nhl.pl said:
Any JavaScript programmer will be good and will solve issues like this.
Well there more things than that;
@nhl.pl said:
Clear browser cache and try again.
Look here: https://github.com/NodeBB/NodeBB/issues/2994
Still the same, the list of errors with my forums are steadily growing. No worries am thinking of hiring someone to solve all these issues, is there a place to ask for pro help?
@nhl.pl said:
You have to update NodeBB core files and theme.
We're testing it here:
https://community.nodebb.org/topic/4228/3-2-1-engage
grats on the forum promotion, well deserved 
Still struggling to get the forums working, having recently advised my members to visit recent topics and then new topic, they're now reporting the "function.escape error as the topic title.
Still no joy getting the new topic buttons working on any pages, several members have reported this too.
am using dev-0.7. on digital ocean
@nhl.pl said:
You're using plug-ins written for NodeBB v0.6.x with the latest v0.7.0-dev. To troubleshoot such problems a plug-in should be uninstalled and not only disabled. It will clean your database from locks and similar things.
Sorry, I can't help with the downgrade.
ok many thanks, I disabled and uninstalled, didn't make a difference so I guess I'm stuck with what I have, hopefully the dev version will become stable at some stage.
@nhl.pl said:
It's not that bad. You can create new topics from "Recent" page. And yes, something wrong with non-approved users and permissions.
Disabling the plugin makes no difference, I'm still unable to create or delete topics. I've carried out a complete browser cache.
Also bear in mind I'm logged in as admin, I get this message when viewing your deleted post;
"This topic has been deleted. Only users with topic management privileges can see it."
So maybe a general Nodebb permissions error?
thanks
@nhl.pl said:
I have registered a new user account and created a new topic.
http://wikievolved.org/recentIt works fine for me.
lol and thanks, yeah I noticed, makes it even worse then, because after your posting I tried and was still unable to post lol I wonder if it a problem with nodebb-plugin-newuser-approval?
If you don't mind can you try again? I've activated your account, if it is because of the approval plugin my bet is you can't post now.
@nhl.pl said:
You should hit F5 and prune browser cache before trying again. I guess it could be a problem with WebSockets or some kind of interference problem between NodeBB instances (your own install and this forum for example).
A very slow connection can also be a source of problem.
Thanks nhl, any idea why the new topic button isn't working?