Deleted apps are still billed, suspected to have "ghost resources"

Viewed 80
feedback

Dear ClawCloud technical support,

Hello! My account is experiencing a problem with the console as follows:

On the billing page (Billing Center → usage), it shows that there are 5 applications that are being billed, 4 of which are WordPress applications (the names are wordpress-pvbdhsna, wordpress-tdprcjqa, wordpress-wtsroeyp, wordpress-zpadwent), and the other 1 is the "code server Hukgdeqy" that I need.

In fact, I have already deleted these 4 WordPress applications in the application interface, but I have already searched them in the application list, app store, database, compute instance, storage volume, EIP, etc., and there is no trace of related resources at all.

Despite this, these 4 apps continue to incur charges in the bill (see attached screenshots), and there are suspected cases of "orphan resources" or "billing residues".

I need to keep only the "code server Hukgdeqy", please help me verify and clean up these 4 WordPress-related resources or cancel their billing.

Please ask a technician to help you with this and confirm that you will not continue to incur charges for these 4 deleted apps in the future.

Thank you!

Account Information:

Account name: revolution-7

Account ID: 5wEeHZoSy9

Area: SQY

Relevant time period: August 2025

1 Answers

You can delete these resources manually by using Terminal.

  1. Open your UserCenter->Usage to find out whitch apps takes cost and why( eg: wordpress-pvbdhsna keeps using some storage)
  2. Open Terminal from your dashboard.(In which region & namespace costed)
  3. Find out these ghost resources
// List resource types you can operate in this namespace
$ kubectl api-resources | grep true
....

// For example wordpress-pvbdhsna keeps using some storage, So we should find resources about them.(storage/volume)
$ kubectl api-resources | grep true | grep storage
Warning: Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
objectstoragebuckets                                                   objectstorage.sealos.io/v1               true         ObjectStorageBucket
objectstorageusers                                                     objectstorage.sealos.io/v1               true         ObjectStorageUser
volumesnapshots                    vs                                  snapshot.storage.k8s.io/v1               true         VolumeSnapshot
csistoragecapacities                                                   storage.k8s.io/v1                        true         CSIStorageCapacity

$ kubectl api-resources | grep true | grep volume
Warning: Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
persistentvolumeclaims             pvc                                 v1                                       true         PersistentVolumeClaim
lvmvolumes                         lvmvol                              local.openebs.io/v1alpha1                true         LVMVolume
volumesnapshots                    vs                                  snapshot.storage.k8s.io/v1               true         VolumeSnapshot

// Then list the resources in each resource type
// kubectl get <resource type>
$ kubectl get objectstoragebuckets  
Warning: Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
No resources found in ns-xxxxxxx namespace.

// For example we found out that wordpress-pvbdhsna in 'persistentvolumeclaims'
$ kubectl get persistentvolumeclaims
Warning: Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
NAME                          STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS     AGE
vn-data-wordpress-pvbdhsna-0   Bound    pvc-xxxxx-xx-xx-xx-xxxxxxx   1Gi        RWO            openebs-vg-lvm   21h
  1. Delete it (Be careful!!!!!)
// kubectl delete <resource type> <resource name>
kubectl delete objectstoragebuckets vn-data-wordpress-pvbdhsna-0

Claim Reward + [[email protected]]

1

I have encountered a similar problem with my project, which is the project in the App launchpad. How can I find the 'ghost project' and how can I delete it?

UncleLong•
Related Questions
Incorrect Pod Count Displayed in Workspace Dashboard
1 answers
i can't save and inactive my workflow but other workflows is normal
How can I get a refund if I haven't used it yet? ClawCloud Run's access speed is so slow that it's basically unusable. It's very frustrating to use.
My Memos application data has been completely lost.
when install n8n community nodes, the app launchpad seems crash and cannot restart