I can not revalidate my feed that has been active for years

Question

Level 1

8 points

I can not revalidate my feed that has been active for years

Today I added the SSL protocol on my site, and I had to revalidate my feed address in podcastsconnect.apple.com to include https at my address.

But it seems that he is not recognizing the same feed that has always been there.

Whenever I include the s in my feed link and send to revalidate it displays the message: "Your feed could not be sent. The feed does not have an explicit element tag or the tag is empty."

I visually check the feed and the <itunes: explicit> clean </ itunes: explicit> tags seem to be there.

My feed is: https://alexmansour.com/category/fotometrando/feed/

Other than that, I have 3 other podcasts managed on the same site, all are managed via Blubrry Powepress, and the same problem appeared once for the other changes and on the second attempt they were validated, only the link above that is allowed without validation.

The other feed are:

https://alexmansour.com/category/caveira-e-ossos/feed/

https://alexmansour.com/category/skull-and-bones/feed/

https://alexmansour.com/feed/podcast/

What should I do to correct the problem of the first FEED?

Posted on Apr 4, 2018 9:44 AM

Reply

Answer 1

alexmansour Author

Level 1

8 points

Apr 5, 2018 1:04 AM in response to Roger Wilmut1

After much trying, clearing the cache several times, the feed has finally been cleared. I think the problem really has to do with some persistent cache that kept on existing, even after it was deleted. The web has these Stranger Things, sometimes. (I.e.

Thanks for your help, Roger.

My best regards!

Reply

Answer 2

Apr 4, 2018 11:06 AM in response to alexmansour

There wasn't when I checked it, nor at first when I checked it just now: but then I reloaded and the tag appeared. This is indicative of a cacheing problem, though I don't know whether it's at my ISP or your server - more likely the latter since I got it in both cases on a first call, so it wouldn't have been accessed before to be cached. I also got the same error in Podcasts Connect. I don't know how you would get round this - try actually deleting the feed from the server and then re-uploading it, rather than just replacing it.

Reply