• Resolved laurentm99

    (@laurentm99)


    Hi,

    One of the most important feed in my field is: http://blog.geneanet.org/index.php/feed/rss2

    This link works in my browser and, for example, in Feedly, but it does not work with RSS Aggregator. I get a “Retrieved unsupported status code “403”” error.

    I contacted the website’s support team, and they gave me another URL: https://www.geneanet.org/blog/feed?lang=fr&page=1. Unfortunately, this one does not work either.

    Could you please help me figure out what the issue might be?

    Thank you in advance.
    Laurent

    • This topic was modified 1 week, 1 day ago by laurentm99.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Hendra Setiawan

    (@hendcorp)

    Hi @laurentm99

    Thanks for including both URLs, that made this quick to check.

    The problem is not your settings or the plugin. Both Geneanet URLs are protected by Cloudflare, and Cloudflare responds with a “Just a moment…” browser check instead of the feed.

    Your browser gets past that check because it can run it. Feedly most likely gets through because Cloudflare usually lets well-known feed readers pass. A WordPress site fetches feeds from its server and cannot complete a browser check, so Cloudflare refuses the request with a 403, which is the error you are seeing. I tested both URLs from our side and got the same 403 and the same check page every time, including with a regular browser user agent. So changing the plugin’s request settings will not get around it.

    The fix has to come from Geneanet. Since you are already in touch with their support team, you could send them something like this:

    “Your RSS feeds (https://www.geneanet.org/blog/feed and https://blog.geneanet.org/index.php/feed/rss2) return a Cloudflare challenge (HTTP 403, “Just a moment…”) to feed readers that run on a server, such as WordPress plugins. Could you exclude your feed URLs from the Cloudflare challenge, or allow my server’s IP address?”

    If they go with the IP option, your web host can tell you your server’s outgoing IP address.

    Once they have made the change, the source should import normally on its next scheduled update, and there is nothing else to change on your side. If they recommend a different feed URL, just replace the one in your source.

    If the source still shows an error after that, please let us know what it says. If it is the same 403, the Cloudflare check is still in place and Geneanet will need to take another look. If it is a different error, we will look into it from there.

    Thread Starter laurentm99

    (@laurentm99)

    Hi Hendra,
    It’s working now. Thanks to your guidance, Geneanet has given me access to its feed.
    Thank you very much for your help.
    /Laurent

    Plugin Support Hendra Setiawan

    (@hendcorp)

    Hi @laurentm99

    That’s great news. Thanks for letting us know!

    It looks like the change Geneanet made on their side was the missing piece, so going back to them with the details was the right move 🙂

    If you have a minute, a quick review would mean a lot to us. It helps other users find the plugin and is always great feedback for our team.

    Glad to hear everything is working now. If you run into any other issues in the future, feel free to start a new topic, and we’ll be happy to help.

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

You must be logged in to reply to this topic.