Hi,
I have DirectAdmin server with 2 network interfaces, WAN and LAN.
My DirectAdmin server is configured to connect to a remote MySQL server on the LAN.
My setup is:
DirectAdmin server:
WAN: 37.xx.xx.xx
LAN: 192.168.1.4
MySQL Server: 192.168.1.5
When I restore a user I encounter with a few strange behaviors:
I have DirectAdmin server with 2 network interfaces, WAN and LAN.
My DirectAdmin server is configured to connect to a remote MySQL server on the LAN.
My setup is:
DirectAdmin server:
WAN: 37.xx.xx.xx
LAN: 192.168.1.4
MySQL Server: 192.168.1.5
When I restore a user I encounter with a few strange behaviors:
- DirectAdmin creates a database user(s) with the wrong IP address (WAN IP, instead of LAN IP), so the machine won't be able to connect to those users later. I was almost able to solve this problem with a custom scripts: database_create_post.sh and database_user_create_post.sh. They grant the correct IP address to the created users, but it doesn't work as expected (see number 3).
- DirectAdmin try to restore user database with [email protected] instead of [email protected] (It doesn't really matter but if it was da_admin my problems was solved).
- When restoring a user with databases, database_create_post.sh script get an empty user and passwd parameters. BUT when creating a database to an existing user it works fine.