I'll make this as simple as it can be, after importing your forum it might come a problem when you see some of your users avatars broken, here's a simple method to set a placeholder image for missing images.

• First you have to upload your default image anywhere on the public directory, I would suggest in public/uploads/default.png, the full path should be /path/to/nodebb/public/uploads/default.png.

• Now you have to get the default avatar directory for your imported forum, to get this path right click on the avatar of your broken user and click copy image location, paste it in a text file, in my case it was example.com/assets/uploads/xenforo/data/avatars/m/0/84.jpg so the path should be the folder containing all avatars /uploads/xenforo/data/avatars you have to lose the assets folder from the path.

• In your nginx conf add this block under the main block /:

  location /uploads/xenforo/data/avatars {
    try_files $uri /uploads/xenforo/data/avatars/default.png;
  }
  

  Full nginx conf should look something like this:

  upstream nodebb {
    ip_hash;
    server 127.0.0.1:4567;
  }
  server {
    server_name example.com www.example.com;
  
    root /path/to/nodebb/public;
    location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $http_host;
        proxy_set_header X-NginX-Proxy true;
  
        proxy_pass http://nodebb;
        proxy_redirect off;
  
        # Socket.IO Support
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
  
        location /uploads/xenforo/data/avatars {
          try_files $uri /uploads/xenforo/data/avatars/default.png;
        }
    }
  }
  

Hope this helps someone.

@julian Happy to help!

Just figured it out, mysql sock was pointing to macOS's MAMP path, instead the developer should've made it a mandatory field for user to specify the location of the sock or use default location for each OS. For anyone having the same issue here's the solution.

• First use ssh to login to mysql: mysql -u root -p

• Enter your root password then type: show variables like 'socket';

• You will get something like this:

  +---------------+---------------------------+
  | Variable_name | Value |
  +---------------+---------------------------+
  | socket | /var/lib/mysql/mysql.sock |
  +---------------+---------------------------+

This the sock path you need /var/lib/mysql/mysql.sock now exit mysql and open index.js file located in nodebb-plugin-import-xenforo and edit this line https://github.com/akhoury/nodebb-plugin-import-xenforo/blob/master/index.js#L24 to reflect your sock path, save the file and restart the forum.

Note: After you select an exporter and before starting the migration make sure to check the box Skip the module install or it'll replace the file index.js and reverse all the work you just did.

The importer should work now if everything is set properly. Hope this helps someone.

Hey guys. Been trying for the last 2 days to import my XenForo database to NodeBB for testing purposes. But I couldn't get it to work it just try to install the XenForo importer plugin and break on setup. I have done everything required and tried both locally and on my VPS but I always get the same result.

If someone can help i'll be much appreciated.

I'm very impressed!

@rod said in Site is not working properly with nginx proxy?:

@Cyb3r To go through the paces, comment the include statements that are not already commented. Comment the location ~ block. What you should be left with is the bare minimum configuration and one location block, that being location /.

RESTART Nginx. Give that a try.

Thanks that's seemed to work only one file is missing now: plugins/nodebb-plugin-markdown/styles/railscasts.css

Edit: Now it's working great!

Thanks guys I really appreciate the help and I love NodeBB. Easy, fast and elegant software.

Cheers!

@tqwhite said in Site is not working properly with nginx proxy?:

@Cyb3r If it's working properly from localhost:port, then NodeBB isn't the problem. The installation paths are not going to matter either. NodeBB is serving the CSS, etc, itself. In my config, nginx has no idea where the files are coming from, just the port to which it passes the request.

That means that your nginx config is incorrect. So, post it and let's see what's going on.

Good luck.

Thanks for the reply and here's my nginx config:

server {
	server_name mydomain;

	access_log /home/nginx/domains/mydomain/log/access.log combined buffer=256k flush=60m;
	error_log /home/nginx/domains/mydomain/log/error.log;

	root /home/nginx/domains/mydomain/public;

	# prevent access to ./directories and files
	location ~ (?:^|/)\. {
		deny all;
	}
	
	location / {
		proxy_set_header X-Real-IP $remote_addr;
		proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
		proxy_set_header Host $http_host;
		proxy_set_header X-NginX-Proxy true;

		proxy_pass http://127.0.0.1:4567/;
		proxy_redirect off;

		# Socket.IO Support
		proxy_http_version 1.1;
		proxy_set_header Upgrade $http_upgrade;
		proxy_set_header Connection "upgrade";
	}

	include /usr/local/nginx/conf/staticfiles.conf;
	include /usr/local/nginx/conf/php.conf;
	include /usr/local/nginx/conf/drop.conf;
	#include /usr/local/nginx/conf/errorpage.conf;
	include /usr/local/nginx/conf/vts_server.conf;
}

I use centmin mod LEMP web stack.

Hey guys, so I have decided to try NodeBB yesterday but I got lots of issues with the rules and i'm fairly good with nginx and servers but i don't know what's wrong.

Here's full issue details:
Site public folder path: /home/nginx/domains/mydomain/public
NodeBB path: /home/nginx/domains/mydomain/ (I installed it here in hope the issue would be solved)

First I installed it in a sub folder but I got lots off issues where CSS and JS files didn't load for some reason even after adding the rules.

When I moved it to the path mentioned above the CSS is restored but the JS files won't work I inspected the network traffic and it show's 404 for most files.

I have to note the site is working good with the normal server ip and port 0.0.0.0:4567.

Any idea why would this happen?