Sometimes it's necessary to run some tests or debug specific issues in Blesta. Here are some common things you may need to do, or may be instructed to do by support, when something goes wrong.
Check PHP CURL, outbound TLS Version
Blesta integrates with many 3rd party services and it may be necessary to ensure that your server is capable of making a TLS connection with certain minimum requirement. Here's sample code you can place on your server and access in your browser. It will return the most modern version of TLS that your server is capable of negotiating. If it say TLS 1.1 and the service you are connecting to requires TLS 1.2, then it will explain why a connection is not possible.
Copy the code into a text file named curl-check.php and upload to your Blesta installation directory. Access in your browser and it will display the most modern TLS version supported. e.g. TLS version: TLS 1.2
Enabling Error Reporting & Debugging
To enable error reporting, edit /config/blesta.php and change Configure::errorReporting(0); to Configure::errorReporting(-1); You may also wish to enable System Debug. To do so, change Configure::set("System.debug", false); to Configure::set("System.debug", true);
Do not leave System.debug enabled
Checking Error Logs
Starting with Blesta 4.1.0, errors are logged to disk by default. To see if your system is logging, check the path under Settings > System > General > Basic Setup for "Log Directory". This should be the full system path to your logs directory, and it should indicate to the right of the field that it is writable.
Then, navigate to this directory on your server. You should see some log files, including:
Support staff are mostly interested in the error and emergency logs, but depending on the issue the other logs may be important. The error log contains PHP exceptions, and the emergency log contains Blesta errors. Find the files with the most recent date, and open them to find the errors. If the error is reproducible and you have SSH access to the server, you can "tail" the log files while reproducing the error to more easily find what you need. For example: tail -f general-*.log will tail all of the log files at once.
Checking the integrity of your System Key and Encrypted Data
The /config/blesta.php file contains a very important Blesta.system_key. This key is generated during installation and must match the original database. If the key is changed, all encrypted data will be irrecoverable and your installation will be permanently broken.
To check your system, follow these steps:
- Download the SystemKeyTest.zip file below.
- Unzip the file.
- Upload admin_keytest.php to ~/app/controllers/
- Visit /admin/keytest in your browser.
- Observe the output.
Disable Human Verification (CAPTCHA)
If you enable a Human Verification / CAPTCHA's for staff logins, and are then unable to login, you may disable Human Verification for the company using the following query. Please note that this will disable Human Verification / CAPTCHAs for the entire company. If you are using multi-company and the issue affects a company ID other than 1, update the query to replace the company ID with the desired company ID.
After running this query, login to Blesta and visit Settings > Company > General > Human Verification. Adjust your settings and re-enable Human Verification / CAPTCHA's for the desired forms.
Regain Staff Access to Settings
If you edit your own staff group and lock yourself out of the staff settings area, you can regain access by adding ACL permissions to edit your staff group back manually by running the following query:
Then, access the edit group page at the URL ~/admin/settings/system/staff/editgroup/1/ and you can grant permissions to any others that may have been erroneously removed.
Forcefully disable auto-debit for clients that do not have active services
Clients who have no active services, yet have open invoices with auto-debit enabled will be charged. This query will create a client setting for autodebit and set it to false for any clients that do not have any active services. Backup your database first!
How do I prevent a domain or service from being renewed via the module when an invoice is paid?
Sometimes, particularly with domains the domain could be renewed outside of Blesta. We recommend that you let Blesta handle these renewals automatically. If for some reason you need to prevent that from happening you will need to remove the relevant record from the service_invoices table where invoice_id=your invoice id, and service_id=your service id.
Fetch the Collation of Tables
This query can be useful for fetching the collation of your database tables. Replace DATABASE-NAME with your database name. The query should return each collation found and the tables that use it.
The recommended requirements for Blesta 5.0+ includes MySQL 5.7.7+ or MariaDB 10.2.2+. If you are running MariaDB < 10.2.2, you can upgrade to 10.2.x using this script.
First, backup all databases.
On CentOS 7.x with no root password set. use "mysql_upgrade -u root -pPASSWORD" if there is a password.
Manually Resetting Staff Password
There are a couple ways to reset your staff password, from simplest to most complex. Follow these steps in order until your password has been successfully reset:
- To reset the staff password visit /admin/login and click the "Reset My Password" link. Enter your username, and click the "Reset Password" button. You should get an email with a password reset link within a few minutes.
- If you don't get an email, ensure that your username is correct. In phpMyAdmin or other MySQL database utility, look in the users table. Your username should appear in the "username" column, typically where id equals 1, as the primary staff account is the first user to be created. Try using the password reset option above with the correct username.
- If that still doesn't work, you will need to temporarily enable legacy passwords.
- Please see Encryption in the user manual, specifically Blesta.auth_legacy_passwords and set it to true.
- Then, in the users table for your username, update the password field to: 5f4dcc3b5aa765d61d8327deb882cf99
- Then, try logging in with your username and the password password. Reset your password.
- Then, change Blesta.auth_legacy_passwords back to false.
Renaming a Module
In some rare cases it may be necessary to rename a 3rd party module. For example, if you are using a third party module named TestModule, and we release an official module called TestModule, you may wish to rename third party module so that it is not overwritten by the official module.
Before proceeding, make sure you really need to rename the module and be sure to back up your files + database. If you encounter any issues, roll back your changes.
The first step is to rename the module directory and primary module file
- /components/modules/testmodule becomes /components/modules/testmoduleold
- Rename /components/modules/testmodule/testmodule.php to /components/modules/testmodule/testmoduleold.php
The second step is to update the class name in testmoduleold.php from:
The third step is to update the modules database table.
The fourth step is to change view context statements from: