Wordpress and Wordfence Security is the best solution for Invalid Login, Server Errors, Slowness and DDoS attacks on your WordPress Website or Blog

ISSUE: If you own a wordpress site you know its a constant battle to prevent Robots and Spammers some of the key issues are Preventing Invalid Login, Server Errors, Slowness and DDoS attacks. and scanning harmful links

SOLUTION: After searching for several anti-virus plugin for WordPress I finally found one that protects all my websites, form these attacks in addition it also has a falcon setting to increase the speed of your website.

You can download a copy of the plugin here: https://wordpress.org/plugins/wordfence/

The settings I suggest is after 5 invalid logins, or password recovery attempts block the user for 6 hours, enable the falcon settings under performance and enable auto update. 

These settings have prevented a huge number of attacks on my sites. 

The Google Policy Team - We have now verified that we are no longer detecting PII

ISSUE: Got this strange email unexpectedly from Google Adsense

Publisher ID: ca-pub-XXXXXXXXXXXXX

Dear Publisher,

We have now verified that we are no longer detecting PII being passed to Google from the account(s) under your control.

Thank you for helping to resolve this matter.

Regards,

The Google Policy Team

NOTES: I got this email after enabling the Google Adsense Plugin, I also added a few new sites to webmaster tools so I'm not sure why I got the email 

RESEARCH DONE: 

It seems like the notifications were sent in error overall but my own personal feeling is that it does come from Webmaster tools, not google adsense and it has to do with connecting your website to a wordpress plugin or another app that transfers your personal google account across the internet.

SOLUTION: 

I don't think this is a publishers security breach. I would love to hear what anyone else has to say about this issue for the time being I'm going to leave this one as resolved on my end and will blog more if I get any follow up notifications

Godaddy Timming out when trying to access Hosting Account

Here is the error when trying to access the hosting account using Google Chrome:

Google Chrome could not load the webpage because gateway.godaddy.com took too long to respond. The website may be down, or you may be experiencing issues with your Internet connection.

Check your Internet connection

Check any cables and reboot any routers, modems, or other network devices you may be using.

Allow Chrome to access the network in your firewall or antivirus settings.

If it is already listed as a program allowed to access the network, try removing it from the list and adding it again.

If you use a proxy server...

Check your proxy settings or contact your network administrator to make sure the proxy server is working. If you don't believe you should be using a proxy server: Go to the Chrome menu > Settings > Show advanced settings... > Change proxy settings... > LAN Settings and deselect "Use a proxy server for your LAN".

Error code: ERR_TIMED_OUT

REASON:

Browser Cache issue

ISP/Internet connectivity issue reaching the site

Godaddy is having an issue Overload etc..

ANSWERS: 

1. Try flushing your DNS locally on your computer 

by opening up command prompt>ipconfig /flushdns

That will refresh the DNS cache

2. Try a different Internet Browser

3. Reset your Internet connection

4. The one that fixed it for me is waiting about 10 minutes and trying again

SPF Record error when sending mail 551 5.0.0 Rejected

If you get the following error when sending a message, as a bounce back NDR notification
Remote Server returned '<mx.mail.google.com #5.0.0 smtp; 551 5.0.0 Rejected, look at http://www.openspf.org/why.html?sender=al@topel.com&ip=69.84.129.239&receiver=mailin1-trm.thomsonreuters.com>'

This means that the recipient server is doing an SPF record check and it doesn't match. 

What needs to match? 

The IP of the server you are using needs to be added to the SPF record also known as a TXT record in your DNS you can perform an SPF look-up by going to: 

http://mxtoolbox.com/SuperTool.aspx?action=spf%3a&run=networktools

Explained: 

Sender Policy Framework Why

Why did SPF cause my mail to be rejected? What is SPF? SPF is an extension to Internet e-mail. It prevents unauthorized people from forging your e-mail address (see the introduction). But for it to work, your own or your e-mail service provider's setup may need to be adjusted. Otherwise, the system may mistake you for an unauthorized sender. Note that there is no central institution that enforces SPF. If a message of yours gets blocked due to SPF, this is because (1) your domain has declared an SPF policy that forbids you to send through the mail server through which you sent the message, and (2) the recipient's mail server detected this and blocked the message. mailin1-trm.thomsonreuters.com rejected a message that claimed an envelope sender address of al@topel.com. mailin1-trm.thomsonreuters.com received a message from zixvpm03.reflexion.net (69.84.129.239) that claimed an envelope sender address of al@topel.com. The domain topel.com has not published an SPF policy. It is possible that the receiving mail server refuses all mail from domains that do not have an SPF policy. How can I reference this web page for explaining SPF results? This web page is a public service of the SPF project. SPF implementations can (and do) use it to help explain the results of SPF checks by presenting to users a parameterized link to this page. See the "Why?" page documentation for details on how this works. Edit text of this page | View other revisions Last edited 2008-04-04 13:27 (UTC) by Frank Ellermann (diff)