Is there a queable way to delete them all? A script that will purge them in the background?
cd /home/virtual
DeleteDomain --force *.test
Although, I would encourage you address Cannot delete account - #2 by Troy as a precheck is done to ensure a domain may be deleted without obliterating DNS records on a server move; this is the root cause of failure.
A domain may exist on multiple servers. If cp-proxy is configured, a check is performed prior to deletion to ensure removing a defunct account will not remove DNS zones elsewhere.
This is a different server, so unrelated.
There have been no server moves, this was observed when running a cp-collect and observing the results.
It would be nice if this .test issue is going to come back once in a while if there was an automated way to remove them instead of a long running DeleteDomain process.
Ok, maybe they are related, all of a sudden deleting accounts results in a 503.
What’s changed recently? Which logs should I check if the panel log just confirms it can’t delete the account?
Ok, found on the API server in the httpd access log:
[20/Oct/2025:23:23:16.3486 -0400] “POST /lookup HTTP/1.1” 503 15861 “-” “HTTP_Request2/2.3.0 (HTTP_Request2) PHP/8.1.21”
I’m selling an old house after moving. My time is limited as of July. Changes are hamstrung until all of this is rectified.
I’d look at what the most recent release is; this is a requisite to post.
cpcmd misc:cp-version
This will allow me to vet your software revisions to better assist you.
All servers are 3.2.48
That’s not what I asked for. I asked for the output of cpcmd misc:cp-version which includes drift.
revision: 50eca27bdf98f47e978cc66122911e4c0193a82c
timestamp: 1760625243
ver_maj: 3
ver_min: 2
ver_patch: 48
ver_pre: ‘’
dirty: false
debug: false
Same for the others
Not sure what broke it, php pools was a no sentient life error page, reconfig on the site brought that back and I could restart the pool. /shrug