• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Can't delete a subscription: Operation is taking too long

DocF

New Pleskian
When trying to delete a subscription, the following message appears:
This operation is taking too long. Check the results in a few minutes.


/var/log/sw-cp-server/error_log
1975#0: *5539 upstream timed out (110: Connection timed out) while reading response header from upstream, client: xxx.yyy.zzz.aaa, server: , request: "POST /admin/subscription/delete/?redirect=/subscription/list/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock", host: "domain.com:8443", referrer: "https://domain.com:8443/admin/subscription/list?context=subscriptions"

Can anybody help?
 
Hi DocF,
I've got the same error, but when I try to change anything in DNS parameters, subscription parameter, etc.

I've got this in /var/log/sw-cp-server/error_log :

[error] 30571#0: *79 upstream timed out (110: Connection timed out) while reading response header from upstream, client: XXX.XXX.XXX.XXX, server: , request: "POST /admin/subscription/delete/?redirect=/subscription/list/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock", host: "mydomain.tld:8443", referrer: "https:/mydomain.tld:8443/admin/subscription/list?context=subscriptions"

Do you have some clue to fix it ?
I've tried with no luck 2 of these solutions: http://kb.odin.com/fr/124377

I am on CentOS 6.7 Plesk 12.0.18

Thanks in adance for any help !

Best Regards
 
Hi,

My mistake....
I reboot server then everything was better:

- Reboot
- httpdmng --reconfigure domain

Was enough to repair everything !
Hope I won't have this kind of problem again.

Thanks to the community.
 
Back
Top