Resync Didn't Work "There is an issue that must be addressed with your source feed for the feed" Null

[MT]

Feedburner stopped updating our rss / xml raw file.
After trying everything else, I tried to "Resync" and got an error "

There is an issue that must be addressed with your source feed for the feed
NULL

No explanation what the error is or what needs to be fixed.  Nothing changed on our end AFAIK.
Our raw RSS still validates on "Feed Validator"

The feedburner feed doesn't validate with error on lastbuildate format 

<lastBuildDate>Tue, 28 Jun 2016 00:00:01 UTC</lastBuildDate>

but we don't have access to edit feedburner, and in any case, the raw file we're trying to resync is validated, but it won't resync.


Any suggestions, thanks?

[thebudd...@gmail.com]

We are experiencing this exact same issue. Updates are broken since July 3 with "null" reason as reported above. Feeds pass the validator, and there is nothing in feedmedic nor podmedic.

FB: http://feeds.feedburner.com/BuddyPodcast

Source: http://buddypodcast.com/feed/index.xml

[Les baleines et les coquillages]

Same issue here. That's somehow reassuring as it means the issue is probably on feedburner's side.

Tried to ping, and then resync, nothing works and the feedburner feed does not update while the source feed works fine.

It would be great if somebody at google could step in and solve that issue!

FB: http://feeds.feedburner.com/lesbaleinesetlescoquillages
Source: http://www.lesbaleinesetlescoquillages.com/feed

[Les baleines et les coquillages]

Hi all,

The solution is to configure your web server so that it accepts IPv6 requests. It seems that feedburner only tries to connect through IPv6 since recently and that sites that can only be accessed using IPv4 no longer have their feeds updated.

I've just done that on my sites and resyncing / pinging worked straight away, I hope it'll work for you as well.

[Nathan Smith]

Thanks for the work-around.

The real solution is for Google to repair what broke, as I can hardly believe this was intentional. I think it is a bit soon for support for IPv4 to be deprecated, especially without an announcement.

Apparently nobody at the company looks at this forum at all. I've stopped using feedburner, possibly losing a sizable part of my audience.

[Nathan Smith]

And yes, I can confirm what was described above was the issue. I had a AAAA record configured for my domain, but my server was not actually listening on that address. Apparently they just started using IPv6, or they changed something so that it no longer fails back to IPv4 if something is wrong in v6 land. Everything is working now.

So at least the feedburner feed can still update to keep the existing audience up-to-date, but I still won't be relying on this unsupported service any more.

[MT]

Thanks for the work-around, but it didn't work for me.  I configured my rss server for ipv6 and tested with ping6, but Feedburner still won't update, and when i try to resync i still get the "NULL" error msg.

Any other suggestions or am i missing something in the workaround?  Anyways, isn't it unlikely that Feedburner/Google would drop ip4 support without notice?

[Thomas Themel]

Just to clarify the above, IPv4 support isn't deprecated, it's just that we now prefer IPv6 to IPv4, so if you have an IPv6 DNS record but don't actually serve on IPv6 it's going to fail. I agree that falling back to IPv4 where available would be nice, but it's not very likely that this will be fixed soon. 

MT, you didn't specify your feed AFAICT, if you let me know (privately if you want) which feed URL you're having problems with I can try to diagnose your problem as well. 

ciao,

Thomas

[MT]

Hello all,

The solution that Thomas suggested worked for us.  We removed the ipv6 AAAA record from our DNS host and the feedburner immediately synced and is now working fine.

Regards All,
Michael

[Nathan Smith]

It would be very helpful if you could update feedburner with a bit more debugging feedback than "null" :-)

[PB]

Facing similar issue on our website http://www.final-yearproject.com/.

Feed is not working and giving below error.

+++++++++++++++++++++++++++++

There is an issue that must be addressed with your source feed for the feed "FINAL YEAR PROJECT'S AND GUIDANCE"

The URL you entered does not appear to be a valid feed. We encountered the following problem: Error on line 3: The element type "link" must be terminated by the matching end-tag "</link>".

+++++++++++++++++++++++++++++

[Matti nescio]

On Sunday, 15 October 2017 10:59:55 UTC+3, PB wrote:

Facing similar issue on our website http://www.final-yearproject.com/. 

What are you actual domain A and CNAME records ? 

Currently they are being masked by your use of Clouldflare. 

(whether Cloudflare even works with Feedburner is another matter; 

using Cloudflare at all with a Blogger-powered blog seems quite pointless)

Right now, you are redirecting http://www.final-yearproject.com/feeds/posts/default to 

http://feeds.feedburner.com/FinalYearProjectsAndGuidance , but because your 

apparently broken domain records, it's trying to go to http://www.final-yearproject.com/feeds/posts/default?alt=rss . 

If it did, it would just result in an endless redirect loop. 

The URL you entered does not appear to be a valid feed. 

Your feed itself is clearly valid : 

https://validator.w3.org/feed/check.cgi?url=http://www.final-yearproject.com/feeds/posts/default?redirect=false 

[PB]

You were correct, cloud flare was the problem. I paused it and now feed sync properly.

I was thinking to implement SSL on my site that is why added Cloudflare NS.