I'm having trouble connecting to a newly installed WebDataAdmin. I have opened a ticket LOS-40094-586 but hoped I might find a solution here too. I have tried creating the specific domain webdataadmin via the main reseller account - but I get a
#1045 - Access denied for user 'root'@'localhost' (using password: NO)
error.
I have tried also creating webdataadmin from the parent of the sub domain, and from the subdomain itself and all with the same result.
Is there a problem since the move with webdataadmin creation/installation? or is there a 'trick' to get it to work properly.
All other already established webdataadmin websites are working perfectly.
no - phpmyadmin (or webdataadmin as HC likes to call it) - is installed by eukhost - so I don't have access to the config files - My usual system is to not install it via the main account but log into the sub-account concerned and all usually works fine - but that 'hack' doesn't work anymore. I can't do any more that I can think of. Its annoying as I'm trying to get a website live.
no - phpmyadmin (or webdataadmin as HC likes to call it) - is installed by eukhost - so I don't have access to the config files - My usual system is to not install it via the main account but log into the sub-account concerned and all usually works fine - but that 'hack' doesn't work anymore. I can't do any more that I can think of. Its annoying as I'm trying to get a website live.
Hmmm. Does seem a tricky one. Maybe a recent update has caused the problems. Hopefully someone from support will be able to solve your problem soon. Good luck
I had the same problem, exactly the same error message. I deleted the webdataadmin instances and tried to reinstall but this was a bad move because it gave me an error message when I tried to reinstall.
eUKhost support fixed the problem for me but I noticed something interesting. When I tried to go in through the link in Hosting Controller it still came up with the same error message. So I closed all my browser windows and tried to access it straight from the address bar and it then worked fine!
I think maybe HC tried to pass login details across to PhpMyAdmin but gets it wrong? In future I'll try just logging in direct rather than going through HC