Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

503 The request could not be satisfied.

See original GitHub issue

Describe the bug

I am using @sls-next/serverless-component @3.1.0-alpha.0. 503 error appears on the pages where getServerSideProps and getStaticProps is used.

Actual behavior

503 request error on cloudFront. where getServerSideProps and getStaticProps is used.

Expected behavior

The package should serve all the pages.

Project structure

Currently, I am using monorepo architecture for my application. The structure of the project is as follows:

Root
- Next app
  - next.config.json
  - node_modules
  - serverless.yml
  - package.json
- node_modules
- shared.js
- package.json
- cypress

Screenshots/Code/Logs

Serverless.yml : next.config.json:

Versions

OS/Environment: ubuntu debian
@sls-next/serverless-component version: 3.1.0-alpha.0
Next.js version: ^10.2.0

Checklist

You have reviewed the README and FAQs, which answers several common questions.
Please first try using the most recent latest or alpha @sls-next/serverless-component release version, which may have already fixed your issue or implemented the feature you are trying to use. Note that the old serverless-next.js component and the serverless-next.js plugin are deprecated and no longer maintained.

Issue Analytics

State:
Created 2 years ago
Comments:18

Top GitHub Comments

1reaction

Talhafayyaz11commented, Jun 29, 2021

But I think the real culprit was useServerlesstrace.

1reaction

Talhafayyaz11commented, Jun 28, 2021

Here is the code in experiment/offline-state-test

Top Results From Across the Web

503 ERROR The request could not be satisfied (AWS Amplify)

503 ERROR The request could not be satisfied. The Lambda function associated with the CloudFront distribution is invalid or doesn't have the ...

503 Errors - The request could not be satisfied · Issue #222

The request could not be satisfied. The Lambda function associated with the CloudFront distribution is invalid or doesn't have the required permissions. We...

What is HTTP error 503 and how do you fix it? - IT PRO

Essentially, the 503 error is your first warning that something is preventing the browser from accessing the website server. This is where said...

ERROR 503 The request could not be satisfied.

The Lambda function associated with the CloudFront distribution is invalid or doesn't have the required permissions. We can't connect to the ...

CloudFront with Lambda@Edge: 503 The request could not ...

I'm getting the following error while creating cloudfront and lambda@edge. I have used nodejs in lambda function. all are done using ...