11-19-2020, 07:25 PM
I recently took a try on Cyberpanel. First I set it up on my backup server and tested it for about a week.
For the most part, everything works well for my needs.
I did have a few issues so far as everything working right out of the box:
Cyberpanel could use some improvement in default server configurations for rewrite rules, if they are going to have default configurations. I had to fix mine for permalinks. As several people have commented, there is some complexity in the setup of dns and mail - it's great that these options are in place but it would be better if it was easy to get them to work. Hopefully whoever among us figures it out first puts up a good tutorial.
One thing I didn't really like (I wouldn't call it a bug; maybe an unintended behavior) is that after a period of inactivity you are logged out. That's a sensible security precaution, and I appreciate it; however it would be nice if I could be notified or informed after I've been logged out, rather than fighting mystery error messages as I attempt to upload a file.
In comparison to webmin: I noticed the higher ram usage, but made some savings by converting my sites to shared hosting as opposed to each site in its own docker container. While cyberpanel itself uses more resources, I am running much more efficiently overall with the shared hosting setup. Unfortunately this means I haven't made any time to test the docker integrations
After a week of testing on the backup server I decided to reinstall my production server. I still have a few broken links around to tidy up, but overall I like it. The gui is much more intuitive than webmin or ISPConfig: I've used webmin quite a bit, and I've experienced the decline as modules became buggier and broken over the years. Given that RAM is much cheaper than it used to be I don't mind sparing a couple hundred MB to run a more modern panel with more active development and growing documentation. The good reviews also give me hopes of great community support in the future.
For the most part, everything works well for my needs.
I did have a few issues so far as everything working right out of the box:
Cyberpanel could use some improvement in default server configurations for rewrite rules, if they are going to have default configurations. I had to fix mine for permalinks. As several people have commented, there is some complexity in the setup of dns and mail - it's great that these options are in place but it would be better if it was easy to get them to work. Hopefully whoever among us figures it out first puts up a good tutorial.
One thing I didn't really like (I wouldn't call it a bug; maybe an unintended behavior) is that after a period of inactivity you are logged out. That's a sensible security precaution, and I appreciate it; however it would be nice if I could be notified or informed after I've been logged out, rather than fighting mystery error messages as I attempt to upload a file.
In comparison to webmin: I noticed the higher ram usage, but made some savings by converting my sites to shared hosting as opposed to each site in its own docker container. While cyberpanel itself uses more resources, I am running much more efficiently overall with the shared hosting setup. Unfortunately this means I haven't made any time to test the docker integrations
After a week of testing on the backup server I decided to reinstall my production server. I still have a few broken links around to tidy up, but overall I like it. The gui is much more intuitive than webmin or ISPConfig: I've used webmin quite a bit, and I've experienced the decline as modules became buggier and broken over the years. Given that RAM is much cheaper than it used to be I don't mind sparing a couple hundred MB to run a more modern panel with more active development and growing documentation. The good reviews also give me hopes of great community support in the future.