Diploy Posted February 19, 2014 Share Posted February 19, 2014 I have been going crazy over this issue. And so far i yet to hear back from whmcs support (been like almost 2 days). I have set the secretword, i have white listed the 2checkout ips also in cfs whm/cpanel firewall. I can get to the file tco.php when type it in the address bar. I have updated the api passowrd, setup secret words. I have also uploaded an old version of tco but i keep getting that error in the gateway log. The only reason i can think of this is happening is because of the file, maybe its encryption got corrupted or something like that. After searching every where to solve the problem i am asking your help with the issue. Hope some one can give me their file or tell me how to fix that or where to look on the server that might be the cause of this, or anything else. thanks 0 Quote Link to comment Share on other sites More sharing options...
tmx Posted September 19, 2014 Share Posted September 19, 2014 Did you ever find a solution? having the same problem here. Everything is spot-on. Secret word, callback urls, etc....like you, all I can come up with is the possibility of data/encryption corruption somewhere along the line. Thanks, -Bob I have been going crazy over this issue. And so far i yet to hear back from whmcs support (been like almost 2 days). I have set the secretword, i have white listed the 2checkout ips also in cfs whm/cpanel firewall. I can get to the file tco.php when type it in the address bar. I have updated the api passowrd, setup secret words. I have also uploaded an old version of tco but i keep getting that error in the gateway log. The only reason i can think of this is happening is because of the file, maybe its encryption got corrupted or something like that. After searching every where to solve the problem i am asking your help with the issue. Hope some one can give me their file or tell me how to fix that or where to look on the server that might be the cause of this, or anything else. thanks 0 Quote Link to comment Share on other sites More sharing options...
snake Posted September 21, 2014 Share Posted September 21, 2014 if this problem has only started for since 5.3.9 then I can tell you why, as our md5 hashing alsos topped working. it was because the md5 hash is now case sensitive since 5.3.9 and must be in lower case. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.