# Callback URL timeout with react SPA hosted on AWS s3 using Auth0

**URL:** <https://community.auth0.com/t/callback-url-timeout-with-react-spa-hosted-on-aws-s3-using-auth0/6836>\
**Category:** Get Help\
**Tags:** s3, aws, react, callback-urls\
**Created:** [June 1, 2017, 10:28am UTC](https://community.auth0.com/t/callback-url-timeout-with-react-spa-hosted-on-aws-s3-using-auth0/6836 "2017-06-01T10:28:02Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![sebastian.jezierski](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@sebastian.jezierski](https://community.auth0.com/u/sebastian.jezierski)\
**Post date:** [June 1, 2017, 10:28am UTC](https://community.auth0.com/t/callback-url-timeout-with-react-spa-hosted-on-aws-s3-using-auth0/6836/1 "2017-06-01T10:28:02Z")

</div>

I have a react SPA deployed on AWS s3 that uses Auth0 user authentication. The app, including login/logout flow, works fine on my local machine but fails with a timeout when trying to access the callback URL on the s3 deployed app.

I can see from the Auth0 logs that the user authentication succeeds but the app times out when trying to access the callback URL with the user token etc.

I have configured the callback URLs in the Auth0 client settings as below:

https://{my-app-name}.s3-website-ap-southeast-2.amazonaws.com, https://{my-app-name}.s3-website-ap-southeast-2.amazonaws.com/callback

and I have added https://{my-app-name}.s3-website-ap-southeast-2.amazonaws.com/callback as the callbackUrl parameter in auth0-variables.js.

As far as I can tell the s3 bucket is configured correctly and the app works for all non-protected routes.

---

<div class="post-metadata">

**Author:** ![prashantT](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/prashantt/32/6002_2.png) [@prashantT](https://community.auth0.com/u/prashantT)\
**Post date:** [June 1, 2017, 10:53am UTC](https://community.auth0.com/t/callback-url-timeout-with-react-spa-hosted-on-aws-s3-using-auth0/6836/2 "2017-06-01T10:53:41Z")

</div>

Can you try capturing a HAR file for the authentication flow to help us debug this.

> **[Generate and Analyze HAR Files](https://auth0.com/docs/troubleshoot/troubleshooting-tools/generate-and-analyze-har-files)**
>
> Learn how to troubleshoot with HAR files and steps to generate a HAR file.

Please remove any sensitive information from the file before sending it through.

---

<div class="post-metadata">

**Author:** ![sebastian.jezierski](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@sebastian.jezierski](https://community.auth0.com/u/sebastian.jezierski)\
**Post date:** [June 1, 2017, 11:06am UTC](https://community.auth0.com/t/callback-url-timeout-with-react-spa-hosted-on-aws-s3-using-auth0/6836/3 "2017-06-01T11:06:13Z")

</div>

Hi Prashant, thanks for your response, I’ve got the HAR file but can’t attach it here and am on the free plan so can’t log a support ticket… Any further suggestions?

---

<div class="post-metadata">

**Author:** ![prashantT](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/prashantt/32/6002_2.png) [@prashantT](https://community.auth0.com/u/prashantT)\
**Post date:** [June 1, 2017, 11:09am UTC](https://community.auth0.com/t/callback-url-timeout-with-react-spa-hosted-on-aws-s3-using-auth0/6836/4 "2017-06-01T11:09:25Z")

</div>

You can upload it to any cloud storage service (Google Drive, Dropbox, Onedrive) and share the link here. If you’d like to restrict access to only Auth0 staff, feel free to protect the URL to the `@auth0.com` email domain using [Sharelock.io](https://sharelock.io/).

---

<div class="post-metadata">

**Author:** ![sebastian.jezierski](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@sebastian.jezierski](https://community.auth0.com/u/sebastian.jezierski)\
**Post date:** [June 1, 2017, 11:29am UTC](https://community.auth0.com/t/callback-url-timeout-with-react-spa-hosted-on-aws-s3-using-auth0/6836/5 "2017-06-01T11:29:13Z")

</div>

I fixed it!

---

<div class="post-metadata">

**Author:** ![sebastian.jezierski](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@sebastian.jezierski](https://community.auth0.com/u/sebastian.jezierski)\
**Post date:** [June 1, 2017, 11:31am UTC](https://community.auth0.com/t/callback-url-timeout-with-react-spa-hosted-on-aws-s3-using-auth0/6836/6 "2017-06-01T11:31:09Z")

</div>

No worries, I managed to fix it

---

<div class="post-metadata">

**Author:** ![sebastian.jezierski](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@sebastian.jezierski](https://community.auth0.com/u/sebastian.jezierski)\
**Post date:** [June 1, 2017, 11:31am UTC](https://community.auth0.com/t/callback-url-timeout-with-react-spa-hosted-on-aws-s3-using-auth0/6836/7 "2017-06-01T11:31:09Z")

</div>

I managed to fix it.

Not exactly sure what I had wrong but after creating a new bucket and retyping all the config URL’s in both Auth0 and client code this problem was fixed. Possibly a typo or errant `/` somewhere.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [March 2, 2018, 5:54am UTC](https://community.auth0.com/t/callback-url-timeout-with-react-spa-hosted-on-aws-s3-using-auth0/6836/8 "2018-03-02T05:54:16Z")

</div>


