How do I purge old artifacts (two remaining apps) from a previous Cloudron installation?

[Info-Tech.guru]

I have recently become a Cloudron user, and I am quite impressed with what it can do, but I have gotten myself into a bit of a bind. I am in the middle of migrating my services from my old LAMP server onto this decidedly more powerful platform. The problem which I am currently dealing with though, is that I had previously linked an earlier incarnation of this very server to my Cloudron account and installed a couple of apps (Rocket Chat, and Mastodon) into that administrative user-panel environment.

After messing around a bit with the free version of the Cloudron software, I decided to enroll into the subscription/paid-user plan. When doing so, I was having some problems getting things to run smoothly, so I (perhaps foolishly) unlinked/disconnected my server's registration from the Cloudron.io management environment. I was then able to get things up and running again with a fully functional version of the server-administration software installed onto what I thought was a new and fresh instance - however, it still has those two apps which I had installed earlier on it.

This would be just fine, if they were shown as available and detected by the my.website.tld Cloudron control panel, so that I could properly manage and access the behind-the-scenes infrastructure at play - but they seem to be running as fully functional (yet ghosted) processes which I cannot track down on my server. Now when I visit rocket-chat.some-website.tld or mastodon.different-website.tld - these apps are shown as running and available - but I cannot stop them from gobbling up my server resources or control them in any way. I am hoping that someone can explain how to stop these two Docker instances which I have accidentally left running and installed from a previous Cloudron operating environment, and remove them from the server... so that I can then have full control within the new administrative interface.

I have done some searching and analysis of the following directories through the SSH command line interface: /var/lib/docker/ and /home/yellowtent/appsdata/ but it is not very effective, since everything is Docker-style obfuscated by whatever virtualization magic is at play. So if I could go ahead and sum this all up into two succinct questions just one simple question, then it would look like such:

1. Is there a way to locate old orphaned apps from a previously installed Cloudron environment, so that they can be uninstalled and removed?
   2. On the occasion that I need to reimage my server from scratch, in order to zero things out to fresh-start, can I then backup, and reinstall my currently installed Cloudron apps onto the newly formatted machine?

I look forward to hearing back from someone who has perhaps dealt with something like this before, or from somebody who knows how to address this situation and fix whatever I have accidentally misconfigured.

I appreciate the time and attention you have devoted to this matter.

Gratefully,

Info-Tech.guru

EDIT: I just noticed how insanely simple it is to implement, and restore backups within the Cloudron user interface. This is really cool! I am hoping that I don't have to go to such extremes though.

[nebulon]

Have you restored the platform (box) backup onto the new server? In which case also the apps will be restored. If this was not the case, it is indeed very strange why old apps are still there. Can you double check if the DNS to the apps resolves to the new host?

[Info-Tech.guru]

Ahh yes! That makes perfect sense @nebulon ... and I feel rather silly for not taking that into consideration. It should have been the first place that I looked - because indeed the subdomains rocket-chat, and mastodon were pointing to the old server still. Therefore, there is nothing more to be assessed or figured out here, because you have helped me to solve the problem. I am taking the old server offline, and setting up the apps within the new host environment - as it seems this was much ado about nothing!