Hi. tldr default allowed hosts for new db users is hard coded as "localhost" which isn't ideal if you used a remote database server during install. Here's how you can change that. I've just done a new install of ISPConfig, using a remote DB server for IPConfig db and all client db's. To do this I simply entered the remote servers details when prompted for database credentials at the start of the ISPConfig install. I had some minor issues, I had to recreate the ispconfig database user as it had an incorrect value in the "Host" field of the mysql.user table (although I think this is probably more down to my setup and DNS configurations) However, the biggest issue I've found that wasn't a feature of my own setup is that the default host value for new db users is hard coded in as "localhost". When a new database user is created on the remote db server, it can't be used by ISPConfig because the ISPConfig server isn't "localhost" to the dbserver. This can be changed in each instance by specifying ISPConfig server details in the "remote access" settings when creating the database but this isn't ideal for new clients. To change this, I first defined $clientdb_default_user_host to be the default value in the "Hosts" field for new mysql users in /usr/local/ispconfig/server/lib/mysql_clientdb.conf Next I had to make some small changes in /usr/local/ispconfig/server/plugins-enabled/mysql_clientdb_plugin.inc.php: Find lines 211 and Lines 261: PHP: $host_list .= 'localhost'; And also line 270 and 466: PHP: $old_host_list .= 'localhost'; change 'localhost' to $clientdb_default_user_host Now when new db users are created, their default host value will be the value of $mysqldb_default_user_host instead of 'localhost' Does anyone know of any reason why I should NOT do it this way (e.g. does this conflict with any other code)? It seems the easiest and most intuitive way of creating a setup where all databases (including ISPC master) are on a remote db server. It might be worth considering adding a check during the install, where if the database server entered during install isn't localhost (or 127.0.0.1 etc) then prompt the user for a default user host value, or add a setting somewhere in the interface for it. Alternatively, if the root credentials provided allow a login, simply login with root, do "SELECT USER()" and parse the correct hostname from that. Although this maybe more trouble than it's worth for the amount of people it will effect, and also will vary across DB types.