Error: Your IP is Blocked

[Amauri]

Server operating system version

AlmaLinux 8.10

Plesk version and microupdate number

Plesk Obsidian v18.0.67_build1800250205.19 os_RedHat el8

Hi

From some weeks a WordPress website can't be updated by WPToolkit.

I get the mail:

Updates were not installed for the following items:


1. Website "XYZ" (https://example.com): Failed to reset cache for the instance #1: Error: Your IP is Blocked. If you think this is not right, please contact site administrator.

Updates are correctly installed automatically from the website.

The ip is whitelisted on fail2ban.

I dont know where to search, I'm confused

Thanks!

 

[Sebahat.hadzhi]

Hello, @Amauri . Could you please enable debug mode in Plesk, re-attempt the update, and double-check if there are entries logged in /var/log/plesk/panel.log related to extension/wp-toolkit. Thank you in advance. Once the test is completed, please make sure to disable the debug mode.

 

[Amauri]

Hi @Sebahat.hadzhi,

I get more data with debug on:

WARN
extension/wp-toolkit
Error while loading themes: Error: Your IP is Blocked. If you think this is not right, please contact site administrator.

ERR
panel
PleskUtilException: '/usr/local/psa/admin/bin/filemng' 'user' 'exec' '/var/www/vhosts/xyz/httpdocs' 'timeout' '60' '/opt/plesk/php/8.3/bin/php' '-d' 'safe_mode=off' '-d' 'display_errors=on' '-d' 'opcache.enable_cli=off' '-d' 'open_basedir=' '-d' 'error_reporting=341' '-d' 'max_execution_time=60' '-c' '/var/www/vhosts/system/xyz/etc/php.ini' '/usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wpt-wp-cli.php' '--path=/var/www/vhosts/xyz/httpdocs' '--no-color' 'theme' 'auto-updates' 'status' '--all' '--enabled-only' '--field=name' '--skip-plugins=false' '--skip-themes=false' failed with code 1.

stdout:


stderr:
Error: Your IP is Blocked. If you think this is not right, please contact site administrator.

file: /usr/local/psa/admin/plib/Service/Agent/Transport/Local/Exec.php
line: 60
code: 0
trace: #0 /usr/local/psa/admin/plib/Service/Agent/Transport/Local.php(23): Service_Agent_Transport_Local_Exec->process(integer '0', object of type Service_Agent_Command_Exec, object of type Service_Agent_Transport_LocalTransaction)
#1 /usr/local/psa/admin/plib/Service/Agent.php(94): Service_Agent_Transport_Local->process(string '4a9995e17d68d418c670df05db83dbd2', array)
#2 /usr/local/psa/admin/plib/modules/wp-toolkit/library/Capability/WpCli/LocalPleskLinux.php(26): Service_Agent->commit()
#3 /usr/local/psa/admin/plib/modules/wp-toolkit/library/Capability/WpCli/WpCli.php(126): PleskExt\WpToolkit\Capability\WpCli\LocalPleskLinux->call(array, NULL null, array, boolean false, NULL null)
#4 /usr/local/psa/admin/plib/modules/wp-toolkit/library/Capability/Command/Asset.php(429): PleskExt\WpToolkit\Capability\WpCli\WpCli->handleErrorCall(array, NULL null, array, boolean false, NULL null)
#5 /usr/local/psa/admin/plib/modules/wp-toolkit/library/Capability/Command/Theme.php(137): PleskExt\WpToolkit\Capability\Command\Asset->_handleAssetCall(array)
#6 /usr/local/psa/admin/plib/modules/wp-toolkit/library/Service/Instance/InstanceAssetsManager.php(505): PleskExt\WpToolkit\Capability\Command\Theme->getThemesWithAutoUpdatesEnabled()
#7 /usr/local/psa/admin/plib/modules/wp-toolkit/library/Db/Row/Instance.php(1400): PleskExt\WpToolkit\Service\Instance\InstanceAssetsManager->getThemesWithAutoUpdatesEnabled(object of type PleskExt\WpToolkit\Db\Row\Instance)
#8 /usr/local/psa/admin/plib/modules/wp-toolkit/library/Service/Instance/InstanceCache.php(259): PleskExt\WpToolkit\Db\Row\Instance->loadAttributes(boolean true, boolean false, boolean true)
#9 /usr/local/psa/admin/plib/modules/wp-toolkit/library/Service/Instance/InstanceCache.php(213): PleskExt\WpToolkit\Service\Instance\InstanceCache->reloadInstanceAttributes(object of type PleskExt\WpToolkit\Db\Row\Instance, object of type PleskExt\WpToolkit\Model\InstanceResetCacheOptions)
#10 /usr/local/psa/admin/plib/modules/wp-toolkit/library/Service/Instance/InstanceCache.php(143): PleskExt\WpToolkit\Service\Instance\InstanceCache->refreshBaseCache(object of type PleskExt\WpToolkit\Db\Row\Instance, object of type PleskExt\WpToolkit\Model\InstanceResetCacheOptions)
#11 /usr/local/psa/admin/plib/modules/wp-toolkit/library/Service/Instance/InstanceCache.php(96): PleskExt\WpToolkit\Service\Instance\InstanceCache->PleskExt\WpToolkit\Service\Instance\{closure}(object of type PleskExt\WpToolkit\Db\Row\Instance, object of type PleskExt\WpToolkit\Model\InstanceResetCacheOptions, object of type PleskExt\WpToolkit\Updates\InstanceUpdateHelper)
#12 /usr/local/psa/admin/plib/modules/wp-toolkit/library/Service/Instance/InstanceCache.php(141): PleskExt\WpToolkit\Service\Instance\InstanceCache->execute(object of type Closure, object of type PleskExt\WpToolkit\Db\Row\Instance, object of type PleskExt\WpToolkit\Model\InstanceResetCacheOptions, object of type PleskExt\WpToolkit\Updates\InstanceUpdateHelper)
#13 /usr/local/psa/admin/plib/modules/wp-toolkit/library/BackgroundTasksImplementation/Update/MassCheckUpdates.php(90): PleskExt\WpToolkit\Service\Instance\InstanceCache->resetCacheAdvanced(object of type PleskExt\WpToolkit\Db\Row\Instance)
#14 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/plesk/background-tasks/src/Adapter/PleskSimpleTaskAdapter.php(36): PleskExt\WpToolkit\BackgroundTasksImplementation\Update\MassCheckUpdates->run(object of type BackgroundTasks\Adapter\PleskTaskProgressAdapter, object of type BackgroundTasks\DataStorage\PleskTaskDataStorage)
#15 /usr/local/psa/admin/plib/Task/Control/Sdk.php(49): BackgroundTasks\Adapter\PleskSimpleTaskAdapter->run()
#16 /usr/local/psa/admin/plib/Db/Table/Broker/LongTasks.php(178): Plesk\Task\Control\Sdk->run()
#17 /usr/local/psa/admin/plib/Db/Table/Broker/LongTasks.php(113): Db_Table_Broker_LongTasks->_syncStart(object of type Db_Table_Row_LongTask)
#18 /usr/local/psa/admin/plib/Task/Async/Executor.php(54): Db_Table_Broker_LongTasks->runTaskWithinExecutor(object of type Db_Table_Row_LongTask)
#19 /usr/local/psa/admin/plib/scripts/task-async-executor.php(6): Task_Async_Executor->execute()

 

[Sebahat.hadzhi]

Thank you for the update. Unfortunately, I cannot identify the reason for the issue. What I can suggest for further troubleshooting is to try temporarily disabling fail2ban, any other server firewall, and WordPress security plugins, to isolate the potential reason. If you have the option to get in touch with Plesk's support, they can perform a further investigation. If not, please consider getting in touch with your hosting provider so they can forward the request to our support staff.

 

[AYamshanov]

Interesting. As additional option, I recommend checking what security plugins you have in WordPress and trying to disable them one by one to find out which one blocked the IP address.

 

[Amauri]

Thanks for pointing me in the right direction! I thought it was related to Plesk, but it was actually a WordPress plugin. Problem solved

 

[AYamshanov]

I am glad to hear that! But what plugin was it?

 

[Amauri]

WPArmor. A fix is coming on their side

127.0.0.1 banned

127.0.0.1 banned Amauri (@amauric) 16 hours, 58 minutes ago Hi, On one of my installation 127.0.0.1 get banned and automatic updates from Plesk was blocked. I guess it can be a good idea to whiteli…

wordpress.org