forum is really really S - L - O - W---maintenance going on?
- Thread starter Mike Lavigne
- Start date
I also found that one member was locked out and he’s from this part of the world when I checked the IP address he logged in with it showed as Germany so something else is going on
several of us (myself included) have also gotten that. I think it is a 503 server error
I works ok / normal speed for me this morning. We are on a shared host so probably the server got loaded by one or more of the other websites it is hosting. With Coronovirus normal usage may have change i.e. gone up at certain times of the day.
I'll talk to them, see what they say.
I'll talk to them, see what they say.
Status Update..........
I am posting this update as I have been getting emails from friends of members in China, and Hong Kong telling me that they are unable to access the site. As I have stated here WBF incurred 2 major assaults on the site last year and our ISP blacklisted China and Hong Kong. We added the firewall in order tallow access to our members in China and Hong Kong as the only other ways was for those members to use a VPN (forbidden in China). This firewall has served us reasonably well after the glitches were ironed out. Last week for whatever reason the site was very slow.
Submitting a ticket earlier in the week confirmed to our tech support that indeed it was the firewall as they removed it and directed all traffic directly to the server and bypass the firewall. When they did the speed returned to normal. Our problem at this point was whether they could program the firewall to work at normal speeds. As soon as the firewall was lifted everyone could access the site at normal speed BUT members from China and Hong Kong could not gain access as the countries remain black listed. This will not change due to the severity of the assault on our site
I spent several hours last night talking to tech support about how to resolve the issue because we don't want to lose our members from China and Hong Kong. Some are accessing the site now with a VPN
Finally late last night I got the message that indicates we should be able to soon see the light at the end of the tunnel.......here is what I received
"So as I mentioned about testing and finding this one option that might have been causing it and it seems like it fixes the speed issue.
The option is called "XMLRPC, Comments and Trackbacks blocked" and this was causing it from what i see because now I am sending your site to go through the DoS firewall and it is going as fast as the site directly to the web server.
Maybe tomorrow morning we can test it together and then switch back to the DoS firewall.
Please update me with your availability for tomorrow morning."
In summary I will be on the phone with them today at 1000 with the chief tech at which time he will access my computer by team viewer. Then he will redirect my IP address through the DoS and if the speed is as he says then all members will once again be directed through the DoS firewall. At that point everyone should have normal speeds and members from China and Hong Kong will also have no problems accessing the site
So I hope t finally put this issue to rest later today
I am posting this update as I have been getting emails from friends of members in China, and Hong Kong telling me that they are unable to access the site. As I have stated here WBF incurred 2 major assaults on the site last year and our ISP blacklisted China and Hong Kong. We added the firewall in order tallow access to our members in China and Hong Kong as the only other ways was for those members to use a VPN (forbidden in China). This firewall has served us reasonably well after the glitches were ironed out. Last week for whatever reason the site was very slow.
Submitting a ticket earlier in the week confirmed to our tech support that indeed it was the firewall as they removed it and directed all traffic directly to the server and bypass the firewall. When they did the speed returned to normal. Our problem at this point was whether they could program the firewall to work at normal speeds. As soon as the firewall was lifted everyone could access the site at normal speed BUT members from China and Hong Kong could not gain access as the countries remain black listed. This will not change due to the severity of the assault on our site
I spent several hours last night talking to tech support about how to resolve the issue because we don't want to lose our members from China and Hong Kong. Some are accessing the site now with a VPN
Finally late last night I got the message that indicates we should be able to soon see the light at the end of the tunnel.......here is what I received
"So as I mentioned about testing and finding this one option that might have been causing it and it seems like it fixes the speed issue.
The option is called "XMLRPC, Comments and Trackbacks blocked" and this was causing it from what i see because now I am sending your site to go through the DoS firewall and it is going as fast as the site directly to the web server.
Maybe tomorrow morning we can test it together and then switch back to the DoS firewall.
Please update me with your availability for tomorrow morning."
In summary I will be on the phone with them today at 1000 with the chief tech at which time he will access my computer by team viewer. Then he will redirect my IP address through the DoS and if the speed is as he says then all members will once again be directed through the DoS firewall. At that point everyone should have normal speeds and members from China and Hong Kong will also have no problems accessing the site
So I hope t finally put this issue to rest later today
Speaking of XML RPC, does that include XHR (a.k.a. XMLHttpRequest)? The WBF does a ton of this by the way:
It's always the same URL. Request body size is always 0 so they're just a blank pings. Reply is always just the little object {"more":true}. In fact, the Sucuri firewall makes no difference to these XHR interactions. Given this firewall option, I'm actually surprised this part was working before...
Attachments
-
wbf_xhr.jpg
All above my pay grade. I wish I understood your point as it seems important.I have forwarded it to our ISP techsSpeaking of XML RPC, does that include XHR (a.k.a. XMLHttpRequest)? The WBF does a ton of this by the way:
It's always the same URL. Request body size is always 0 so they're just a blank pings. Reply is always just the little object {"more":true}. In fact, the Sucuri firewall makes no difference to these XHR interactions. Given this firewall option, I'm actually surprised this part was working before...
Hello all
I have just finished with our tech support and we are now once again going through the DoS firewall and the speed is unchanged. We spent 30inutes on Team Viewer and I watched them direct traffic to the server and then direct traffic to the server via the DoS and the speed is unchanged
As a result we feel they have solved the problem and by doing such there should be no reason for members from China and Hong Kong to need a VPN to access the site. It should be business as usual
I have just finished with our tech support and we are now once again going through the DoS firewall and the speed is unchanged. We spent 30inutes on Team Viewer and I watched them direct traffic to the server and then direct traffic to the server via the DoS and the speed is unchanged
As a result we feel they have solved the problem and by doing such there should be no reason for members from China and Hong Kong to need a VPN to access the site. It should be business as usual
Hello Steve : A million thanks!
We are addicted to WBF.
Thank you again!
We are addicted to WBF.
Thank you again!
ignore them.
Just close your browser and log back in. It's merely a time out from server activity
Just close your browser and log back in. It's merely a time out from server activity
I was told that it all depends on the traffic passing through the DoS at the same time and not uncommonly a server 503 message will occur. Others including myself have gotten "fatal error "messages which I was told by out tech support is the same as a 503 message.
Fortunately as they stated, just close your browser , then reopen the browser and click on the site. I have yet to have this not provide an immediate fix
Similar threads
 | Steve Williams Site Founder | Site Owner | Administrator |  | Ron Resnick Site Co-Owner | Administrator |  | Julian (The Fixer) Website Build | Marketing Managersing |