REST API endpoint /webp-converter/v1/paths/ returns 404

  • Resolved vorteri

    (@vorteri)


    8 months, 3 weeks ago

    Hi, I’ve been encountering a persistent issue with the plugin. When accessing the settings or running conversions, I see this error:

    An error occurred while connecting to the REST API. 404 - Not Found (https://mydomain.com/wp-json/webp-converter/v1/paths) Here’s what I’ve already tried:

    • Reinstalled the plugin completely
    • Verified that REST API works globally:
      https://mydomain.com/wp-json/ loads fine
    • But https://mydomain.com/wp-json/webp-converter/v1/paths/ returns:{ "code": "rest_no_route", "message": "No route was found matching the URL and request method.", "data": { "status": 404 } }

    I also checked for security plugins or code disabling REST API — nothing is blocking it. Additional info:

    • Plugin version: latest (free version)
    • REST API is working fine for other plugins and endpoints
    • Another site I own using the same plugin behaves the same way (404 on that endpoint) but the plugin works fine there

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

Viewing 1 replies (of 1 total)
  • Plugin Author Mateusz Gbiorczyk

    (@mateuszgbiorczyk)

    8 months, 3 weeks ago

    Hi @vorteri,

    Thank you for your message.

    Your website is redirecting from URLs that don’t end with a “/” to URLs that end with a “/.” This means they’re forcing a trailing slash.

    The problem isn’t that there’s a redirect, but that it’s being implemented incorrectly. The plugin is making a POST request to the URL /wp-json/webp-converter/v1/paths, and then something is redirecting it to a GET request to the URL /wp-json/webp-converter/v1/paths/. This shouldn’t happen. If the request is a POST request, the type shouldn’t change.

    Please check the rules in your .htaccess file.

    Best,
    Mateusz

Viewing 1 replies (of 1 total)

The topic ‘REST API endpoint /webp-converter/v1/paths/ returns 404’ is closed to new replies.