api.getgo.com token 400 Bad Request

Hi @openpressfr,

Where are you seeing these errors?

Do you want to try authenticating with our app instead? So remove your custom app details on the general options tab, save the settings, refresh the page, and then click the connect button again and see if that works?

Do you have any kind of firewall or security on your site? Maybe temporarily deactivate this?

And when you are getting these errors? Is this happens when you click on the Connect button? After you get redirected back to your site?

Thanks,

Hello,
Thanks for the feedback and sorry for my delay in responding.
I have tried both methods. The manual entry of Consumer Key from Secret. And the connect button with a Succes confirmation.
To do my tests I disabled LiteSpeed Cache.
I can’t clear the webinar cache and I get the following error in the browser console.

TypeError: response.trim is not a function
    at Object.success (adminscript.js?ver=14.39:46:25)
    at c (jquery.min.js?ver=3.6.3:2:28447)
    at Object.fireWith [as resolveWith] (jquery.min.js?ver=3.6.3:2:29192)
    at l (jquery.min.js?ver=3.6.3:2:80176)
    at XMLHttpRequest.<anonymous> (jquery.min.js?ver=3.6.3:2:82630)
(anonymes)	@	adminscript.js?ver=14.39:46
c	@	jquery.min.js?ver=3.6.3:2
fireWith	@	jquery.min.js?ver=3.6.3:2
l	@	jquery.min.js?ver=3.6.3:2
(anonymes)	@	jquery.min.js?ver=3.6.3:2
load (asynchrone)		
send	@	jquery.min.js?ver=3.6.3:2
ajax	@	jquery.min.js?ver=3.6.3:2
(anonymes)	@	jquery-migrate.min.js?ver=3.4.0:2
e.<computed>	@	jquery-migrate.min.js?ver=3.4.0:2
S.<computed>	@	jquery.min.js?ver=3.6.3:2
(anonymes)	@	adminscript.js?ver=14.39:44
dispatch	@	jquery.min.js?ver=3.6.3:2
y.handle	@	jquery.min.js?ver=3.6.3:2

The server is running LiteSpeed server enterprise and Imunify360.

I can create a Sandbox clone to help you debug.

Thanks

Hi @openpressfr,

Could you please try deactivating all other plugins except ours and then try the authentication.

Can you also turn off litespeed to see if that is an issue.

THanks,

Hi,

Thanks for the feedback.

I reconfigured wp-config by removing superfluous lines and now it works.

Fantastic, great to hear!