Replies posted by songhieu

3 Replies

D
Contributor I
dev_ljContributor I
asked in Developer Group

500 internal server error on oauth with magento2

Hey @songhieu, 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:  If so, then this is a known issue pertaining to this Magento version as detailed in the Cannot Activate OAuth Magento 2.4.2 #122 Github. You can also find the solution to this from the following Magento post: Unable to activate integration with Oauth 1.0 I hope this helps! David I fixed this error but when I redirected to klaviyo and clicked on "Intergrate magento" I got a 500 error from klaviyo's server.

7
S
Contributor I
2 years ago
D
Contributor I
dev_ljContributor I
asked in Developer Group

500 internal server error on oauth with magento2

Hi @songhieu, Thanks for sharing this information. 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.    my magento version 2.4.2.

7
S
Contributor I
2 years ago
D
Contributor I
dev_ljContributor I
asked in Developer Group

500 internal server error on oauth with magento2

Hi @dev_lj, 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  

7
S
Contributor I
2 years ago

Most helpful members this week

Terms & ConditionsCookie settings

Links & Resources

Platforms

Partners

Useful Things

About

  • Terms and Privacy
    © 2024 Klaviyo All rights reserved. Klaviyo and the Klaviyo logo are trademarks or registered trademarks of Klaviyo, Inc. or its affiliates.