• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:
    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Error when adding docker proxy rule to domain

Y

yehudigt

Basic Pleskian
Username:

TITLE

Error when adding docker proxy rule to domain

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian Version 18.0.53 - Almalinux 8.5

PROBLEM DESCRIPTION

I added varnish via docker extension in plesk.
It used to work fine, but after the last update I'm receiving this error when trying to add a docker proxy rule to a domain:
ERROR: TypeError: Cannot assign Plesk\Task\Manager\Helpers\SocketClient to property Plesk\Task\Manager::$client of type Psr\Http\Client\ClientInterface (Manager.php:40)

If I refresh the page Plesk seems like saving the rule, but no modify has been made in the vhost configuration file related to the docker extension and there is no redirect to the specified ports.

STEPS TO REPRODUCE

Add varnish extension to docker (i used million12/Varnish)
Go to domain and select Docker Proxy Rule -> Add

ACTUAL RESULT

ERROR: TypeError: Cannot assign Plesk\Task\Manager\Helpers\SocketClient to property Plesk\Task\Manager::$client of type Psr\Http\Client\ClientInterface (Manager.php:40)

If I refresh the page Plesk seems like saving the rule, but no modify has been made in the vhost configuration file related to the docker extension and there is no redirect to the specified ports.

EXPECTED RESULT

No error and vhost file modified with docker extension added

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Help with sorting out
 
We could not reproduce the issue:

Deploy a million12/varnish docker container on 18.0.52.
Add Docker proxy rule.
Update to 18.0.53.
Try to add Docker proxy rule on a new domain.

Proxy rule is created successfully.

Please provide debug log (without sql_query option) when trying to create a rule (https://support.plesk.com/hc/en-us/articles/12377672365975-How-to-enable-disable-Plesk-debug-mode):

Code: 
[debug]
; Enable debug mode (do not use in production environment)
enabled = on
[log]
; Log messages verbosity level (from 0 to 7)
; 0 - only critical errors, 7 - all including debug messages, default - 3
filter.priority = 7
; Enable logging of SQL queries
;show.sql_query = on
; Enable logging of external utilities calls
show.util_exec = on
; Enable logging of stdin and stdout for external utilities calls (do not use in production environment)
show.util_exec_io = on
 
[2023-06-25 11:09:15.731] 3803:6498043bb257f ERR [panel] TypeError: Cannot assign Plesk\Task\Manager\Helpers\SocketClient to property Plesk\Task\Manager::$client of type Psr\Http\Client\ClientInterface
file: /usr/local/psa/admin/plib/Task/Manager.php
line: 40
code: 0
trace: #0 /usr/local/psa/admin/plib/Task/Manager/Dependencies.php(13): Plesk\Task\Manager->__construct()
#1 (0): Plesk\Task\Manager\Dependencies::plesk\Task\Manager\{closure}(object of type DI\Container)
#2 /usr/local/psa/admin/plib/vendor/php-di/invoker/src/Invoker.php(74): call_user_func_array(object of type Closure, array)
#3 /usr/local/psa/admin/plib/vendor/php-di/php-di/src/Definition/Resolver/FactoryResolver.php(80): Invoker\Invoker->call(object of type Closure, array)
#4 /usr/local/psa/admin/plib/vendor/php-di/php-di/src/Definition/Resolver/ResolverDispatcher.php(71): DI\Definition\Resolver\FactoryResolver->resolve(object of type DI\Definition\FactoryDefinition, array)
#5 /usr/local/psa/admin/plib/vendor/php-di/php-di/src/Container.php(390): DI\Definition\Resolver\ResolverDispatcher->resolve(object of type DI\Definition\FactoryDefinition, array)
#6 /usr/local/psa/admin/plib/vendor/php-di/php-di/src/Container.php(139): DI\Container->resolveDefinition(object of type DI\Definition\FactoryDefinition)
#7 /usr/local/psa/admin/plib/WebServerManager/Adapter/Apache.php(41): DI\Container->get(string 'Plesk\Task\Manager')
#8 /usr/local/psa/admin/plib/Service/Driver/Web/Apache/Base.php(65): WebServerManager_Adapter_Apache->__construct(integer '0', object of type Template_Configuration_Applier)
#9 /usr/local/psa/admin/plib/Service/Driver/Web/Vhost/Apache.php(339): Service_Driver_Web_Apache_Base->_getApacheManager()
#10 /usr/local/psa/admin/plib/pm/WebServer.php(22): Service_Driver_Web_Vhost_Apache->updateWebServerConfiguration(string 'igea.yeb.it')
#11 /usr/local/psa/admin/plib/modules/docker/library/Docker/Db/Table/Row/ProxyRule.php(48): pm_WebServer->updateDomainConfiguration(object of type pm_Domain)
#12 /usr/local/psa/admin/plib/modules/docker/library/Docker/Db/Table/Row/ProxyRule.php(23): PleskExt\Docker\Db\Table\Row\ProxyRule->_updateWebServer()
#13 /usr/local/psa/admin/plib/vendor/plesk/zf1/library/Zend/Db/Table/Row/Abstract.php(493): PleskExt\Docker\Db\Table\Row\ProxyRule->_postInsert()
#14 /usr/local/psa/admin/plib/vendor/plesk/zf1/library/Zend/Db/Table/Row/Abstract.php(439): Zend_Db_Table_Row_Abstract->_doInsert()
#15 /usr/local/psa/admin/plib/modules/docker/library/Docker/Form/ProxyRule.php(101): Zend_Db_Table_Row_Abstract->save()
#16 /usr/local/psa/admin/plib/modules/docker/controllers/ProxyRuleController.php(99): PleskExt\Docker\Form\ProxyRule->process()
#17 /usr/local/psa/admin/plib/vendor/plesk/zf1/library/Zend/Controller/Action.php(516): ProxyRuleController->createAction()
#18 /usr/local/psa/admin/plib/vendor/plesk/zf1/library/Zend/Controller/Dispatcher/Standard.php(308): Zend_Controller_Action->dispatch(string 'createAction')
#19 /usr/local/psa/admin/plib/vendor/plesk/zf1/library/Zend/Controller/Front.php(954): Zend_Controller_Dispatcher_Standard->dispatch(object of type Zend_Controller_Request_Http, object of type Zend_Controller_Response_Http)
#20 /usr/local/psa/admin/plib/pm/Application.php(87): Zend_Controller_Front->dispatch()
#21 /usr/local/psa/admin/htdocs/modules/docker/index.php(5): pm_Application->run()

[2023-06-25 11:09:15.731] 3803:6498043bb257f DEBUG [panel] Execute: '/usr/local/psa/admin/bin/send-error-report'
 
Thank you! The only thing I can add is that I have custom domain templates, but they used to work fine, and before the last update I did not have any problem at all
 
@yehudigt, please provide the output of the following commands:
# rpm -V docker-ce docker-ce-cli docker-buildx-plugin docker-ce-rootless-extras docker-compose-plugin
# dnf list --showduplicates
 
the first command output is blank.
dnf list --showduplicates has a very huge output
 

Attachments

  • dnf.pdf
    1.9 MB · Views: 1
Hi @yehudith,

Could you please tell me the Varnish Backend configuration you have?

I'm trying million12/Varnish with AlmaLinux 8.9 and I get Error 503 Backend fetch failed.

I tried various configurations, but the same result.

Thank you in advanced.
 
It turned out to be in newer OSs, The Plesk is Binding Apache on 127.0.0.1:7080

The Plesk has already implemented a command to change this behavior. :)

#plesk bin apache --listen-on-localhost false
 
You must log in or register to reply here.

Similar threads

Y
Issue Error when adding docker proxy rule
Replies
0
Views
1K
yehudigt
Y
N
Issue Docker Error- Can not reach the admin panel after restart
Replies
1
Views
1K
Peter Debik
P
G
Resolved Docker proxy rules not working
Replies
6
Views
5K
USY
U
S
Issue Installing Owncast via Docker - Ports not exposed
Replies
2
Views
2K
bo_max
B
WebHostingAce
Input Magento 2 | Plesk | Varnish Setup in a Docker
Replies
1
Views
5K
WebHostingAce
WebHostingAce
Back
Top