Question

15

403 Access Error returned from Browser possibly caused by AWS

rated 0 times [ 16] [ 1] / answers: 1 / hits: 5618 / 4 Years ago, wed, january 29, 2020, 12:00:00

I have my serverless web app hosted on AWS amplify. I am getting Access Denied error XML if I try refreshing the page. When I look into the Console, it shows no output. The code works fine on localhost, but will cause 403 error on live.

I have found a question that is very similar, except I did not use CloudFront.

How can I find a potential cause of this problem?

Update

I solved this, and I posted the answer in the answer section. However I now have a part 2 of this question.

How do I make it so that the client can directly call my URL like such:

https://URL.com/listing/LISTING_ID

Right now, if I try to call it directly while passing a LISTING_ID the page errors out. Does this have anything to do with Isomorphic ReactJs?

I have tried using Digital Ocean as my web hosting service instead of AWS. The same error happens.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

nestorjarettg

Add To Favorites

Follow

Total Points: 451

Total Questions: 108

Total Answers: 108

Location: Rwanda

Member since Thu, Feb 10, 2022

2 Years ago

nestorjarettg questions

1 Discord Bot Not Playing Audio discord.js v13

Sat, Sep 25, 21, 00:00, 3 Years ago

1 Access and modify react context from jest test with react testing library

Wed, Sep 9, 20, 00:00, 4 Years ago

1 Uncaught ReferenceError: _ is not defined at < anonymous>:1:1 (Not jQuery)

Sun, Feb 16, 20, 00:00, 4 Years ago

1 Uncaught TypeError: Class extends value #< Object> is not a constructor or null

Mon, Jan 13, 20, 00:00, 4 Years ago

1 React overwrite component function

Tue, Dec 4, 18, 00:00, 6 Years ago

View All

answered 4 Years ago arthur · Accepted Answer

I solved this by moving from AWS to Nginx for hosting.

And added this to etc/nginx/sites_available/default

location / {

                # First attempt to serve request as file, then

                # as directory, then fall back to displaying a 404.

                #try_files $uri $uri/ =404;

                try_files $uri /index.html;

        }

The reason why this is happening is because my app was a single paged app. Refreshing causes the browser to request the server, and the server does not handle requests.