Reply To: FreePBX access denied to SQL error on one node

The problem most likely was created by changing the FreePBX database username/password on one node and not the other. Changing the FreePBX database username/password does two things: 1. it updates the /etc/freepbx.conf file, and 2. it updates the ‘users’ table in the MySQL ‘mysql’ database.

So although you may be syncing the ‘freepbx’ database between nodes, you are not syncing the ‘mysql’ database between nodes. And you should not try to synchronize the MySQL ‘mysql’ database (which holds the schema as well as user info), unless you are a DBA and really understand what you are doing!

The solution to this problem is very simple:

• Copy the full MySQL database from the working node to the problem node; or,
• Reset the FreePBX user password on the problem node to match the working node; or,
• Don’t sync the freepbx.conf file and set the two nodes to have different passwords

To avoid this in the future either:

• set the FreePBX MySQL user password identically on both systems; or
• leave the default password; or
• don’t synchronize the freepbx.conf file; or,
• sync the ‘mysql’ database (but you have to be sure you understand the implications before doing so) – we don’t recommend this

So the cause and solution to this problem reside completely within FreePBX (HAAst has not malfunctioned in any way).