dgbaker

So been a faithful client for 14+ years and this is how they reward that loyalty? Time to start evaluating other solutions and show them what we think of their new licensing.

We are seeing similar issues. Did you get it figured out?

We are looking for the same type of option as well.

I have it resolved for us. Do you have IPv6 enabled on the server? We did and once we disabled it whmcs works perfectly for replies etc... Here's how to disable the protocol on a Red Hat-based system: Open a terminal window. Change to the root user. Issue the command sysctl -w net.ipv6.conf.all.disable_ipv6=1 Issue the command sysctl -w net.ipv6.conf.default.disable_ipv6=1 To re-enable IPv6, issue the following commands: sysctl -w net.ipv6.conf.all.disable_ipv6=0 sysctl -w net.ipv6.conf.default.disable_ipv6=0

Well figured one thing, when we use the mobile app aWHMCS there is zero lag replying to tickets. I suspect something is going screwing with possibly the htaccess file and redirects.

For you is it only with tickets? We see the issue with slowness on credit card capture as well. The capture itself is quick it's the whmcs update and redirect after capture that is slow.

We are running into the same issue with ticket open and replies and with invoice capturing. We've tried optimizing tables etc... without luck. This started just 2 days ago out of the blue. We are on 6.3.1 still.

We have two separate licenses and both were on same version. Well upgrading them to V6 and both had very different experiences and issues. The admin theme is pathetic. We rolled both sites back to 5.3.

Well said Stephen and couldn't agree more. As a cPanel forum Moderator (although not active for quite some time) I remember the days when support their was awesome. I am in no way though blaming front line support here, and yes it is the developers that need to listen. I can accept them not making a change if it was something silly or cosmetic, but when it is an issue that basically cripples their software for some of their customers this should be a higher concern that should be addressed in the software. PSIGate users are basically crippled from using this software without a true fix. I know I will be more actively looking at alternative software as a recourse to this issue and future.

What I don't understand is why not make the extremely simple change to psigate.php instead of screwing around with the O/S which as Stephen has just shown can cause way more issues with other software. As I stated in a ticket, it is WHMCS responsibility to ensure THEIR software works. I will say this is not the way WHMCS staff used to be, not sure why they have become so closed minded especially since PSIGate themselves have handed you a simple solution.

I am indeed on 6.5, done the whole upgrade/downgrade of openssl as well. WHMCS support basically not helping either and just keeps saying it's an O/S issue even though I have shown that we are using the latest openssl patch and still having the issue. The fact other gateway modules are not effected (like netbilling, paypal etc...) says that there is code specific in psigate that they should be looking at. I am not happy with WHMCS support cause they seem to be unwilling to help their clients even with work-arounds nor updating the software to work with 6.5 properly. P.S. I replied to your PM thanks.

Nope cause this works fine. openssl s_client -connect secure.psigate.com:443 -state Verify return code: 0 (ok)

We were on 5.2.12 and just upgraded to 5.2.14 and still same issue. At least I know we aren't alone.

Hey all; I am hoping someone (maybe a linux guru?) can help me out with this urgent issue. I have a ticket open but still can't get this resolved. Here is the issue, our PSIGate gateway module died the other night with the following error: Error => 1035 Error Message => error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol We have tried the solutions from support for updating a broken openssl that was said to fix this issue. Well, in our case it has not fixed it. We have the latest openssl installed; rpm -qa |grep openssl openssl-devel-1.0.1e-16.el6_5.x86_64 openssl-1.0.1e-16.el6_5.x86_64 Openssl connects to PSIGate without issue. openssl s_client -connect secure.psigate.com:443 -state Verify return code: 0 (ok) Yet when we run a credit card through PSIGate we get the same error as above. We've spoke with PSIGate support and they do not even see a connection attempt from us so we know it has to do something on our end. Anyone out there have any thoughts on getting this working again? As it stands we are kinda dead as a company if we cannot process credit card payments. As an addon to this, one of our other servers (exact same setup O/S and all) we have a client using whmcs and netbilling and it works fine. Thanks for any help or suggestions. David

Can tell you right now it is a WHMCS issue. We have seen a few installs on different servers having this issue and a simple look through these forums should say it is a WHMCS issue as there cannot be that many servers that are incorrect. Guess time to look for a better billing system maybe?