ERROR: The feed cannot be parsed after migration | ww.wp.xz.cn

Resolved Anonymous User 14746719
(@anonymized-14746719)

7 years, 4 months ago

Hi,

I just migrated a site between hosts and also installed an SSL so originally I had a feed URL of http://www.northantsvoice.co.uk/feed but now it is https://www.northantsvoice.co.uk/feed

I can access the feed URL perfectly fine

However, from another WordPress site I just get the error:

ERROR: The feed https://www.northantsvoice.co.uk/feed cannot be parsed. Simplepie said: A feed could not be found at https://www.northantsvoice.co.uk/feed. A feed with an invalid mime type may fall victim to this error, or SimplePie was unable to auto-discover it.. Use force_feed() if you are certain this URL is a real feed.
You should use the Force Feed or Change User Agent features of WPeMatico Professional

Any ideas on what may be wrong?

Viewing 2 replies - 1 through 2 (of 2 total)

Plugin Contributor manuelge
(@khaztiel)

7 years, 4 months ago

Hi miketurnermk

Try activating the “Force Custom Simplepie Library” option from WPeMatico Settings.

If the problem continues, create a ticket in our support system to give you a better help and we can take a better control over your case.

Regards,
Manuel

Thread Starter Anonymous User 14746719
(@anonymized-14746719)

7 years, 4 months ago

Just to update this thread rather than leaving it blank with no conclusion…

We investigated further and it seems for whatever reason that the user agent that is being set by the plugin for the SimplePie library is returning a HTTP 400 error.

I do believe the issue to potentially be at my host as this only occurred after the migration. I think possibly the firewall they have is seeing this traffic with a strange user agent and rejecting it.

Unfortunately the plugin doesn’t support being able to set a custom user agent without paying for the premium version although Manuel has been very helpful with providing suggestions.

Currently I await to hear from my website hosting company (SiteGround) with regards to whether this is getting caused by the Firewall.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘ERROR: The feed cannot be parsed after migration’ is closed to new replies.

2 replies
2 participants
Last reply from: Anonymous User 14746719
Last activity: 7 years, 4 months ago
Status: resolved