“Error Undefined” with fast-indexing-api after 1.0.0

#299861
  • Resolved Gordan Bobic
    Rank Math free

    With fast-indexing-api, everything works fine.

    With any version later than that (1.1.0, 1.1.1, 1.1.2), every submission results in “Error undefined” response.

    Restoring the 1.0.0 plugin directory makes everything work again.

    Tried generating a new key and updating the key, but it makes no difference. 1.0.0 always “just works”, every version after that errors out.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Hello,

    Thank you for contacting Rank Math and bringing your concern to our attention. I’m sorry for any inconvenience this issue may have caused you.

    Can you please share the Raw Response from the Indexing API?

    Also, please share the URL you are trying to submit for us to check.

    Looking forward to helping you.

    Thank you.

    Example of URL: https://shatteredsilicon.net/mariadb-mysql-support/
    It happens on any and every URL I try to submit. With 1.0.0, everything works, every later version responds back with “Error undefined”.

    Raw API response:
    16:43:18 getstatus: https://shatteredsilicon.net/mariadb-mysql-support/
    {
    “readyState”: 4,
    “responseText”: “<p>There has been a critical error on this website.</p><p>Learn more about troubleshooting WordPress.</p>”,
    “status”: 500,
    “statusText”: “Internal Server Error”
    }
    ——————————————————–

    If I downgrade back to 1.0.0, it returns success and raw API response is:

    16:45:46 getstatus https://shatteredsilicon.net/mariadb-mysql-support/
    {
    “url”: “https://shatteredsilicon.net/mariadb-mysql-support/&#8221;,
    “latestUpdate”: {
    “notifyTime”: “2021-11-29T17:21:47.904907281Z”,
    “type”: “URL_UPDATED”,
    “url”: “https://shatteredsilicon.net/mariadb-mysql-support/&#8221;
    }
    }
    ——————————————————–

    Hello,

    5xx errors are usually caused due to server misconfiguration or other server issues. Having the error log file will give a clear idea of why this might be happening.

    You can follow this guide to enable debug mode in WordPress to get the error log
    https://www.wpbeginner.com/wp-tutorials/how-to-set-up-wordpress-error-logs-in-wp-config/

    Or you can ask your web host and they should be able to help you locate the log files.

    Looking forward to helping you with this one.

    So why does it work with v1.0.0 but hits a 500 error with v1.1.2? The website doesn’t break with 1.1.2, everything still works fine, it is just the indexing that thinks it returns 500.

    Hello,

    Could you please share the recent error log from your server so we can determine what’s causing this issue? You may ask your hosting provider for the logs.

    Looking forward to helping you with this one.

    As far as I can tell, the error is caused by this:
    [Wed Dec 08 10:18:34.094984 2021] [autoindex:error] [pid 2148879:tid 281471747088336] [client 172.70.34.11:38410] AH01276: Cannot serve directory /usr/share/wordpress/wp-includes/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive, referer: http://www.google.com

    This doesn’t happen with 1.0.0, but it does happen with 1.1.2.

    Hello,

    We might need to take a closer look at the settings. Please edit the first post on this ticket and include your WordPress & FTP logins in the designated Sensitive Data section.

    Please do take a complete backup of your website before sharing the information with us.
    Sensitive Data Section

    It is completely secure and only our support staff has access to that section. If you want, you can use the below plugin to generate a temporary login URL to your website and share that with us instead:

    https://wordpress.org/plugins/temporary-login-without-password/

    You can use the above plugin in conjunction with the WP Security Audit Log to monitor what changes our staff might make on your website (if any):

    https://wordpress.org/plugins/wp-security-audit-log/

    We really look forward to helping you.

    Hello,

    Since we did not hear back from you for 15 days, we are assuming that you found the solution. We are closing this support ticket.

    If you still need assistance or any other help, please feel free to open a new support ticket, and we will be more than happy to assist.

    Thank you.

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

The ticket ‘“Error Undefined” with fast-indexing-api after 1.0.0’ is closed to new replies.