Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

ACS - Error code 502 after Transactional mailing move to prod

xavierv6303633
Level 3
Level 3

Hello,

 

I have the exact same issue as described in those two tickets : here and here.

 

We implemented transactional messaging on our Staging ACS instance, where everything works fine. After moving to production, we get the following error message when calling the transaction message API. (The token exchange works fine) : 

{

    "code": 502,

    "message": "Oops. Something went wrong. Check your URI and try again."

}

 

After seeing the response in the two tickets I referred, I created a second projet in I/O, specifically for Production, but I still get the same error. This doc seems to indicate it might be a CNAME issue, to check with support. Can this really be the issue? Does someone have an idea of what else might cause this?

 

The URI itself seems correct to me :

 

- Staging : https://mc.adobe.io/TENANT-mkt-stage1 /campaign/mcTENANT/EVTRecuVenteConnu

- Prod : https://mc.adobe.io/TENANT /campaign/mcTENANT/EVTRecuVenteConnu

 

Any help is appreciated!

 

SOLUTION EDIT : A separate Adobe I/O project is indeed mandatory for staging and production. The 502 issue in production was indeed related the a misconfiguration with the CNAME, which support could fix for us.

 

Kr,

Xavier

 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution
mmbb110
Correct answer by
Level 8
Level 8

you are on the right track, this is CNAME issue. Adobe support can fix this for you.

View solution in original post

3 Replies
mmbb110
Correct answer by
Level 8
Level 8

you are on the right track, this is CNAME issue. Adobe support can fix this for you.

View solution in original post

xavierv6303633
Level 3
Level 3
Ok great, I hope this is indeed the issue, which means an easy fix! I will update this thread whenever I get an answer from support, for future reference. Thanks for your reply!
xavierv6303633
Level 3
Level 3
After 1 week of waiting, 2 reminders and 1 escalation, support finally replied and fixed the issue, which was indeed related to the CNAME !