Actually quite a nice system. Otherwise you would need to either check regularly if a ban has expired and thus probably do a lot of unnecessary checks, or you would need to predict when the next ban expiration will be and thus probably introduce a lot of bugs with the prediction code.

What might be interesting is a feature request, to not show the flag if the expiration has happened. I assume the flag is stored with a timestamp for when the ban will expire. Thus it should be possible to filter it out when displayed. But actually remove it when the user logs in.

Could you clarify something. Why are you saying putty console? Is this installation running on your local machine or is it running on a remote machine?

Also why are you running NodeBB 1.6.1 and not a more up-to-date one like 1.10.1?

@Macrow-Willson said in Facebook sso - essentials:

yeah, i tried that too, https://myurl.com:4567 renders the forum inaccessible since it doesn't return encrypted http, obviously.

Not really obviously. The URL in your config.json should be the one you're using publicly. Thus whatever your Apache reverse proxy is configured for. The configuration is used to create the URLs on your site. It has no impact on the actual communication with your reverse proxy.

My hunch is, you also need to remove that port. Because your Apache reverse proxy probably is providing your site over the standard HTTPS port. So it probably is just https://myurl.com. Also don't change anything about your reverse proxy configuration when you change this url parameter. Your reverse proxy still fetches the forum over HTTP at the port 4567. This has nothing to do with the url parameter.

Have you read the readme of the import plugin? Especially that giant section saying:

THIS PLUGIN ONLY SUPPORTS: NodeBB v1.7.5

I don't know if it is that but at least that might be a possibility since you're saying in the opened issue that you're using the latest NodeBB?

Nginx reverse proxy can improve the performance of NodeBB. The simplest way to understand this is by viewing the client connection. The client bandwidth requesting something is usually slow or at least much slower than your server. With the reverse proxy in place the request will be done by the proxy and the result stored in memory. Thus it frees up capacity in NodeBB to serve another request. While Nginx caches responses and send them back to the client via their slower connection.

Good to hear. Just in case you need it in the future.

MongoDB has very good documentation and you can find it here: https://docs.mongodb.com/

Dropping the database would be described here: https://docs.mongodb.com/manual/reference/method/db.dropDatabase/index.html

Thus probably would be something along the line of:

use nodebb
db.dropDatabase()

There are many things in this log I find kind of strange.

What NPM version have you installed? According to that Node Security output 1.4.29? That would be way outdated. And thus probably also running a way outdated NodeJS?

Are you sure you followed that documentation? Because it seems you have NodeBB 0.4.3 on your system? npm WARN nodebb@0.4.3

To reinstall from start by losing all your data, just remove the NodeBB directory, drop the database and start fresh. But I highly recommend to first make sure that you run at least NodeJS 6.x and an up-to-date NPM.

Just remove the rights to create topics in there from all users. You can still allow to create topics in the sub categories.

Have a look at the documentation: https://docs.nodebb.org/configuring/proxies/apache/

No ServerAlias needed and just put your subdomain.domain.tld as your ServerName.

Great to hear. But I would like to just put out this notice:

Google Analytics and my plugin do very different stuff. My plugin should be considered as a part of network, system, or website monitoring. It is monitoring the software and its components. While Google Analytics is a web analytics which is about the users and how they use your website. An alternative for Google Analytics is Matomo.

Website monitoring and web analytics are usually not exclusive but are used both at the same time since they are used to monitor different things. Or actually one is monitoring a thing and the other is monitoring humans.