Might as well add another cog to my plan im on cent os
-
I have full confidence in them, @OutlawedOffroad -- after all, they're paid professionals, right?
If you want to pay somebody else to take a look, I'm sure that can be arranged too (although I do not have much apache experience, so I would be quite helpless as well)
-
I have full confidence in them, @OutlawedOffroad -- after all, they're paid professionals, right?
If you want to pay somebody else to take a look, I'm sure that can be arranged too (although I do not have much apache experience, so I would be quite helpless as well)
They have it working now the issue now is that there is a weird delay of like 10 seconds for things like the 4 stats at the bottom of the home page showing up.
-
The rest of the page loads but the data takes time.
Happens on Admin home, main page home, admin settings, etc.. sometimes like in admin if i jump back and forth on buttons it will load faster.. but strange that it is hanging up like that.
A+ to Liquid Web support. It's basically an "DIY issue" and they are willing to lend a hand and help work things out. Customer Service means everything to me as someone with a heavy Marketing background it's what makes a good brand a great one. They deserve the shout out
-
The rest of the page loads but the data takes time.
Happens on Admin home, main page home, admin settings, etc.. sometimes like in admin if i jump back and forth on buttons it will load faster.. but strange that it is hanging up like that.
A+ to Liquid Web support. It's basically an "DIY issue" and they are willing to lend a hand and help work things out. Customer Service means everything to me as someone with a heavy Marketing background it's what makes a good brand a great one. They deserve the shout out
Try a different browser I think Firefox dose not always play nice in my limited experience.
-
The rest of the page loads but the data takes time.
Happens on Admin home, main page home, admin settings, etc.. sometimes like in admin if i jump back and forth on buttons it will load faster.. but strange that it is hanging up like that.
A+ to Liquid Web support. It's basically an "DIY issue" and they are willing to lend a hand and help work things out. Customer Service means everything to me as someone with a heavy Marketing background it's what makes a good brand a great one. They deserve the shout out
Try a different browser I think Firefox dose not always play nice in my limited experience.
I'm on Safari, have been the entire time.. Issue has only popped up today since the port redirection..
@julian is there any instances where the port is hard coded ? that was a Q from the LW team trying to figure out why the delay.. Everything else spits out fine.. just the things I mentioned above delaying so we're trying to figure out that commonality between them.
-
The delay is caused by the websockets not being relayed properly. In your case, NodeBB is dropping back down to an older (more reliable) technology called "xhr-polling".
Ask them to check that these commands are set up in the nginx config:
# Socket.IO Support proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; -
The delay is caused by the websockets not being relayed properly. In your case, NodeBB is dropping back down to an older (more reliable) technology called "xhr-polling".
Ask them to check that these commands are set up in the nginx config:
# Socket.IO Support proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade";Forwarded through to support, thanks @julian.. Once this is all over we gotta gather the info from the threads so that CentOS page isn't a read link of nothingness
Good part is everything does work now and in the right way.. just fine-tuning the details..
-
We're still only using Apache here and not nginx.
I was a bit behind on the versions @ 2.2 so support is about to update to 2.4.6 they found a module that is supposed to have it built in as web socket proxy was not previously supported.
Might just be an issue of people being bleeding edge current on their servers to eliminate all the hoopla. More details as I get them
-
Okay, had a dr appt with the kid now I'm back with an update.
- Recompile complete, updated Apache installed now.
- Working on web socket proxy.
- Going to reinstall nginx themselves and use that as a fallback.
They are going above and beyond.. Maybe it's a quiet rainy day for them like it is for me I don't know but their level of support is phenomenal. Remember this was all a "DIY issue" fixed on a best efforts basis. Their best efforts are freakin' awesome!
-
The quest continues!! @julian here's an email from LW Support they had a question at the bottom for you guys so I figured best to just cut/paste in case it can help anyone down the road of the dev process for you guys in general.....
Steve,
I am glad to be of service. I also tried using mod_proxy_wstunnel in Apache 2.4 however it was not working, I was only getting a 500 internal server error. Here is a link to the page:
Here is the configuration I used:
ProxyPass / ws://127.0.0.1:4567/
ProxyPassReverse / ws://127.0.0.1:4567/I have changed it back to using just mod_proxy with the following configuration and the 500 errors are gone however the site is still slow to load the footer:
ProxyPass / http://127.0.0.1:4567/
ProxyPassReverse / http://127.0.0.1:4567/Perhaps the developers at nodeBB will have insight in a way to make nodebb work properly utilizing mod_proxy_wstunnel? I'd like to know if they think something like this could work.
-
-
@OutlawedOffroad -- any chance you can get a member of LW Support onto this forum to chat?
Done. Just emailed thread link and let them know everyone wants to work together to figure it out for both the community and them as a host that can support NodeBB users.
-
Productive day yesterday and night both on my end starting to re-color, resize, etc.. the theme but more importantly LW has totally delivered the awesome sauce. I'm waiting on permission to share since it's their code/work but I can post where I'm at today.
1 - nginx version needed is not in their current build. The people responsible for that did tell support it can be done, but they need a few days. The last thing I'm going is putting pressure as I believe they have gone above and beyond as it is. When they get it sorted the last major "issue" of lag will be squashed and I can tell family and friends, etc.. to check it out.
2 - Dan from the late night support kicks major ass. He offered 2 nights ago to help setup scripts for the cpanel service checker. Now every 3-5 minutes it checks for an active http response on port 4567. If it does not get one it fires up the kill script to clear out any hung processes and starts it back up.
I will share the .sh files once they give me the thumbs up. I just believe in asking first when it's someone else's hard work put in.
Less than a week so far and the thread on here basically saying CentOS guys have a lot of work to get it going has become CentOS guys have 1 or 2 small hurdles left to clear and then we can all use NodeBB.. BOOOOOM!!!
-
Their timeline of "a few days" apparently includes the time between telling me and doing other things.. Already working on updating ngix today for the server.. Can't say it enough how great their support is for anyone else needed a self-hosted option they are going above and beyond the call of duty to help make this happen for me.
More details later.. Football and food now..
-
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?
