veppa

It might be server timeout or browser related issue. Can you check console log in chrome browser (by pressing F12 key) for related errors?

Thank you for reaching out.

Increased custom rule limit to 30 in version 1.3.6.

Hope it meets your requirements.

Regards.

Thank you for reporting.

Fixed in version 1.3.6.

HTTP Requests Manager plugin is not related to search.

I found another one in WordPress repository that might help. https://www.ads-software.com/plugins/search-limiter-blocker/

Regards.

Recently in version 1.3.4 I added force blocking to “Block external requests” and “Block external requests (allow www.ads-software.com only)” modes using wordpress constants. Now other plugins cannot remove that block.

For “Smart block” I have another idea that can force blocking rules. Will check it soon and keep you updates.

Released fix with version 1.3.5.

Regards.

Thank you for reporting. Will add fix to next release. In couple days.

Ok. In above code what happens when $ids emty because of network error or blog blocking external requests.

It will store empty ids. Then on next page will request ids from remote server again. And this will be repeated on every page.

Issue can be reproduced following these steps:

• You block external URL requests by defining WP_HTTP_BLOCK_EXTERNAL as true in your wp-config.php file. Ref https://developer.www.ads-software.com/reference/classes/wp_http/block_request/
• wait 1 day until transient expires or delete it.
• navigate in admin with “query monitor” to view api calls as you visit pages.

Regards.

@amirhossein7

Very interesting case. From screenshot I can see that 2 secont timeout applied. So plugin works partially.

Then other part that blocks requests is not executed.

My guess is first plugin “nfwplus” firewall removes related hook added by “HTTP Requests Manager”. Then all other requests pass without being blocked as well.

Once hook removed nothing will be blocked.

Which is sad. Because you cannot control other requests (by other plugins or core ) as well on your own WordPress website.

I have not seen their code.

Also I do not want to force add that blocking hook back. We both use default WordPress features. I add they remove.

Only thing I can do probably add some message showing that hook was removed by other plugin. And blocking or logging will not work. So other users will know why my plugin is not working as expected.

Thank you for reporting and screenshot. It helped a lot.

Regards.

@fidoboy your case is different than original thread starter.

You have 2 part question.

First part

Request timeout in 2 seconds even if it is has “always” “allow” rule.

I released version 1.3.3 that removes “smart block” limitation from requests that have custom rule “allow”. In your case 2 second timeout will not be applied to requests to your own domain because you added it as “allow” rule.

I experinced similar problem with “allow” rule limitation here https://veppa.com/debug-wp_http/#backup-error then fixed bug in plugin version 1.3.3.

Then second part

When you switched to “only log” mode request to your domain timed out in 5 seconds.

This 5 second timeout is default for all requests in WordPress. Which is defined by WordPress. It is not altered by “HTTP Requests Manager” plugin whfn using “only log” mode.

In this case request timed out because it didn’t get any response from you server in 5 seconds. This happens when responding server is busy. It is normal. And plugin does not alter or limit any communication in “only log” mode. It just logs requests.

Hope this clarification helps.

Please start separate thread if you have other issues.

Regards.

It seems like some plugins should be always allowed.

Can you please try following setup.

Say for example:

a1, a2 — plugins or theme break your website when they are blocked or limited by smart block.

b1, b2 — plugins that do not effect WordPress when they are blocked. And you want to block them.

1. First create rule that will allow “a1” and “a2” plugins “always” “everywhere”.
2. Then switch to “smart block”.
   • Test if website works. Then block “b1” and “b2” plugins.
   • If website crashes then it means there is some other plugin “a3” that should always be “allow”ed. This “a3” also can be one of “b1” or “b2” plugins.

In other words if your website crashes/breaks when blocked eather by “smart block” or by “custom rule” then some plugin needs to be “always allowed” via “custom rule”. You can find that plugin by guessing it and allowing. Then switching to “smart block”.

Some premium plugin or theme that checks for license might need to be always allowed. So allow them first before switching to “smart block”.

Hope this helps.

Please let me know how it goes.

Regards.

Problem resolved. It seems like FTP was partially uploading some files of plugin causing this fatal errors.

Plugin worked when updated using wpcerbers own repository “Use WP Cerber’s plugin repository” inside main settings.

Regards.

I found reason why my custom fields stopped showing in edit page.

It was disabled by mistake in “Pods admin” -> “Settings” page. Core : “Allow Pods to create and manage custom fields on any content type created/extended through Pods” option value should be “Enable creating custom fields with Pods” to view and edit custom fields.

Posted it here in order to help other having similar issued by mistake.

Regards.

Added priority loading to plugin via MU plugin functionality. When enabled, plugin should load before other plugins and detect/manage/block as much requests as possible.

Priority loading released with version 1.3.1.

Regards.

Increased request timeout to 2 seconds. Update released in version 1.3.1.

Regards.