ERROR: Manual Suspension Required - Login Failed

[PARoss]

Why am I getting this:

 

Cron Job Report for Friday 8th November 2013 @ 01:00:07

 

0 Invoices Created

 

0 Late Fees Added

 

0 Unpaid Invoice Payment Reminders Sent

 

0 Overdue Invoice Reminders Sent

 

0 Domain Renewal Notices Sent

 

0 Cancellation Requests Processed

 

0 Services Suspended

- ERROR: Manual Suspension Required - Login Failed - Heck Heckert - Starter Hosting Pkg. - dixiepaddle.com (Service ID: 34 - User ID: 3)

- ERROR: Manual Suspension Required - Login Failed - Heck Heckert - Starter Hosting Pkg. - padenny.com (Service ID: 29 - User ID: 3)

- ERROR: Manual Suspension Required - Login Failed - Heck Heckert - Starter Hosting Pkg. - phsclassof1966.com (Service ID: 39 - User ID: 3)

- ERROR: Manual Suspension Required - Login Failed - Heck Heckert - Starter Hosting Pkg. - yellowambulette.com (Service ID: 33 - User ID: 3)

- ERROR: Manual Suspension Required - Login Failed - Heck Heckert - Starter Hosting Pkg. - yellowtaxiparkersburg.com (Service ID: 18 - User ID: 3)

 

0 Fixed Term Terminations Processed

 

Processed Email Marketer Rules

 

Updated Disk & Bandwidth Usage Stats

[mlew2]

Looks like your whmcs and WHM aren't synced user and password in whmcs is different then in WHM (for your customers that is)

[bear]

It's not the client password, it's the reseller/root account used to manage it on that server from within WHMCS. We just saw one of these after a server change, where we had the wrong hash for the reseller account on the new server, and the process failed. Check the WHMCS reseller/root account credentials it was set up under, and make sure the client username(s) are right. If both are correct, it should process.

[mlew2]

I get along the same line of error and it is whmcs user and pass being different then WHM

[bear]

Why would it require the password for the user to perform an operation *on* the account itself by the account owner such as the reseller or root? To suspend (for instance), you only need permission to change that status on the account (the account owner, such as the reseller), and the hosted account username to change.

If what you're suggesting was true, a client could avoid automatic suspension/termination through WHMCS by simply changing the password in Cpanel, and since WHMCS is connecting as the reseller, that would mean you couldn't suspend even from WHM.

[mlew2]

NO what I mean is alot of my accounts have the passwords from WHM setup not though WHMCS that can give a different user and pass is all I was saying if all is setup through WHMCS all will be fine

[PARoss]

I did go through a server upgrade recently. I made the change, tomorrow will tell. Thanks.

[PARoss]

Same error this morning. What login in needed?

[bear]

For us, these clients had been migrated to a new box. The hash key to log in as the reseller that owned them (also moved there) was incorrect for that server. Visited WHM as that reseller, generated a new hash, and entered that as the log in within WHMCS for that server. That corrected it.

Another point, the attempt to log in and suspend the account with bad credentials caused CSF/LFD to deny access for the new server's IP. Unblocked it, added to ignore and it's working again. You can see if the info is right by looking at the usage statistics for one or more of the accounts, if you have yours set to "Update Usage Statistics" under Setup->Automation->Miscellaneous. If that's been running on the accounts in question and it has no stats listed, it's not connecting. After fixing ours, that was populated after the next run on the affected accounts.