Might as well add another cog to my plan im on cent os
-
I missed this discussion last night, I'm glad you figured out how to install. Congrats @OutlawedOffroad!
As for the vB migrator, I can't promise you if we'll have the time to build it in the short term, but it definitely is in our long term plan
-
I missed this discussion last night, I'm glad you figured out how to install. Congrats @OutlawedOffroad!
As for the vB migrator, I can't promise you if we'll have the time to build it in the short term, but it definitely is in our long term plan
That's why I'm playing around with a different domain for now The OO site can stay as it is for the time being there really is no rush there. It's going to take time to get comfortable with the system, process, etc.. so I'm going to keep working on the fatherhood forum for now, then release it to the wolves on the twitter/blog groups I'm in and go from there. slow and steady..
my support ticket is in.. but we know how that goes.. it means so and so is not in yet and I need to wait for them i did add in the nginx proxy info if they choose to set it up that way, i tried with no luck. when i was running the service it was killing the 2 vbulletin forums and i can't have that.
-
This guide may help: https://github.com/designcreateplay/NodeBB/wiki/Configuring-nginx-as-a-proxy-to-NodeBB
Yup that's what I sent them!
-
Still plugging away.. Multiple people there trying to get it to work.. Currently it's down completely after support tried to do a transparent .htaccess setup. I removed .htaccess completely after it was borked and now I can't even get to the site via 50.28.60.124:4567 which is very frustrating!!!
-
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.
-