Following the instruction to install the extension for magento 2.4.1 I came across an error when activating the integration. Once click integrate Magento 2 on the popup window, I was told the error message below. I double checked the API details are correct, and also the firewall Sucuri is not blocking Klaviyo. Anyone has experienced the same issue?
There was an error while integrating your Klaviyo account with Magento 2. Below are the details about your error
Klaviyo is unable to connect to Magento Server for OAuth Handshake.Url tried was: https://www.xxxxxx/oauth/token/requestPlease ensure that both /oauth/token/request and /oauth/token/accessare accessible
Best answer by klaviyojadView original
Moreover what do you get as a response if you plugged the Urls tried in the error message in your browser?
Does the response start with: ”oauth_problem=”?
If not then its an indication that the server rewrite rules are not set up correctly to route to the oauth api endpoint in magento2.
If so then we would need to work on this case via a support ticket. A member of Klaviyo Success Engineers would need access to Magento Admin to investigate more closely.
Apologies on the delay in response. I have located the ticket submitted for the account id and responded to it. You should have received an email if you were the original sender
Thank you so much for reaching out to the Klaviyo Community for integration support!
@klaviyojad Thank you for jumping in to help solve this challenge! It’s collaboration like this that makes the Klaviyo Community, and Klaviyo as a whole, so much stronger. I’m grateful that as a team, we are able to help solve most challenges together.
@Ryancaremax and @klaviyojad for being a valued part of our community!
I’m getting the same error running an Magento 2.4.1 store version.
@klaviyojad had ask if the website url is public… In my case it is not, since it is a stagging account, and it is protected by a user and password to access.
In my case,I’m trying to connect an stagging acccount to see how things first works, and to not run into problems in the live account.
I see that
Is this an problem, and can this be the origin to get the exactly same error has first reported?
Can anyone give the Ip´s used from Klaviyo in order to whitelist it and this way try to connect to staging environment?
@klaviyojad I already ffound your other reply related to my question. @klaviyojad recommendation and post
Please, any other with my question see