Skip to main content

Brute Force problem after cpanel update

Comments

6 comments

  • vincentg
    Re: Brute Force pproblem after cpanel update I found the user and password config file It's in /var/cpanel/hulkdpass I updated the password for it but no luck. But the today's update fixed it! That saved me time but would still like to know where the host entry is for the mysql connect. Why did all else work and yet Brute Force was giving a mysql connect error? The host name is from $hostname = Cpanel::Sys::Hostname::gethostname(); This info would be nice to know if one has a problem with Brute Force Mysql error. For those that would suggest I should have used /usr/local/cpanel/bin/hulkdsetup Tried it and it did not fix the problem yesterday. It would be nice if they could fix easy apache Mod Security connect problems. When I run easy apache it updates the password for the wrong connect entry. That's because they don't use update password = password() where user = "user-name" which would be the correct way. They instead use set password for user@host-name There are two entries for each user One for an IP address One for the server name It seems mod security connects using the IP address.
    0
  • cPanelMichael
    Re: Brute Force pproblem after cpanel update Hello :) Please submit a bug report for any flaws in cPanel/WHM via: Submit A Bug Report Ensure you open a separate report for each individual issue. You can post the ticket numbers here so we can update this thread with the outcome. Thank you.
    0
  • vincentg
    Re: Brute Force pproblem after cpanel update That link brings me to customer support. Are we supposed to submit bug problems there?
    0
  • cPanelMichael
    Re: Brute Force pproblem after cpanel update It should bring you to the customer portal, where you can sign in and submit the flaw. Thank you.
    0
  • vincentg
    Re: Brute Force pproblem after cpanel update Turns out that they fixed it as I ran Easyapache and no problems this time. No problems with Mod Security of which I experienced in the past. No need to submit a ticket.
    0
  • cPanelMichael
    I am happy to see the issue is no longer occurring. Thank you for updating us with the outcome.
    0

Please sign in to leave a comment.