Hi,
No, we have to migrate to new servers with more security in the ISP.
That are a down time of WangGuard. We have a lot of attacks since a month ago 🙁
I’m sorry, but we are working on it but seams that WangGuard works and Sploggers are working on kill WangGuard.
Hi José-
Sorry to hear that. Hope the transition goes smoothly!
-David
Today, we had another attack and WangGuard was down for 1h 45m
Near of a month, we will migrate to new servers and new ISP (with better protection).
We will notify by Twitter.
I’m sorry for the problem.
The WangGuard migration is finished and seams that now is working fine and the new ISP can stop Attacks to WangGuard.
Kind regards
HI José-
Thanks for the update. I’m still seeing a fair number of new user requests that are not checked (~200/day). Do you think these requests are timing out?
I’ve updated to the latest version. Is there anything else I should check?
Thanks,
-David
Hi dcavins,
Since the migration, WangGuard server has 100% uptime.
Maybe your server has a conectivity problem and sometimes cannot contact with WangGuard server. All our test installations has 0 unchecked users.
Can you look if all your unchecked users are at same time? Maybe your server cannot perform the connection to WangGuard by a server limitation…
HI José-
That’s a good question. From 5 pm yesterday to 8 am this morning, I had ~160 unchecked users. The times are like this:
July 25, 2013 1:25 pm
July 25, 2013 1:25 pm
July 25, 2013 1:25 pm
July 25, 2013 1:20 pm
July 25, 2013 1:18 pm
July 25, 2013 1:15 pm
July 25, 2013 1:15 pm
July 25, 2013 1:03 pm
July 25, 2013 1:00 pm
July 25, 2013 12:56 pm
July 25, 2013 12:55 pm
…
I don’t see any problems in our server logs, but I don’t expect a timeout to a remote server to create a log entry. Maybe I’ll have WG create an error log so I can see what’s happening.
Thanks again for the great plugin (dealing with 160 unchecked users is so much better than dealing with 1200 fake users everyday).
-David
Hi José-
Mea culpa. Another piece of code was overwriting the errors that WG sets at the BP action bp_signup_validate. So form submission wasn’t being prevented as it should have been. Once I realized the conflict, it was easy to make the other code behave as it should have to begin with.
WG was doing everything right; sorry for the false bug report.
-David
Don’t worry David,
If you have any problem you can open a new topic or contact with us with our contact form.
Kind regards