@RandomAnimeGamer what you mean it recommends specifying a port? Here's a quote from the guide:
Note: When entering your site URL, make sure it is exactly what you plan on accessing your site at. If you plan on visiting http://example.org to open your forum, then enter exactly http://example.org.
So after doing a lot of digging, I found out that the error was that NGINX needs to be configured for the SSL. This isn't really mentioned in the Ubuntu nodeBB guide, and the NGINX configuration guide linked on it is a dead link.
First, I needed to combine my certificate and intermediate certificate (If you have a root certificate, you combine it as well) into one .cert file. This amounted to just copying the intermediate certificate and pasting it after the regular certificate (keeping the "BEGIN" and "END" lines).
Then, I inserted the combined key into /etc/ssl/ directly. After doing this, I added my private key to a new folder I created in etc named "keys" (/etc/keys/).
Lastly, I referenced my SSL in the "default" file in /etc/nginx/sites-available/default
the deleted threads appearing in the category listing
Non-privileged users should just see "This topic is deleted!" or "This post is deleted!". Their position is kept because it is rather difficult to keep track of the topics/posts based on who can view the post and who cannot.
@baris@julian I've just found out that this problem goes much deeper. If you look at the general page in the ACP, all of the values are missing (but are there in the database). In addition, the email page does not allow any changes to be saved.
Is there any setting that can be toggled or tweak that can be made to NodeBB so that users are able to block mods? I can envision a usecase where they may not want to see mod posts, but can still be reachable via DMs. Is this possible?
However, all emails sent to these kinds of addresses are returning back to us. This was already happening, but it was not bothering us so far 😄 unfortunately, recently we started to have a lot of "Delivery Status Notification (Failure)" emails... so, we would like to solve this.
Address not found
Your message wasn't delivered to [email protected] because the domain facebook.com couldn't be found. Check for typos or unnecessary spaces and try again.
And on the Facebook postmaster page, we can confirm the problem as "RCP-P1 The attempted recipient address does not exist."
Since the forum sees these accounts as valid and activated, it keeps trying to send an email at any action that causes email delivery. And of course, all emails are being failed to be delivered and returned back to us.