#subin_error

1 messages · Page 1 of 1 (latest)

maiden irisBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1370331995070009394

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

ancient warren
#

Dear Stripe Support,
I’m reaching out regarding an issue encountered during the OAuth integration process for Stripe Connect.
I have been following the official documentation for Stripe’s OAuth integration. My current implementation is hosted on a Cloudways server, where the flow works as expected. Upon successful connection, the redirect URI receives a response like the following:
code=ac_SAe21H7Bc53fsmYLq5rppu7AYO5JyHjY&user_id=usr_MTMsOxAahaiTvo&account_id=acct_1MgkSrCxZV7Ws7XN&stripe_user_id=acct_1MgkSrCxZV7Ws7XN&state=aHR0cHM6Ly93b3JkcHJlc3MtMTA0NjE5OC01MzY1ODYxLmNsb3Vkd2F5c2FwcHMuY29tLz93Yy1hcGk9d3Rfc3RyaXBlX29hdXRoX3VwZGF0ZSZtb2RlPXRlc3QmbmFtZT1laF9zdHJpcGVfcGF5bWVudF9nYXRld2F5
However, after migrating the same codebase to an
AWS server, I receive the following unexpected data at the redirect URI:
{"_gcl_au":"1.1.2099103451.1743759728","_ga":"GA1.1.1260244605.1743759728","_ga_BQH8MSKD4M":"GS1.1.1745219754.5.0.1745219754.60.0.1179731273"}
This looks like cookie tracking data (possibly from Google Analytics) instead of the expected OAuth parameters like
code, user_id, etc.
Here’the part of code handling the redirect endpoint:
function stripe_oauth_verification() {
try {
$log_file = WP_CONTENT_DIR . '/oauth-connect-log.txt';
ini_set('error_log', $log_file);
error_log('Connect response - ' . json_encode($_REQUEST));

}
I’ve verified that the redirect URI is configured correctly in the Stripe app settings and that the same integration logic is used on both servers.
Could you please help me understand why the AWS server is not receiving the proper OAuth parameters in the redirect response? Any insight or guidance would be greatly appreciated.
Documentation followed:
https://stripe.com/docs/connect/oauth-reference

magic fog
#

👋 happy to help

lean dust
#

{"_gcl_au":"1.1.2099103451.1743759728","_ga":"GA1.1.1260244605.1743759728","_ga_BQH8MSKD4M":"GS1.1.1745219754.5.0.1745219754.60.0.1179731273"}
You received this on what endpoint exactly ? on the redirect url ? This seems like an analytic tracking call

#

Stripe doesn't differenciate between your hosting providers, as the same integration was working correctly on the "Cloudways", there must be other changes you did on the integration to add some analytics on the same redirect endpoint...

#

This could be a deployment conflict or something...

ancient warren
#

on the redirect url

maiden irisBOT