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
BedrockMission!

Learn More

View all

Sign in to view all badges

ACS - Error code 502 after Transactional mailing move to prod

Avatar

Avatar
Boost 5
Level 2
xavierv6303633
Level 2

Likes

6 likes

Total Posts

21 posts

Correct Reply

1 solution
Top badges earned
Boost 5
Validate 1
Contributor
Shape 1
Boost 3
View profile

Avatar
Boost 5
Level 2
xavierv6303633
Level 2

Likes

6 likes

Total Posts

21 posts

Correct Reply

1 solution
Top badges earned
Boost 5
Validate 1
Contributor
Shape 1
Boost 3
View profile
xavierv6303633
Level 2

29-06-2021

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

 

502 CNAME IO transactional message

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 25
Level 4
mmbb110
Level 4

Likes

23 likes

Total Posts

339 posts

Correct Reply

21 solutions
Top badges earned
Validate 25
Applaud 25
Validate 10
Validate 1
Contributor
View profile

Avatar
Validate 25
Level 4
mmbb110
Level 4

Likes

23 likes

Total Posts

339 posts

Correct Reply

21 solutions
Top badges earned
Validate 25
Applaud 25
Validate 10
Validate 1
Contributor
View profile
mmbb110
Level 4

29-06-2021

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

Answers (0)