In order to resolve this issue, you have to login to your cpanel >> change password option and reset the password that you are using for cpanel.
In order to resolve this issue, you have to login to your cpanel >> change password option and reset the password that you are using for cpanel.
I have come across a similar issue, but mine appears to be due to password complexity requirements in cpanel.
Thus, what I found is that fantastico reported a successful WP installation. However, we were seeing the loathed white screen.
Checking the sql setup revealed that the database user was not assigned to the database. Trying to do so manually with the password in wp-config.php revealed that the user could not be added due to the password not being sufficient complex to meet the requirements enforced via whm/cpanel settings (in this case, only 40% requirement.)
This would appear to be a Netenberg issue - I do not see any option in Fantastico that would allow complexity requirements to be set.
Unfortunately, I've found Netenberg support to be horrible.
Does anybody know of a fix or workaround, other than dumbing down the password complexity requirements in cpanel?
Thanks.
Mike
Get your hosting business listed on www.HostPremiums.com.
Visit www.decomodo.com for cool stuff you can't live without.
All the same, this should be posted to their forum. I've just reposted for you there in the Bug Reports forum.
https://netenberg.com/forum.html/index.php&topic=7606.0
Fav cPlinks this week: Blog - cPanel & WHM 11.32 we love it! | cPanel University study for it! | Attracta is coming! we want this!
I'm not sure you correctly understood the issue I've described. The issue is that Fantastico is assigning a database user password that does not meet the complexity requirements defined in WHM/cpanel. This means that the database user does not get assigned.
This has nothing to do with accessing Fantastico or its features.
Get your hosting business listed on www.HostPremiums.com.
Visit www.decomodo.com for cool stuff you can't live without.
Ran into the same issue -- it was the password complexity.
Use a more complex password, or manually adjust the complexity settings for MySQL users in WHM => Password Strength Configuration
Once you do that, it'll work fine.