Need help for ubuntu free control panel like cpanel/plesk

Better to ssh into a machine.

Most of the free panels suffer from various problems. For example, WebMin will sometimes just start spinning one CPU at 100%, draining machine performance.

Also with Panels security is always an issue, especially with abandoned Panel projects.

Also, even worse, anything you do in a Panel can never be reproduced. If you run commands under ssh, you can keep a copy of important commands to duplicate tasks which must be repeated in the future.

https://blog.ssdnodes.com/blog/cpanel-alternatives-vps/ provides a list of common Open Source Panels.

Try Ajenti https://blog.ssdnodes.com/blog/install-ajenti/ or Froxlor - https://froxlor.org/ both will work in ubuntu

The search - linux cpanel alternatives - provides a good starting point.

https://blog.ssdnodes.com/blog/cpanel-alternatives-vps - provides one of these alternative lists.

Aside:  Why Linux/UNIX Panel Systems are rarely used.

There are many... Linux CPanel-esque types of systems...

They're rarely used, because Panel systems have many inherent flaws.

1) They obscure important details, so any minor error underneath the GUI, which isn't caught or is handled incorrectly, cause many silent failures.

2) Along the lines of #1, there's no way to convert all the error/warning/diagnostic messages from 1000s of packages into some sort of cohesive messaging system.

Using ssh provides clearest, most actionable diagnostic/message spew.

3) Most Panel systems are poorly maintained, so just as CPanel code is continually hackable, most Panel systems are also security risks.

4) Securing Panel systems is difficult.

https://www.experts-exchange.com/questions/29204301/how-can-i-auto-redirect-webmail-in-CPANEL-to-port-2096.html provides a common approach which works well.

5) Panels provide no audit trail.

There is no breadcrumb trail in Panels.

Execute a set of commands in shell + a simple history command shows what has occurred, so mistakes are easy to find + hopefully reverse.

With a Panel system, if someone destroys the system, there's no clear audit path to determine a recovery approach.

With a Panel system, executing a complex set of actions which produces a working system, can never be duplicated or is complex to duplicate, even with notes or videos, you're hoping someone can humanly manufacture the exact same set of commands.

Which is highly unlikely.

6) Panels tend to destroy manual config tunings.

Most Panels use some sort of intermediate/common config file system to describe data which is then used to generate actual /etc (and other) config files.

If you make the mistake of hand editing a real config file, next time the intermediate config files are compiled, any changes you made are instantly lost, with no audit trail.

This is the source of many lost hours mucking about with config files where Panels are used.

The symptom is... everything works... then some random Panel command recompiles data to overwrite an /etc file, then something breaks, with no clear reason.

7) Panel Config Intermediate Config Formats are limiting.

The other problem with Intermediate Config Formats is they limit what you can actually change, meaning you can only usually effect a very small subset of config options from a Panel system.