Fix Feedburner Error 502/503 After Moving Feeds From Feedburner to Google

Feedburner.com one of most favored feed publishing webservice is on a verge of death, after Google has Acquired Feedburner.com there is hardy any improvement in service & features or customer support. Recently Google has started promoting feed migration from feedburner to Google.

As per Google by moving your feeds from feedburner to google you can monetize your feeds with Google Adsense and use Mybrand to serve feeds from your own domain for free . Initially the feed migration process was manual and you need to email Google Adsense to initiate feed moving process.

Jump to Fix for Feedburner Error 502 & 503

However recently Google has announced they are going to move all account by February 28, 2009 and if your account has not been updated till that time then it will start returning Error 404.

Few week ago when I had logged into my feedburner account I was greeted with following message and without thinking a miniute I immediately rushed to move my feeds to google. The process was moving the feeds was extremely simple but issue started right after moving feeds to google.

I was aware of fact that feedburner count will start fluctuating and as per google the process may take a day or two to completely move the feeds. I was waiting patiently but even after a week the feedburner count was showing 0 readers.

To check what’s wrong with my feed I tried access my feed url. I was surprised to see my feed url was retuning Error 502.

Initially I thought it has to be Google Feedburner glitch since I had recently migrated my feeds but when for consecutive three days I was getting same error I got frustrated and started searching on google.

I came across this post of officially Google Feedburner Status blog. Which was saying that the error is due to Web hosting not allowing Google Feedburner server to access the blog feeds and they have provided fix for Feedburner Error 502.

How to Fix Feedburner Error 502 & 503 After moving Feed from Feedburner to Google

For Shared Server Hosted Blogs and Websites

1. Since your blog/website is hosted on shared server you can’t edit any files of Webserver. You need to open a ticket with your webhosting customer support and ask them to add following IP in webserver whiltelist.

209.85.132.136
74.125.44.136

2. That’s it, now wait till your webhositng support team to add those ip in whitelist. The Error should get resolved once those IP are added to webserver ip list.

For Virtual Private Hosting or Dedicated Server hosted Blog or Websites

If you have cPanel/ Webhosting manager on your VPS or Dedicated server the follow below steps top whitelist an IP.

1. Login to your Webhosting Manager

2. Go to: ConfigServer Security&Firewall

3. Allow IP address ___________ through the firewall and add to the allow file

Enter Following Ip address.

209.85.132.136
74.125.44.136

4. Fill in the above blank

5. Click allow

6. Restart Firewall

That’s it Now access your blog feed URL to confirm.

© 2009, Microments. All rights reserved. On republishing this post you must provide link to original post.

• Tools we use on an almost daily basis – Search Engine Optimization Tools and SEO News Feeds
• Solution for WordPress Feed XML Parsing Error – XML or text declaration not at start of entity
• Integrate Google Talk Badge To Your Blog and Enjoy Realtime Chatting with Readers
• List of useful blog addons and plugins
• To Do List to Increase wordpress blog loading speed – Remove Themes Tags