API REST

Thanks for using our plugin!

This error could be caused by different reasons. We’ve create an article about troubleshooting this issue: https://cusrev.freshdesk.com/support/solutions/articles/43000054875-plugin-not-able-to-receive-reviews-because-wp-rest-api-is-disabled

I hope this helps.

I have reviewed the article and everything is correct. I made a purchase myself and I was able to comment on the product without any problem. I receive the comment, it allows me to approve it, it appears in comments of the cilentes …, everything is fine. The only thing is that in diagnosis of the plugin I get that warning since the last update. Is that important?

Thank you

Hello Ivole again, please can you answer me if this error message is important ???, even though everything works ??
And I would like to add that this happened since the last update.
Thank you very much and forgive the inconvenience.

If everything works fine, you can safely ignore this error message.

There were no changes to the diagnostics screen in the last update. It is difficult to say why it shows the error without being able to see detailed error description. We will add detailed error log in the next version of the plugin and then you should be able to tell more details about the error.

Ok, thank you very much

Hi Ivole,

Ufff, now I get this:

error code: 503; Error message: Service Unavailable; Details:
503 Service Temporarily Unavailable

I have disabled and activated the plugin and now I get the following error:
Additional information can be found in this support article. Error message: cURL error 28: the operation ran out after 10000 milliseconds with 0 bytes received

Can you please let me know what happens if you create a test review? Will it still work or does it fail now?

Hello Ivole,
If it works but only with the manual method. That is, I receive the comments but they are not sent automatically, I have to send them manually from orders.
I have the REST API enabled, I do not use any security plugin, I have consulted my hosting and there is nothing suspicious.
I use the Storefront theme, which is supposed to be the most compatible with woocommerce.

Thanks for answering Ivole.

To be honest, I don’t really understand you. Can you please clarify:

1. What do you mean by “manual method”?
2. What error message do you have now on the Diagnostics screen?

Hello Ivole,
This is the new message: The plugin will not be able to receive reviews because REST API is disabled. Additional information can be found in this support article. Error message: cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received.

I’m sorry for not having explained myself well before.
I mean, all the functions of the plugin are correct, except this: even having activated send revisions automatically, it does not send them. I can only send them from customer orders, by clicking on the button and manually.

I have the REST API enabled.

Thanks for answering.

Thanks for providing additional details.

1. The cause of cURL error 28 is most likely that your server is blocking connections to your own site. Some hosts don’t allow sites hosted in their servers to connect their self using cURL. It’s very common for a WordPress site to perform connections to itself (e.g. AJAX requests) and I can’t see any valid reason to apply this blocking in a server. But for some reason there are many hosts doing this (specially in cheap hosting plans). So you will want to contact with your host support about this and request to remove that limitation if it’s set in the server. Also, see more information here: https://www.samuelaguilera.com/post/curl-error-28-wordpress

2. Can you please share a screenshot of “Review Reminder” page of the plugin’s settings?

Hello Ivole.

Thank you very much for the reply.

I have made the query to my hosting. I’m waiting for you to respond. As soon as I know something, I’ll tell you.
I leave this screen capture of the plugin diagnostic.

A greeting.

https://drive.google.com/file/d/1xdCRCj0ssGXq5jHnQhRPVq7VjJoMfKZq/view?usp=sharing

Ivole, is already solved. It was a security setting in the hosting. They have responded by telling me that an adjustment in security has diminished and I have verified that everything is now correct.

Thank you very much for your interest, patience and perseverance. All this makes your plugin fantastic !, with an unbeatable support.

Regards!