Version 3.24.0 🔗

Features: 🔗

• Add option to disable the configurator in the order settings so only packages can be ordered
• Configurable charges: Documentation
• IPAM Enricher for the Event System: Documentation
• High Availability, Note & Hostname Update, and IP-Assigment for the modify server Action: Documentation

Version 3.23.0 🔗

Features: 🔗

• Add User 2FA to settings & login
• Add server rescaling & package switching
• Add paysafecard payment provider
• Add coinbase payment provider

A note on rescaling: the current implementation enables user to switch every component of their server around - if it’s a server that did not originate from a package. If the server was originally created via a package-order, only other packages can be selected . Note: server disks cannot be shrunk, this is a Proxmox limitation. When switching packages we allow the user to take any package where the disk is greater or equal to the current disk size. He can decide to not scale the disk itself, meaning he could switch back to a smaller package later. The price will remain the package price.

A Note after updating: please test if you current payment integration still works. I’ve changed a lot of code in the background to make it easier to integrate new providers in the future and this is quite a fragile step in the update process. If you face issues, try to execute ./composer update in the installation folder of the ProxmoxCP (default: /var/www/html). For any additional help, please reach out on the discord.

Version 3.22.0 🔗

Tags help you organize resources. Currently it’s only possible to be set on servers and users, but they will be expanded in the future.

Features: 🔗

• Add Test-Mode to the Webhook & E-Mail action for the event system
• Add Load-Tags enricher to event system

Version 3.21.0 🔗

Introducing the Event System:

The Event System is there to help you build integrations and actions based on events that are not integrated into the panel itself. Read more about it: here. Please be aware that this is a beta feature, every feedback is welcome.

Fixes: 🔗

• Admin password reset was not working
• IPAM Logic was working in an unexpected way

Version 3.20.0 🔗

We need to talk about billing, billing-periods and how server cancellation is handled. Prior to this update, if you wanted to get rid of a server, there was only one option: delete it. This would delete the server immediatly. While this can make sense for internal plattforms, it’s most likely not the expierence a customer whishes for, since he paid for the server for a full billing cycle, and suddenly it’s gone.

So - this is now changing. Starting with the version, customers can no longer directly delete the server. Now he needs to first cancel it, which will mark the server as cancelled, leaving the customer with a usable server until the billing period ends. Additionally the server can always be un-cancelled so if the customer realizes he still needs it - no problem. If a server is cancelled, the option to delete it becomes available, so if you really wanted to you can immediately free the resources.

In addition to the above, servers will now also be suspended first. When the billing period ends and the user does not have sufficient funds on his account to pay for the server it would’ve been just deleted, leaving no chance to correct any mistakes. Now, the server will be shut down and enters a suspended state where all interaction is forbidden. The customer can un-suspend the server again by just paying for a new full period. The administor has the ability to configure the days that servers stay in this state. After these days pass, the server will finally be fully deleted.

Fixes: 🔗

• Missing icons in some places
• Added Support for PHP8.3

Version 3.19.0 🔗

Features: 🔗

• Add ISO Attachments for servers. Relevant Storage can be set in the Admin Settings.

Version 3.18.0 🔗

Features: 🔗

• Administrators can set the profile-picture provider in the general settings (Documentation)
• Invoice-PDFs will be automatically downloaded and can be opened by the customer
• Rewrite server status system, now including starting and stopping instead of just online and offline
• Rewrite of the admin-server overview, including the importer. Migration tool temporarily removed
• Rewrite of the dashboard server widget, now including server status
• Servers can now be manually changed to a different node and/or a different user

Version 3.17.0 🔗

Features: 🔗

• Added warning on the Dashboard when license in the CIS is misconfigured
• Reworked the update flow, this will take effect for the next update
• Reworked module installation flow, more error handling, more input-handling
• Reworked miscellaneous globally used systems for new Module
• Reworked auto-installation script, making it more error-prone

With this version, the first release of the Domain Module also goes live. If you want to manage your PowerDNS Domains from the same interface (or want to enable your customers to do so) please checkout the Domain Module: https://bennetgallein.de/shop/ProxmoxCP_Domain_Module-40

Version 3.16.0 🔗

The scope of this update is mainly to make it easier for admins to debug errors in the setup and to make it easier to identify errors during the order process.

Features: 🔗

• Reworked the Proxmox Connection Test in the Admin Settings. It’s more visual appealing, making it easier to identify errors or warnings
• Reworked how errors are shown to the user during the order process. When an error occurs and you are logged in as either an admin or support you will get the same error message as would be shown in the event log
• The Dashboard has been rewritten in Vue, for future expandability

Fixes: 🔗

• Fixed some issues in some APIs that were used internally

Version 3.15.0 🔗

The topic of this update is refactoring. There have been a lot of changes in the background, mainly to the permission system, allowing some new features (resource sharing), simplifying development and maintenance for the future. Also, over the last few updates the frontend has been rebuild with Vue.js, giving me more flexibility in development for future modules, add more APIs for the coming public-API and overall build a better experience.

As always, there are some new features I want to present - and of course some smaller fixes.

Features: 🔗

• Resource Sharing. Server-Owners can now grant access to other users, either as read-only, editor or even full administrator
• Login as user. Administrators can login as a user, giving the exact perspective and permission-scope the user has
• The VNC-Terminal is now based on the advanced version, giving access to things like the clipboard, shortcuts and more
• New connection method with Proxmox: Unlocking API-Key support. It is faster, more secure and offers more flexibility. See Connect Proxmox to read more
• Languages can be disabled/enabled. Administrators can decide what languages are available to users. With the growing amount of languages (thank you very much contributors) I felt like this is needed
• The language-system will now fallback to the english translation when the corresponding text is not found in the target language
• Templates can now be deleted. The Panel will also detect if a template is orphaned (meaning the template was removed in Proxmox)

Fixes: 🔗

• Editing charges was broken
• Moving a VM-Disk after creation from a shared-storage to a non-shared storage was partially not working and should work as expected now
• Units for memory-charts was wrong
• Login and registration now accept all characters in a password
• On some pages the title (the text shown in the Tab) was not correctly set

Most Modules have also been updated to integrate the new permission system and integrate further into the core-panel (with this update into the admin user-overview). The newest versions are the following:

• BackupModule: v1.3.0
• BlockStorageModule: v1.4.0
• LXCModule: v2.6.0
• NetworkModule: v1.4.0

Version 3.14.0 🔗

This update adds one big change: modules now can display widgets. First they will only be available on the server page, but have potential to be integrated everywhere:

this means that now actions like moving a block-storage away from the server, detaching a network or creating/restoring a backup can be done from the server page, without jumping between pages.

Other notables changes:

Features: 🔗

• The invoice system now sends E-Mails (when activated). If the invoicing software supports sending E-Mails via API this is used, otherwise the CP will generate a PDF from the invoicing software and send it to the customer itself
• Notes can now be written for servers. These are saved within the Proxmox notes field, so they are always in sync. You can for example enter informations for the customer here by adding the note in the template
• There also is a new .htaccess file, which is more secure, more error-prone for manual editing and does not generate warnings
• There are also some preparations being done for an public-API which could be used by your customers or yourself to write a custom frontend or integrate the panel into you website by allowing price-calculation. But more on that in a later release
• Starting with this update, any action that will delete something requires manual confirmation by typing in a confirmation sentence

Fixes: 🔗

• Database schema was broken for new installs due to a field that should have been removed
• Invoices where the amount is 0 will no longer be imported and just marked as imported

BackupModule v1.2.0 🔗

• Added frontend module for server page

BlockstorageModule v.1.3.0 🔗

• Frontend rewrite
• Added frontend module for server page

NetworkModule v.1.3.0 🔗

• Frontend rewrite
• Added frontend module for server page

Version 3.13.0 🔗

Features: 🔗

• Intergration for accounting systems (Read the docs)
• Added descriptions to invoices, needed for the integration of accounting systems
• Added the VMID from Proxmox into the admin server-overview
• Added new field in the settings to set custom CSS that will be used globally
• Added logging for the cronjob execution, making it easier to track errors

Fixes: 🔗

• Unified a lot of backend code
• Unified PSP Integration
• Modified autoloading for easier updating
• When a server gets created, the Panel now copies all settings from the existing network adapter and only overwrites the ones needed. So pre-configured things like the model or speed limit will also get cloned
• The network-usage chart on the server ovierview page was calculating the wrong units

LXCModule v2.5.0 🔗

• Readded the Terminal (see docs)
• Added integration for new invoicing system
• Added VMID to admin container overview

BlockStorageModule v1.2.0 🔗

• Added integration for new invoicing system

NetworkModule v1.2.0 🔗

• Added integration for new invoicing system

BackupModule v1.1.0 🔗

• Added integration for new invoicing system

Version 3.12.0 🔗

This version updates a lot in the background and older parts of the codebase to bringt it up to my modern standards and to introduce the new systems that have been implemented.

Backup Module 🔗

The biggest change in this update is the addition of the Backup Module which is revealed for the first time.More information on the shop page (https://bennetgallein.de/shop/ProxmoxCP_Backup_Module) or in the documentation (https://docs-next.bennetg.de/products/proxmox-cp/modules/backup-module)

Redesigning the balance page 🔗

The balance page before was a pain and I agree with that. With this new update we made it easier for your customers to monitor when their balance will run out + we refined the flow of add balance to your account.

Background changes 🔗

I’ve introduced a new Event-System which will allow modules to hook onto certain events (like server deletion) to execute logic without interfering with the main process. Also the cron-system is now full asynchronous per Module, meaning that a Backup-Job wont block the sending of payment reminders for example. This is a scaling issue I’ve seen in production at customers so I’m hoping this is the way to mitigate that.

Dependency Updates 🔗

In order to take advantage of the cool new internal features I needed to update the dependencies slighlty. They should be non-breaking for PHP8.1 installations, older version of PHP might want to update anyways due to the ended support of PHP8.0.

Version 3.11.0 🔗

This version adds a few quality-of-life improvements.

Captchas: 🔗

Administrators can now configure captchas in order to secure the register-page. This has be commonly requested to combat spam. See more information in the dedicated setup-guide here.

E-Mail confirmation: 🔗

Confirming your account upon registration is another feature that will help you to add a layer of security to your Panel. This of course requires you to have a working E-Mail Server, which is also connected to the Panel. For more information read the dedicated entry here

Adress requirements: 🔗

In order (and preparation) for the coming integration of external invoicing-systems it is required to collect customer information to ensure that the invoices are lawfully. This is only needed when the user want’s to add balance to his account (via a payment provider). He will still be able to use vouchers and admin-given money to order servers.

Node Limit Rework: 🔗

A massive pain-point for both you and me was always the configuration of the limit of a node. Since you need to set this up in order to have servers created successfully, it is quite important to me to make this process as painless as possible. Now, when you visit the “Host” page, you will be able to customize the limit of a node by using a slider and will directly see what impact it would have on the provisioned usage of the node.

Version 3.10.0 🔗

In this version, we introduce the abillity to reorder packages and templates so you can control the order in which they are being displayed to the customer. You can also edit packages now, including setting a fixed template for a package, which cannot be changed after the server is ordered.

Reorder packages: 🔗

Reorder templates: 🔗

Edit packages: 🔗