Error We were unable to connect your account. Please contact your system administrator

[graisbeck]

18 hours ago, brian! said:

possibly because you're still using the "Modern" and I think there's an issue in v7.6 with MarketConnect adding promo banners at the viewcart stage - they can cause Modern to have a fit, but standard_cart can handle without issue... switching to standard_cart might be a short-term fix for now as Modern hasn't really been updated in years... or disable the cart/checkout promo settings in MarketConnect.

I now get an 'Error We were unable to connect your account. Please contact your system administrator.', I'm using standard order form. Please see image and ignore 'Issue 1' as that post is under 'Using WHMCS'

[brian!]

12 minutes ago, graisbeck said:

I now get an 'Error We were unable to connect your account. Please contact your system administrator.', I'm using standard order form. Please see image and ignore 'Issue 1' as that post is under 'Using WHMCS'

seeing as you're using a @zomex template, the thread below might be more relevant... you may need to contact Jack and get an update for the Horizon template.

https://www.zomex.com/docs/whmcs-templates/how-to-support-whmcs-v7-6.php

[Rangka Kacang]

I keep getting this "Domain Sync Cron Emails" every 4 hours after updating to 7.6 and this is annoying. Or at least try to combine it with the "WHMCS Cron Job Activity" email or something? There should be a feature where email should only sent out if an error is found... I mean, let's say I handle 10 billing platforms using the same email address and I'm receiving all these emails every 4 hours... in 1 day, I get about 60 email notifications...

This question was asked in 2013 (5 years ago) and it's still happening now. I mean like, are they even listening to their customers?

 

[zomex]

On 8/4/2018 at 9:24 AM, graisbeck said:

I now get an 'Error We were unable to connect your account. Please contact your system administrator.', I'm using standard order form. Please see image and ignore 'Issue 1' as that post is under 'Using WHMCS'

Thanks @brian!

I have replied to your ticket.

Issue 1 is not related to your template and is instead a WHMCS issue (if a issue at all, it may be a designed feature).

Issue 2 is due to using a outdated file within the template, I have replied to your ticket with the updated file.

Thanks,
Jack

[graisbeck]

9 hours ago, zomex said:

Thanks @brian!

I have replied to your ticket.

Issue 1 is not related to your template and is instead a WHMCS issue (if a issue at all, it may be a designed feature).

Issue 2 is due to using a outdated file within the template, I have replied to your ticket with the updated file.

Thanks,
Jack

Thanks again Jack!

[zomex]

On 8/6/2018 at 8:31 AM, graisbeck said:

Thanks again Jack!

Happy to help

[cmshosting]

Hi guys,

I still have the same error ,i am using Antler as my template,

I have tried all the solutions offered but i cannot make it work

[keyboardmls]

On 7/4/2020 at 5:54 AM, cmshosting said:

Hi guys,

I still have the same error ,i am using Antler as my template,

I have tried all the solutions offered but i cannot make it work

Were you able to find a solution for the Antler theme? I am having the same issue.

[gameznet]

I am also having this issue...

cannot get any of the sign-in integrations to work, have triple checked all settings with each of them..

  Error We were unable to connect your account. Please contact your system administrator.

has it been fixed?

 

[7xweb]

Hello!

Thank you for sharing your experience with this error as it helped me fix my own same error.

I encountered this exact same problem with my whmcs new installation and the theme from rsthemes called lagom available in the marketplace.

I didn’t have direct access to support from the theme creator at the time but I am a experienced developer.

I needed a quick fix and found that after reading the console log errors in the browser found the solution was to include the whmcs/payment.js file via html script include in the theme head.tpl 

Once I did this the error was resolved correctly and registration was error free.

I would like to share this with the authors of this thread, further users with a similar problem, the theme authors and the whmcs vendor.

We think action needs to be taken to insure  this problem is more properly documented and addressed by the authors of your whmcs software publishers.

[7xweb]

Hello Again!

 

Thank you again for sharing with the community your own unique experiences with WHMCS software and it's usage by new users and experienced developers alike.

I write this day to say we just re-implemented our whmcs store and I had to patch again the default theme 'twenty-one' to include head.tpl theme modifications to add script tags including jquery and `whmcs.js` to correctly resolve the error on what apears to be a newer version of whcms javascript libraries for payment.

Every thing seems cleanly implemented just not included.

This is a big improvement from the last time I tried to implement this threads solution myself.

Now the whole whmcs javscript is wrapped in jquery and it's clear no more individual payment.js source file including needed, just include 'whmcs.js' in the head.tpl to solve the error message that we are all getting by default in the default software options.

I'm shocked a little that whmcs themes are so badly maintained that they don't even document key required steps in the use of Google Signin/Registration Authentication Module.

It's an easy to fix, harder to maintain the patches situation ... Is there someone who could be reached at whmcs offices about new customer problems? Oh right, support fees 😕