hosting control panel

Hello all,

I'm looking at the control panel to manage my customer's website and possibly also manage my FreeBSD server.

Looking around, I found the following:
  • Virtualmin with Webmin
  • froxlor
  • ispCPOmega
  • ZPanelcp
On another post I was made aware that Virtualmin/Webmin's main aim is focused on Linux environments and not so much FreeBSD and has a few issues on FreeBSD. So far looking at the online demo, I do like froxlor the best. But has any of you used any of this control panel?

ZPanel seem to have security issues. Is that right?

What are your recommendations? what about a Webmin and Zpanelcp or Ajenti with Zpanelcp combination?

Thank you all.
Fred
 
chatwizrd said:
Zpanel is junk. It does everything through php exec. I have never heard of froxlor it looks interesting.

Thank you for the reply. Have to got a suggestion as an alternative to Zpanel? Have you looked at their latest release from July?
 
Well, you already know my personal favourite.

There is one very important matter to keep in mind here: a control panel can never be a substitute for having a solid understanding on how the underlying parts actually work. One way or the other, you are going to need such a level of expertise.

It won't make things easier, only easier to manage. The real strength of a control panel comes as soon as you're hosting several individual websites and related services (such as e-mail, optional back-end database, specific e-mail filtering settings, etc.). Because if you need to move such a website from one server to the other then it can become quite tedious to do so; you need to copy the physical data itself, the configuration of the web server as well as the mail server, you'll need to make a dump of the database as well as making sure to copy the associated credentials and that's ignoring everything else.

That's where control panels can shine. Last months I've been very busy with a full migration from Linux CentOS to FreeBSD and if it wasn't for Webmin / Virtualmin it would have taken me a lot more time than it has now. Simply because I can treat a website as a single "product". And that product includes everything for that particular customer (e-mail settings, database, etc.).

But as said; you'd still need to understand why open relays are bad when dealing with a mail server, you'd still need to make sure that whatever permissions you're applying are actually safe, you might need to know how to utilize Apache's suexec routines (how and why).

Most importantly of them all, in my opinion of course, is that you should be very weary not to become too depending on such an admin panel. I've seen that happening just too many times, and it's a poor sight indeed; people knowing what options to click in a panel like Plesk or cPanel, but without having the slightest idea what it is they're actually doing.

It'll work, you will most certainly be able to get some work done. But you're horribly limiting yourself. Now your limits aren't so much the options which the software you intend to use (mail server, web server, etc.) can provide. Instead your limitations have now become that which the developers behind said admin panels actually understand about the underlying products.

And it's my experience that this level of understanding isn't always as great as it could be. In my opinion that's definitely something to keep in mind...
 
Thank you you very much @ShelLuser for your very wise advice. I needed that to keep me on track.

I will have to manage four websites all together. Although I now know how to create domain hosts for each domain on the web server I haven't got any experience in mail servers. I have never set one up before. Hence the use of a control panel.
 
Last edited by a moderator:
Back
Top