rest_no_route When running Indexing

  • Resolved SGURYGF

    (@sgurygf)


    4 years, 4 months ago

    Hi,

    I’ve been having this problem in the last releases (currently running 15.2)

    Even though under /wp-json/yoast/v1/ I can see the routes listed such as

    /wp-json/yoast/v1/indexation/post/
    /wp-json/yoast/v1/indexation/terms/
    /wp-json/yoast/v1/indexation/prepare/
    /wp-json/yoast/v1/indexation/post/

    however visiting them /wp-json/yoast/v1/indexation/, /wp-json/yoast/v1/indexation/prepare/ is returning

    {“code”:”rest_no_route”,”message”:”No route was found matching the URL and request method”,”data”:{“status”:404}}

    Thus as you understand, I am getting the well known “Oops, something has gone wrong and we couldn’t complete the optimization of your SEO data. Please click the button again to re-start the process.” error.

    All other yoast routes are working fine. Only the indexation ones aren’t.

    I’ve read other posts mentioning conflict with WPML or translation plugins, I don’t have any of those.

    No, I haven’t tried uninstalling/reinstalling the plugin because I assume updating it does the same thing. It should cater for any db changes.

    Any ideas?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Maybellyne

    (@maybellyne)

    Hello @sgurygf,

    Thanks for reaching out.

    We have seen a similar report but we want to be sure.

    You mentioned that visiting /wp-json/yoast/v1/indexation/prepare/ returns a 404 error. Can you confirm if there is a 301 redirect from a URL without trailing slash to a URL with a trailing slash (/wp-json/yoast/v1/indexation/prepare redirects to /wp-json/yoast/v1/indexation/prepare/) before the 404 error? The 404 URL corresponds to the WordPress REST API that our plugin uses to fetch information of your posts.

    Thread Starter SGURYGF

    (@sgurygf)

    Hi Maybellyne,

    That is correct.

    Requesting /wp-json/yoast/v1/indexation/prepare redirects (301) to /wp-json/yoast/v1/indexation/prepare/

    Plugin Support Maybellyne

    (@maybellyne)

    @sgurygf

    We suspect that the redirect is caused by a server rule in your .htaccess file. You may want to have a look at this forum thread where a similar issue is described: https://github.com/johngodley/redirection/issues/673.

    If you are unsure what server rule is causing the redirect, we’d recommend that you reach out to your web hosting provider and bring this issue to their attention. They’ll be able to assist you further and hopefully review and remove any offending rules in your server that are causing that redirect.

    Once the redirect is fixed, we’d expect the “SEO Date” and the other functions to run without any issues.

    Thread Starter SGURYGF

    (@sgurygf)

    I have excluded wp-json from the redirection and now it’s working fine!

    Thank you ??

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘rest_no_route When running Indexing’ is closed to new replies.