Takes a few seconds for it to show users and that I'm logged in.

kelso

On page changes, or more specifically on a f5 reload, it takes sometimes upto 5 seconds to show that I'm logged in as well as show the forum stats. Im wondering if this is due to me proxying the connection through apache?

My config for Apache has this (relevant info)

ProxyRequests off

<Proxy *>
    Order deny,allow
    Allow from all
</Proxy>

<Location />
    ProxyPass http://127.0.0.1:4567/
    ProxyPassReverse http://127.0.0.1:4567/
</Location>

You guys seen this behavior before? I'm very new to this forum, but liking it so far.

<baris>

Im guessing socket.io is dropping back to XHR instead of using sockets. Can you check your network tab and see if socket.io is making lots of ajax requests?

kelso

Ya, seeing a bunch of XHR connections.. I use CFS firewall, would I need to allow some ports in/out in the config perhaps?

kelso

HS6dCnJhUkLgiQ3u1SVz?t=1392003972782
/socket.io/1/xhr-polling
GET
200
OK
text/plain
socket.io.js:2
Script
242 B
3 B
20.10 s
20.10 s
20.10 s1 ms
HS6dCnJhUkLgiQ3u1SVz?t=1392003992884
/socket.io/1/xhr-polling
GET
200
OK
text/plain
socket.io.js:2
Script
242 B
3 B
20.12 s
20.12 s
20.12 s
HS6dCnJhUkLgiQ3u1SVz?t=1392004013009
/socket.io/1/xhr-polling
GET
200
OK
text/plain
socket.io.js:2
Script
242 B
3 B
20.10 s
20.10 s
20.10 s1 ms
HS6dCnJhUkLgiQ3u1SVz?t=1392004033111
/socket.io/1/xhr-polling
GET
200
OK
text/plain
socket.io.js:2
Script
242 B
3 B
20.17 s
20.17 s
20.17 s1 ms
HS6dCnJhUkLgiQ3u1SVz?t=1392004053280
/socket.io/1/xhr-polling
GET
(pending)
socket.io.js:2
Script
13 B
0 B
Pending

kelso

After a bit of research (Your comment got me at least knowing where to look), apache 2.2 doesnt support proxying of websockets. Now to get that resolved

kelso

Just figured I'd write back with what the fix was!

First of all, if you're using apache 2.2, it doesnt come with a new proxy module "mod_proxy_wstunnel", this is now included in the newer 2.4 distributions of the platform.

Next, if you google around, you can find easy instructions for debian/ubuntu for backporting that module to work with your setup.

The next part, is what was added to my sites-available/sitename.conf

ProxyRequests off

<Proxy *>
    Order deny,allow
    Allow from all
</Proxy>

ProxyPass /socket.io/1/websocket ws://127.0.0.1:4567/socket.io/1/websocket
ProxyPassReverse /socket.io/1/websocket ws://127.0.0.1:4567/socket.io/1/websocket

ProxyPass /socket.io/ http://127.0.0.1:4567/socket.io/
ProxyPassReverse /socket.io/ http://127.0.0.1:4567/socket.io/

ProxyPass / http://127.0.0.1:4567/
ProxyPassReverse / http://127.0.0.1:4567/

My config.json from Nodebb
"port": "4567",
"use_port": true,
"bind_address": "127.0.0.1",

Sincerely hope this helps someone else out. However after this major fiasco, I'm leaning towards NGinx more now as it seems to be supported by default and I've been thinking about the move for a while now.

Bri

Cool, thanks for posting the update!

finid

@kelso,

Is your installation a local one, and if so, will you be changing the bind_address to a real IP for the production site, or would it still be the loop back address even in production?

kelso

@planner Since Apache and Node live on the same server and Apache is doing a proxy/reverse proxy, it will live with a local IP, I did have to make one tweak and that was to change use_port: false within the config.json..

finid

@kelso

So you changed use_port: true to use_port: false, right?

kelso

@planner said:

@kelso

So you changed use_port: true to use_port: false, right?

Yes

psychobunny

@kelso any chance you could write up a short guide for Apache on our wiki?

kelso

@psychobunny
https://github.com/designcreateplay/NodeBB/wiki/Configuring-Apache-as-a-proxy-to-NodeBB

How's that?

kelso

Also added link to Main Wiki (Hope that was ok)

psychobunny

Wow awesome! Thanks so much @kelso and of course yeah definitely needs to be on the homepage small shout-out to you on our recent blog post