phpmyadmin not loading for reseller for remote database but does for root
We've setup WHM to use a remote host by creating a MySQL profile. The profile is active and can validate. When logged into WHM using root, we can launch phpmyadmin ok and see the database. However when we login to WHM with the reseller account (which has full priviledges), it can still validate the profile ok but when you click on phpmyadmin you get the error " mysqli_sql_exception: MySQL server has gone away". We've tried launching from within WHM or cpanel but both give the same error.
-
Hey there! Can you provide me with the specific details on how you configured the remote database? Are there any additional errors inside /var/log/mysqld.log (that is the default location of the MySQL error log file, so you may need to check /etc/my.cnf if that has been customized).
0 -
So the remote database is on Azure & working ok. We can connect to the database ok and when logged into WHM as root you can launch phpmyadmin and see the database ok. Yet logged into WHM as the reseller, on the same machine (so not an IP access issue) you get the error when launching phpmyadmin. So we know mysql is ok & running & phpmyadmin works ok, seems related to the user logged into WHM
0 -
It's almost certainly a user access issue, but knowing the details I mentioned above would get us started.
0 -
no it's not generating any errors in the log file, to be sure I emptied the file & restarted mysql and when trying to access phpmyadmin no new entries.
I'm not sure what additional information you need, we configured the remote database by adding a MySQL Profile, adding the remote host address, port & user/pass, then clicked Validate and that is green tick, then activated the profile. When you click Validate you get the green message "The profile "BBDS on azure" is valid. You get this message when you login as root & as the reseller.
0 -
I would have expected it to at least log *something* related to the failed connection or failed user access, or anything interesting at all. Since it's not doing that, you'll likely need to create a ticket so this can be investigated directly on the server.
0
Please sign in to leave a comment.
Comments
5 comments