Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

403 every time I try to open the SDK

Community Beginner ,
Feb 19, 2025 Feb 19, 2025

adobe.png

this pops up every time I try to open SDK in a localhost environment. Yes - it is set in allowed domains, yes - it has https. Could you please take a look why is this happening?


Also is there a delay time between - chanigng the allowed domaind and actually seeing the change? I did a change adding a domain I wanted to test in on the production env. It din't work out. It worked out like 15 hours later without any changes from my side. Is there a way to speed this up?

 

Also2, I have a feeling it's very random sometimes in terms of whether it opens or not. Like it's I'm not in a mood now, vibes off - not working. And starts working an hour after (again no changes). Is it because it's not yet review?

Bug Unresolved
TOPICS
Embed SDK , Error
569
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
8 Comments
Adobe Employee ,
Feb 19, 2025 Feb 19, 2025

Hi, 
Can you please share the response headers obtained during the 403 response?
Also from which geo location the invocation to express is happening?
Tx!


Translate
Report
Community Beginner ,
Feb 19, 2025 Feb 19, 2025

I got this

 

403 ERROR
The request could not be satisfied.

Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

Generated by cloudfront (CloudFront)
Request ID: P_N7gXsnLBrkX8skJUp9bAdUMd6OzjL6keVkegKaof-tffHgCnceXw==

 

plus headers
HTTP/1.1 403
server: CloudFront
date: Wed, 19 Feb 2025 17:01:46 GMT
content-type: text/html
content-length: 919
alt-svc: h3=":443"; ma=86400
x-cache: Error from cloudfront
via: 1.1 bf8300a72b6d0584e2f6b1df22e3f548.cloudfront.net (CloudFront)
x-amz-cf-pop: WAW51-P3
x-amz-cf-id: P_N7gXsnLBrkX8skJUp9bAdUMd6OzjL6keVkegKaof-tffHgCnceXw==
X-Firefox-Http3: h3



Poland

 

Translate
Report
Adobe Employee ,
Feb 19, 2025 Feb 19, 2025

```
Also is there a delay time between - chanigng the allowed domaind and actually seeing the change? I did a change adding a domain I wanted to test in on the production env. It din't work out. It worked out like 15 hours later without any changes from my side. Is there a way to speed this up?```


Missed replying to this query.  The  domains are cached for performance improvement. Usually the Cache doesnt last for no longer then couple of hours. You can always bypass this cache by connecting to any VPN to any other area. 
HTH. 


On a side note, please share couple of more request ids and the request URL for better triaging. 

Translate
Report
Community Beginner ,
Feb 19, 2025 Feb 19, 2025

VPN not working for me, but I'll give it a few hours and see later on, thank you for clarification.

 

as for more ids

2z059cOjtyDzo5Egtq9box9jZywSTxIITEI-5jmh6HEsDjV5QWEbRA==

D5HWaQ7G0ApSy9_WutsoKmAlbZysxlwTBM_tPqSXtNXbyshCp9Wnlg==

m7BFo1aQ81jmLhe2K3RFxy8BdK0R2DqcBdYfh39dvP8H8xzeRxptVQ==

otBgt910QK0UvI3YO526EUmCBxutWxYsZPGDysgG59voZuCVceGuPw==

Translate
Report
Community Beginner ,
Feb 19, 2025 Feb 19, 2025

got it, thank you for clarify

 

Request ID: otBgt910QK0UvI3YO526EUmCBxutWxYsZPGDysgG59voZuCVceGuPw==

Request ID: m7BFo1aQ81jmLhe2K3RFxy8BdK0R2DqcBdYfh39dvP8H8xzeRxptVQ==

Request ID: D5HWaQ7G0ApSy9_WutsoKmAlbZysxlwTBM_tPqSXtNXbyshCp9Wnlg==

 

Translate
Report
Community Beginner ,
Feb 20, 2025 Feb 20, 2025

@Tarun Behari98BCcould you also tell what does this stands for?

 

fourth_5755_0-1740043726501.png

 

Translate
Report
Community Beginner ,
Feb 20, 2025 Feb 20, 2025

I debugged some more and looks like there still an issue witht the API key. I've no idea at this point why it's still not working. I tested the exact same settings (domain and API) with different account and it works just fine. But not here. 12 or more hours later, so I assume cache already refreshed.

 

// 20250220105538
// https://spark-content-publish.adobe.io/contributors/44941E7A67AF2C880A495CBC@AdobeID

{
"error_code": "403000",
"message": "Api Key is required"
}

Translate
Report
Community Beginner ,
Feb 20, 2025 Feb 20, 2025
LATEST

@Tarun Behari98BC We just submitted our app for review under the domain https://fourthwall.com. I would greatly appreciate your assistance in resolving the issues mentioned above, as this is the final step needed for us to complete the integration.


Please let me know if you need any additional information from our side. Thanks so much in advance for your help!

Translate
Report