mirror of
https://github.com/retspen/webvirtcloud.git
synced 2026-04-25 23:45:56 +03:00
[GH-ISSUE #495] HOW TO UNINSTALL WEBVIRTCLOUD? #299
Labels
No labels
bug
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/webvirtcloud#299
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Wotan6891 on GitHub (Apr 19, 2022).
Original GitHub issue: https://github.com/retspen/webvirtcloud/issues/495
Hello,
for reasons of lack of capacity of my pc, I have to remove webvirtcloud.
I have an Ubuntu machine.
how to uninstall it?
Thank you
@catborise commented on GitHub (Apr 21, 2022):
webvirtcloud is a small application. it does not much effect on storage. it about 500mb to 700mb with all libraries.
may be you want to delete a virtual machine?
@Wotan6891 commented on GitHub (Apr 27, 2022):
hello,
thanks for your answer.
the problem was the port it used, and that port is used by another application.
I had to delete the files. but I never found a way to remove it by terminal.
@lmsdscav commented on GitHub (Jun 26, 2022):
delete its supervior service and nginx web config. Then the port'll be free. :)
@lmsdscav commented on GitHub (Jun 26, 2022):
/etc/supervisor/ ()
and /etc/nginx/conf.d/ ()
@Nephiaust commented on GitHub (Jun 12, 2023):
If you wish to purge it from your system, BE WARNED THIS IS A ONE WAY STREET, you can run
sudo apt purge supervisor nginx && sudo apt autoremove. This will remove anything that was installed relating to the supervisor & nginx packages. But as noted, it is a one way street... So if you are using Ngnix for something else it will remove that.If you are having port issues, maybe look at either changing the port being used for the new program OR change the port nginx listens to.
Would also suggest maybe closing issue, as its now over 1 year old and not an actual bug for the system