Installing NodeBB in a subfolder of another site
-
Ok, @baris, @julian, @psychobunny, I think I've gone the whole nine yards on this. The problem is most likely that NodeBB is not at the state where it can be installed and work correctly in a subfolder. The best I've been able to get, is a blank home page with header links that don't work.
I'll just keep adding content to the live site and hope that somebody takes a shot at fixing it before it goes live.
If you guys want to use me as a test case, go right ahead!
-
The last time I tried subfolder installation it was working fine, but I never tried it with nginx proxying. So I suggest you take out all the nginx proxying first and try it with
http://domain.com:4567/forum
if that is working then figure out proxying. -
The last time I tried subfolder installation it was working fine, but I never tried it with nginx proxying.
Accessing it from a subfolder with the port appended is not a problem, but that's not feasible for a public site,
And what do you make of the error messages from Chrome console below?
GET http://192.168.1.4/forum/404 404 (Not Found) 192.168.1.4/:25 Uncaught ReferenceError: io is not defined nodebb.min.js:7 Uncaught TypeError: Cannot set property 'initialLoad' of undefined 192.168.1.4/:270 Uncaught ReferenceError: templates is not defined nodebb.min.js:8 Uncaught TypeError: Cannot call method 'emit' of undefined
And what do you make of the fact that NodeBB is listening on the default port even after specifying during the installation stage that it not listen to the port. Could that be part of the problem?
-
I have found the best solution for me.
I use the redirect rules in iptables of my cloud Ubuntu14.04.
The comand below will redirect port 80 to port 3000. Use your NodeBB at port 3000sudo iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 3000
The comand above will works up to next reboot. It means that you have to add the following string to
** /etc/rc.local file **iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 3000
Important
Check if your network interface use the name eth0. Perhaps you have to use other network interface (for example eth1... etc)
-
@limitx3m said:
Has there been any advancement about displaying nodebb from .com/forum using nginx ?
I would be interested too
-
Actually yeah I've managed to install it in a subdirectory and run it via normal command line but I've got problems trying to get it to restart on reboot.
nginx/site-available/nodebb
server { listen 80 default_server; listen [::]:80 default_server; root /var/www/; index index.html index.htm index.nginx-debian.html; server_name _; location / { # First attempt to serve request as file, then # as directory, then fall back to displaying a 404. try_files $uri $uri/ =404; } location /forum { 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/forum; proxy_redirect off; # Socket.IO Support proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } }
config.json
{ "url": "http://localhost:4567/forum", "secret": "insert_your_secret_here", "database": "redis", "redis": { "host": "127.0.0.1", "port": "6379", "password": "insert_your_password_here", "database": "0" } }
In order to restart nodebb upon server restart I've used the init script based on
https://www.exratione.com/2013/02/nodejs-and-forever-as-a-service-simple-upstart-and-init-scripts-for-ubuntu/Modifications/Important config below
SOURCE_DIR="/var/www/nodebb" NODE_USER="nodejs_user"; APPLICATION_PATH="app.js" # ... other config start() { echo "Starting $NAME" # sample forever command didn't seem to work # forever # --pidFile $PIDFILE # -a # -l $LOGFILE # --minUptime $MIN_UPTIME # --spinSleepTime $SPIN_SLEEP_TIME # start $APPLICATION_PATH 2>&1 > /dev/null & sudo -u $NODE_USER relative_path=/forum upload_url=/forum/uploads/ forever --sourceDir $SOURCE_DIR --pidFile $PIDFILE -a -l $LOGFILE --minUptime $MIN_UPTIME --spinSleepTime $SPIN_SLEEP_TIME start $APPLICATION_PATH 2>&1 > /dev/null &
Not sure if that's the best way of doing it, but it seemed to work for me.
Edit: Seems that file/image upload is broken: it uploads to /uploads/ instead of /forum/uploads/. Still looking into that
Edit 2: Uploads fixed with relative_path=/forum upload_url=/forum/uploads/ in the script. Other problems found:
- Can't stop forever via script (maybe something to do with log and pidfiles not being created)
- Can't install plugins
- Doesn't read from config.json but via environment variables passed in the init/forever script?
-
I forked your topic so you will not be inadvertently resurrecting an old topic.
In my nginx config, I have the following lines that differ from yours:
location /forum/ {
and
proxy_pass http://127.0.0.1:4567/forum/;
Perhaps altering those lines will help.
-
@julian said in Installing NodeBB in a subfolder of another site:
I forked your topic so you will not be inadvertently resurrecting an old topic.
In my nginx config, I have the following lines that differ from yours:
location /forum/ {
and
proxy_pass http://127.0.0.1:4567/forum/;
Perhaps altering those lines will help.
config.json should be:
"url": "http://domain.com/forum",
nginx.conf should be:
location ^~ /forum { proxy_pass http://127.0.0.1:4567; }
^~ /forum is important, not /forum
-
I was able to make it work with /forum; no ^~ required. Given what @yariplus stated this seems relevant.
My conf:location /forum/ { proxy_pass http://172.17.2.3:4567; proxy_redirect off; proxy_set_header Host $http_host; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-NginX-Proxy true; # Socket.IO Support proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; }
Indented lines are ones that I copied from my other blocks that weren't present in the suggested.