Leaderboard

we are proud to announce the release of our new module Hetzner Cloud Server, the module will allow you to resell hetzner cloud services with white label. Features Instant Activation of Cloud Server Automatic Suspension Automatic Unsuspension  Automatic Termination Unlimited Hetzner Projects Client Side Reboot/Boot/Shutdown Change Hostname Change Root Password Reinstall Show Available IP address Admin Side Reboot/Boot/Shutdown Change Hostname Change Root Password Reinstall Suspend/Unsuspend Cancel Create/Add Server Show Available IP address TODO List Add/Remove Volumes (config Options) Add/Remove IPV4/IPV6 (config Options) Add/Remove Cpanel/Softacoulus License (config Options) Allow/Disalow Client To Use Backup Add Snapshot Feature ANY Suggestion , FeedBack , Bugs , Please Post it inthis thread . this Module require a the Vip (GOLD) subscription . Order Link

Disabling open_basedir is the simplest solution, but you could alternatively include all paths that Blesta must access. Off the top of my head, the install directory, the uploads directory, the temp directory (/tmp/) to start. phpseclib also tries to access /dev/random, /dev/urandom for encryption purposes. It's easier to leave open_basedir disabled, but that's up to you. We also recommend running Blesta on its own server (A VPS will do) without any other applications, but many run in it a shared environment.

Thanks, i get now Blesta running: ISPConfig3: Web Domain -> Options -> PHP open_basedir: "None" -> Save I'm not sure if that opens any security problems ?

Your example mixes procedural and class syntax, so I'm not sure if you're running individual functions or if those are methods in a class. If you are writing procedural functions, simply: return success(); otherwise for one class method to call another non-statically: return $this->success();

Depending on the configuration, you will likely need to reissue your Blesta license to the new domain/location. If the credentials are all the same. There is a README file included with Blesta that describes how to upgrade. The upgrade documentation is also useful. Here's what I would recommend in your case: BACKUP YOUR BLESTA INSTALLATION AND DATABASE (especially /config/blesta.php) Put Blesta in maintenance mode Disable your Blesta cron job Download and upgrade to v4.0.0 as an intermediate step. This is mainly due to there being a lot of changes between v3.6.2 and v4.4.2 to make in one big leap. I would recommend upgrading via CLI mode (instead of /admin/upgrade in your browser) so that the upgrade process cannot time out in the web browser. Upload the contents of the "blesta" directory The upgrade documentation will be helpful to review. There are files you should delete as well, mentioned in the note at the top of that page. Some people have problems if those files remain after upgrade while most others do not. Run the upgrade script (via CLI is preferred) Check your Blesta installation to make sure it is working normally on v4.0.0 Backup your Blesta installation and database again, now for v4.0.0 (You can perform the server/cPanel migration here, or later at step #12-13) Upgrade your server to use php 7.2 (php 7.2+ is only supported on v4.4.0+ of Blesta) Ensure php 7.2 is installed for both CLI and web Download and upgrade to the latest version (currently v4.4.2) - via CLI mode is recommended over /admin/upgrade in your browser Since you are on php 7.2, you will need to overwrite a few files from the "blesta" directory with all the files in the "hotfix-php71" directory. You will receive ionCube errors if you do not do this Upload the contents of the "blesta" directory, which now contains the overwritten files from the "hotfix-php71" directory Run the upgrade script (via CLI is preferred) Check your Blesta installation to make sure it is working normally on v4.4.2+ Update configuration settings, like cron jobs and email templates, if necessary, since many changes were made since v3.6.2 Backup your Blesta installation and database again, now, v4.4.2+ Perform your server/cPanel migration as necessary Be aware that changes to your Blesta location (e.g. by domain or subdomain) may necessitate that you update any third-party configuration to point to the new location. e.g. PayPal IPN URL Log in to your account with us, or your reseller, and reissue the license Click to "Manage" the service representing your Blesta license, check the "Reissue License" checkbox, and submit Visit your Blesta installation at your domain and log in. This will complete the license reissue at your new domain Re-enable the Blesta cron job and observe that it runs tasks as shown on the Settings > Automation page You may need to reconfigure the cron job to run at the new location if it has changed Disable maintenance mode

cPanel (and essentially all other systems) will not send notifications to services (like Blesta) regarding a password update made through their system. If the cPanel password needs to be changed, then the user should: Change it from within Blesta, or Update it in Blesta after having changed it in cPanel

There are two separate calls you need to make: Create a ticket (as @Jono mentioned above) Create a reply for the ticket (as you did in your OP). FYI the first question from a customer that opens the ticket represents the first reply

You haven't applied the hot-fix it tells you there: was encoded by the ionCube Encoder for PHP 5.4 and cannot run under PHP 7.1 or later. So you need the hotfix71. Copy the files from /hotfix71/blesta/ to the root of blesta.

Our Hetzner Module in Chinese look very very nice ? in

Screenshot