We recently installed a Barracuda firewall and accidentally left “Proxy” on. This caused our IP to used as a spam relay which got our IP put on a blacklist. A trace route from our server to mtb.com showed the packets getting to MTB.com and stopping. We assumed it was MTB.com blocking the ip.
MTB said they get their blacklist for outside sources. They directed me to the following site were I was able to submit a request to get the IP off of the blacklist.
I could see that the IP was showing as suspect. I clicked on the “IP Reputation” and submitted the IP for review. I knew the proxy issue was resolved the IP should be cleared. This didn’t resolve the issue.
I discovered Barracuda has their own IP blocked. This showed our IP as not having a “poor” reputation.
Moving a customers WordPress site to a new hosting plan I ran into this error.
This turned out to be an semi-easy fix. The website size was too large for the hosting. Well not really; however, Akeeba requires 2.5 times the size of the site to fully extract the site.
I looked at the website files to see where I could trim some fat. The site was 400 megs. There was a folder called “wp-snapshots” which held a backup. I removed all the extraneous files including my first Akeeba backup. Made a new backup which was only 40 megs. This time when I ran Kickstart the site installed without an issue.
Had a customer who’s computer was taking hours to start. The update would install automatically. When the user would shut down or restart the update would install which took an hour and requires a reboot. The machine when rebooting would take a long time to install the update. It would get to 100% run into an error and would have to uninstall the update.
Windows 10 doesn’t allow a user to not install updates. Suggestions said to run SFC /now in the command prompt as the administrator. For the scan came back with no errors.
I tried the Windows updater trouble-shooter tool, but this didn’t fix the issue. Here is the link I used.
There were two updates for this Cumulative Update. The main update and the Security update.
I installed the main update. It took a couple of hours. I tried to run the second update; however, it said I had the wrong version. The update packages came from the same page, so I assumed I just needed to restart.
The machine took 6 hours to restart. While restarting it said it was installing the updates do not restart. When it got to the end it said there was an error and un-installing the update.
The winner was to go into “Programs and Features”. In the “Windows” updates area find the troubling KB and remove it. Run the update manually and this should resolve that issue.
Had a customer call in because he was on the LA Times website and clicked on a link that caused his browser to pop-up a Microsoft warning. The warning said he was infected and needed to pay. He hit control-alt-delete and closed chrome. He restarted his machine and called us.
I opened Chrome and looked at the start page. It was set to “http://www.google.com/ig/redirectdomain?brand=TSND&bmod=TSND”. When I put that URL into another browser it took me to just Google. I figured the rest was unecessary and reset his home page to just be “http://www.google.com”.
I downloaded a rootkit scan tool from Bleeping Computer and ran a quick scan. We also use Vipre Anit-virus. I updated the difinitions and ran a full deep scan with Vipre. Nothing else was wrong.
We got asked to help with a SPF record to be added because the client is starting to use My Emma for email marketing.
The client is using Office 365 for email and a Godaddy reseller account for their domain. I logged into their reseller account. Went to Domains and clicked on “DNS Zone File”. Clicked on the pen and paper icon to edit this record.
Here was the original setting:
v=spf1 include:spf.protection.outlook.com -all
I changed it to: ;
v=spf1 a mx include:e2ma.net include:spf.protection.outlook.com -all