ProxCP version 1.1 is now available for download! Just a few weeks past our first public release and we already have some sweet new features for you.
What’s new? Version 1.1 focuses on cleaning up the Admin dashboard and adding one of the most requested features for end-users. To that end, the Admin dashboard has a new layout for better organization. It also includes an automatic version checker now so you can immediately know when a new ProxCP version is available. Lastly, your end-users can now upload custom ISO images for use with their KVM or Public Cloud services. ISO files can be large…but no problem! ProxCP offers resumable file uploads just in case the process is interrupted. Of course there were quite a few bug fixes as well; especially pertaining to KVM creation and LVM storage.
We will continue expanding and improving upon the ProxCP product. The next major update will include at least a Blesta billing integration and migration scripts from other control panel software. On top of that, we will always be looking for additional feature suggestions and usability improvements.
Haven’t used ProxCP since the beta period earlier this year? Now is the perfect time to grab a copy and provide your VPS customers with the best control panel experience while simultaneously lowering operating costs.
Finally getting around to installing this and setting it up for the FreeMach boxes
Couple small suggestions:
In the Prerequisites and Minimum Requirements page, it says PHP 7.2+. Since the mcrypt php module is required, I’d suggest just saying to use PHP 7.2. The mcrypt module is depreciated and needs to be installed in a wonky way. Unfortunately this method doesn’t work for PHP > 7.3.0. Currently the latest version (7.3.3), there’s no way to install the module (even via the method linked above) without installing a different version of PHP and copying over the mcrypt file. Limiting to PHP 7.2 might help avoid some installation confusion.
On the ProxCP Installation page, it says to copy/move SSL certs to the daemon’s keys directory. If using Let’s Encrypt (as mentioned on the page), it’d probably be better to symlink to the certs rather than copy and move them. That way when renewal comes up every 3 months, they don’t need to be manually copied/moved every time. My forgetful self is bound to forget to do this.
On the Sample VirtualHost Settings page, the formatting is a little off. Also for the nginx config, I think the fastcgi_pass should be the fpm socket (i.e. unix:/var/run/php/php7.2-fpm.sock) instead of just php-fpm. Might work with that, but I’ve always used the sock connection.
Time to continue with installing and setting up the daemon now . So far I’m really impressed. Web panel looks nice!
Edit -
Also wanted to suggest using a systemd service for the daemon rather than using forever or screen. That way the daemon will relaunch if there’s a reboot of the node.
Here’s a quick one that I wrote up that seems to work fine.
We’re looking into switching to libsodium as a permanent solution to this.
Making a symlink using the same file names ProxCP expects would probably work - I haven’t tried that. The Let’s Encrypt certbot also lets you set the certificate paths for auto renewal in the cron job.
The docs will be updated shortly. Thanks for the systemd script!
