Might as well add another cog to my plan im on cent os
-
So I moved to Digital Ocean for the sake of not screwing up my existing forums.. the proxy was screwing up the tapatalk and whatever else so it was not worth breaking 2 good sites for 1 test site.
dad-forums.com now is proxy on and resolving to the right stuff, blah blah..
but... i'm having that same data issue.. here's my config file per the wiki..
upstream nodebb {
server 162.243.229.221:4567;
}server {
listen 80;server_name dad-forums.com; root /home/steve/mynodebb/install; 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"; }}
anyone see something i'm missing here?
-
Weird cause at dad-forums.com:4567 it's working just fine with the counters and no delays anywhere.. so it's still happening now on DO as well.. so it must be something i'm doing or not doing.
next up is to move the data over i'm sure that's going to be a treat lol
-
PITA I have to keep rebooting the DO server for the site to work more than 5 min at a time. Then it goes to a white page..
I made the update to the IP, powering it down and up now.. restarting nginx, node, forever, whatever else seems to do nothing and it just hangs.
-
Here's how the site looks... when going direct to dad-forums.com where it's going the proxy.. keep in mind if I go to the same link and add the port :4567 it works just fine.
-
Now ~5min later the dad-forums.com ghosts up to a white page, but the :4567 still trucking along with no problems...
Jeeeeeeeez I'm glad I got a lot of hair so if I pull some out there's plenty left.
edit: spoke too soon, both sides a white screen now lol.
-
from nginx error log, I have pages of this error.
2013/12/10 19:34:22 [error] 614#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 67.225.149.136, server: dad-forums.com, request: "GET /socket.io/1/?t=1386704047703 HTTP/1.1", upstream: "http://127.0.0.1:4567/socket.io/1/?t=1386704047703", host: "dad-forums.com", referrer: "http://dad-forums.com/"
-
this is the other error I'm seeing a bunch of as well:
2013/12/10 20:14:24 [error] 614#0: *450 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 71.183.91.42, server: dad-forums.com, request: "GET /socket.io/1/xhr-polling/h_jR4ziaFtyNQriIAv2D?t=1386706416376 HTTP/1.1", upstream: "http://127.0.0.1:4567/socket.io/1/xhr-polling/h_jR4ziaFtyNQriIAv2D?t=1386706416376", host: "dad-forums.com", referrer: "http://dad-forums.com/"
-
Perhaps it will help you to know that I have been checking in on dad-forums.com periodically throughout the day, and it has been up every time?
I've been resetting it constantly lol you might just have good luck.. buy a lotto ticket
-
Let's confuse the issue deeper...
Site just went white in my browser. too long to read error in the error.log for nginx.
I open up Chrome, it works.
I open up my iPad, it works (also a Safari based item).So something in Safari/desktop is not playing nice with the site.
BUTTT (there's always one)
The site does not show stats, admin info, etc. in ANY of these broswers or devices unless I load the site up with the port # info :4567 -- also the same re: Login showing after signing in and getting Admin access.. all that happens over everything.
So I'm thinking it's a nginx setup issue because it's obviously not node/forever/etc.. they're all ok.. it's something with the proxy/nginx config.
-
Okay. I tried a bunch of things systematically when I get the white screen. End result is if I close/open a tab and retype in addy it loads up.. so the process there is crapping out, but it's still up.. that's why @julian you see it when checking
Now the real and final issue here is the :4567 showing the data / #'s etc.. correct, and the url without port is not per the screenshots.
Once that's fixed I can finally pull in the other database. I'm sure that will be a treat.
-
When NodeBB doesn't show the forum stats, that's usually because it is unable to connect with websockets, and will eventually fall back to XHR polling. At least... that's the hope
If you stay on that page for 10-20 seconds, do the stats come up eventually?
-
When NodeBB doesn't show the forum stats, that's usually because it is unable to connect with websockets, and will eventually fall back to XHR polling. At least... that's the hope
If you stay on that page for 10-20 seconds, do the stats come up eventually?
Only the first stat.. or in ACP some come in some don't. But yeah it's 10-20 seconds.
I used to run old school BBS's back in the day 10-20 years ago compiling C++ and whatever with my old WWiV systems so I don't mind troubleshooting as long as I know there will be an end to the rainbow.
