Technical Support

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()

No, as viewing IP addresses are a core part of the moderation experience. Global moderators can access the account info page, and category moderators can view IPs per post in categories they moderate. This is needed to see if particular users are sockpuppets, or other malicious types of users.

@pitaj you're right, I've just upgraded to the latest version (v1.10.1) and everything seems fine!

Mmhm, because we noticed it taking a long time we added progress bar support, so you can see that it's doing something We store the IP addresses going back to the installation of the forum, so it's possible that it's no longer needed. One could simply delete the entire ip:recent set with no ill effects... (well, except that you'd no longer have a historical record of recent IP addresses)

So, with this configuration, it's ok ! <VirtualHost *:80> ServerName mydomain.com ServerAdmin [email protected] DocumentRoot /var/www/html # Available loglevels: trace8, ..., trace1, debug, info, notice, warn, # error, crit, alert, emerg. # It is also possible to configure the loglevel for particular # modules, e.g. #LogLevel info ssl:warn ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined # For most configuration files from conf-available/, which are # enabled or disabled at a global level, it is possible to # include a line for only one particular virtual host. For example the # following line enables the CGI configuration for this host only # after it has been globally disabled with "a2disconf". #Include conf-available/serve-cgi-bin.conf <IfModule mod_rewrite.c> RewriteEngine On RewriteRule ^[^\/]*\/(.*) https://mydomain.com/$1 [R=301,L] </IfModule> RewriteCond %{SERVER_NAME} =mydomain.com RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent] </VirtualHost> <VirtualHost *:4567> ServerName subdomain.mydomain.com # Basic security headers Header always set X-Content-Type-Options "nosniff" Header always set X-Xss-Protection "1; mode=block" # NodeBB header RequestHeader set X-Forwarded-Proto "https" # Static file cache <FilesMatch "\.(ico|jpg|jpeg|png|gif|js|css)$"> <IfModule mod_expires.c> ExpiresActive on ExpiresDefault "access plus 14 days" Header set Cache-Control "public" </IfModule> </FilesMatch> ProxyRequests off <Proxy *> Order deny,allow Allow from all </Proxy> # Custom Error Document when NodeBB is offline ProxyPass /error-documents ! ErrorDocument 503 /error-documents/503.html Alias /error-documents path/to/nodebb/public # Websocket passthrough RewriteEngine On RewriteCond %{REQUEST_URI} ^/socket.io [NC] RewriteCond %{QUERY_STRING} transport=websocket [NC] RewriteRule /(.*) ws://localhost:4567/$1 [P,L] ProxyPass / http://localhost:4567/ ProxyPassReverse / http://localhost:4567/ # Log stuff ErrorLog ${APACHE_LOG_DIR}/nodebb-error.log CustomLog ${APACHE_LOG_DIR}/nodebb-access.log combined RewriteCond %{SERVER_NAME} =subdomain.mydomain.com RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent] </VirtualHost> The problem is that I had not put 2 different ServerName in the config, so all traffic was redirected and rewritten in HTTPS on the same ServerName : subdomain.mydomain.com

Not right now, feel free to open an issue for it on github page.

Your reverse proxy is set up wrong, or not set up at all.

Settings => Uploads => Profile Avatars

NodeBB version: 1.10.0 Database type: mongo Database version: 3.2.11 Hi, we have a critical situation here. In order to increase the speed, We replicated mongodb (master/slave mode; whotout sharding). It increased the speed for a few months But now it seems that the database is missing and all of the users, topics etc. ?? I don't know what cause this problem. Can we find out whether the database is missing or not?

Ahh yeah that's a bit confusing, the merge topic tool can be used between categories, so you should click merge first and then select the topics. The placement seems like a theme/skin issue.

@butonix if you run ./nodebb build does it show up though?

@pitaj said in Adding javascript in the footer: Ok have you tried embedding the whole thing in the footer HTML? What is the script and stuff for? Analytics? Are there any alternatives that don't require a script? Yes, it breaks certain part when it is placed in that widget. It's so that when users from other countries click on the link for amazon they get redirected with the US referrer code link embedded their countries amazon store.

@Atayz I did that but sadly not fixed. Had to restore a back-up from 2 days ago. Now it's gone but I miss data from 43 hours sadly (my fault i know)

I changed the permissions and checked, as I said before. I even tried the alternative configuration from the NodeBB scaling guide. That didn't make any difference. There are missing directories and I don't know why. I'll delete NodeBB and move on. Thanks for trying to help guys.

@hoang6 go in to your nodebb folder, the logs are inside the logs folder, open output.log and paste the last 20-30 lines which should show the crash.

Please first check the data storage directories of your MongoDB. While doing some crazy tests and more or less intentionally made the MongoDB go crash I found at times that it "forgot" about the available data, even though there were still kind of big files probably with all the data. I don't know how to recover from there but I assume there would be some articles out there in the internet helping you with it. But yeah, mongodump, borg backup, lftp synchronize to remote drive (or similar). Every day. And if you're at it, make sure the backups on your local computer are working as intended as well

http://prntscr.com/jzjkvo at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14), code=ETIMEDOUT, errno=ETIMEDOUT, syscall=connect, address=159.203.9.60, port=443

Solution: I've copied the catagories.tpl from Vanilla to Persona, enabling me to use Persona's mobile menu with Vanilla's categories style, both.

.........Forgot to mention it's Vanilla theme, so the mobile view is unlike Persona. I wish it was , though