The klaviyo extension is installed and configured correctly and integration is added accordingly as well. When we go for activation , we are facing the following:
We are getting 500 internal server error while trying to perform integration oauth with magento2 CE on a local machine setup.
The oauth page does not close and gives this error. If i press on close window and cancel then it gives me the message of :
Integration 'klaviyo Auth' has been sent for activation.
and under my integrations tab in klaviyo i do not see it activated.
Thanks for sharing your question with the Klaviyo Community.
As a general first step it is a good idea to first try re-creating the OAuth Integration from Magento 2.
You can achieve this by going to Stores > Configuration > Klaviyo like below and create a new entry:
Then try activating the new entry and deleting the existing one.
However, in your case it appears that the instance of Magento you were testing was only accessible via the local network on your local computer and so Klaviyo had no way to reach the server. In order to avoid the error, you would need to make this instance public facing or use a cloud server.
Thanks for sharing your question with the Klaviyo Community.
As a general first step it is a good idea to first try re-creating the OAuth Integration from Magento 2.
You can achieve this by going to Stores > Configuration > Klaviyo like below and create a new entry:
Then try activating the new entry and deleting the existing one.
However, in your case it appears that the instance of Magento you were testing was only accessible via the local network on your local computer and so Klaviyo had no way to reach the server. In order to avoid the error, you would need to make this instance public facing or use a cloud server.
Thanks for sharing your question with the Klaviyo Community.
As a general first step it is a good idea to first try re-creating the OAuth Integration from Magento 2.
You can achieve this by going to Stores > Configuration > Klaviyo like below and create a new entry:
Then try activating the new entry and deleting the existing one.
However, in your case it appears that the instance of Magento you were testing was only accessible via the local network on your local computer and so Klaviyo had no way to reach the server. In order to avoid the error, you would need to make this instance public facing or use a cloud server.
Hi dov.derin My server is public but still getting this error, please check for me
Can you confirm if you are on Magento 2 versions 2.3.0 to 2.3.3? There have been reported issues of folks enabling oauth with these M2 versions. You can try upgrading your Magento Extension to version 2.3.4 or higher to resolve since this error is only occurring on 2.3.0 to 2.3.3, you shouldn't have a problem initiating OAuth in our more recent 2.3.4+ versions.
Can you confirm if you are on Magento 2 versions 2.3.0 to 2.3.3? There have been reported issues of folks enabling oauth with these M2 versions. You can try upgrading your Magento Extension to version 2.3.4 or higher to resolve since this error is only occurring on 2.3.0 to 2.3.3, you shouldn't have a problem initiating OAuth in our more recent 2.3.4+ versions.
Being on Magento version 2.4.2, when clicking on the Activate button, do you immediately receive a pop up notification with an error dialog stating “Something went wrong. Please try again later” as below:
Being on Magento version 2.4.2, when clicking on the Activate button, do you immediately receive a pop up notification with an error dialog stating “Something went wrong. Please try again later” as below:
