Installing NodeBB in a subfolder of another site
-
Here's my config.json:
{ "base_url": "http://192.168.1.4", "port": "4567", "use_port": false, "secret": "fff02b17-b9cc-444c-b929-85ec9cecec93", "bind_address": "0.0.0.0", "database": "redis", "redis": { "host": "127.0.0.1", "port": "6379", "password": "redis", "database": "0" }, "bcrypt_rounds": 12, "upload_path": "/public/uploads", "relative_path": "/forum"It shows that even after telling it not to connect via port 4567, it still did anyway.
-
@baris, @julian, @psychobunny, I'm still on this.
If I modify the code given here for the subfolder installation to look like this:
upstream nodejs { server 192.168.1.4:4567; } server { listen 80; server_name 192.168.1.4:4567; root /var/www/forum; 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://192.168.1.4:4567; proxy_redirect off; # Socket.IO Support proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } }I get a 403 Forbidden error message when I attempt to access http://ip-address/forum.
And if I replace
server_name 192.168.1.4:4567;withserver_name 192.168.1.4/forum;.nginx -treports"nginx: [warn] server name "127.0.0.1/forum" has suspicious symbols in /etc/nginx/sites-enabled/default:91Note that NodeBB (nodejs) is listening on the default port, even though I didn't want it to.
Any suggestions?
-
NodeBB has to listen on a port. It could listen on a UNIX socket, but that's outside of the scope of this question (and is pretty pointless, anyway).
Given your nginx config, please make the following changes:
- Remove the
upstreamportion, as you don't seem to be referencing it anymore - Remove the
rootdirective, it is not required server_nameshould be192.168.1.4, no port
nginx -tshould work then, and you can restart it and try again.nginx: [warn] server name "127.0.0.1/forum" has suspicious symbols in /etc/nginx/sites-enabled/default:91If you still get this error, take a look at what's on line 91 of
default..! - Remove the
-
I'm getting warmer. Here's what I did:
I just added the code below into the default server block, that is, no separate server block for NodeBB.
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://192.168.1.4:4567; proxy_redirect off; }Navigated to http://ip-address/forum and got the default page, minus the default categories. And clicking on any of the buttons returns nothing. No error messages in the log files.
I'll recircle back to the previous attempt, but what do you make of this?
Here's a screenshot:
-
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 undefinedThat's the type of messages on clicking on any link.
In Nginx's access.log, I get lines like:
"GET /forum/api/config HTTP/1.1" 200 265 "http://192.168.1.4/forum/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.93 Safari/537.36"Nothing in Nginx's error.log.
Btw, clicking on the Unread link loads the default Nginx page.
-
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/forumif 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 undefinedAnd 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 3000The 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 3000Important
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
