Currently getting a 503 on all of my NextJsSite AP...
# sstd
Dillon Peterson
11/07/2021, 1:37 PMCurrently getting a 503 on all of my NextJsSite API endpoints. Has anyone else had this issue?
r
Ross Coundon
11/07/2021, 1:38 PM@Justin Philpott was seeing this yesterday
d
Dillon Peterson
11/07/2021, 1:48 PMI'm going to try updating to latest version of SST 0.50.2 to see if that fixes it.
Dillon Peterson
11/07/2021, 1:48 PMCurrently on 0.47.0
Dillon Peterson
11/07/2021, 1:48 PM@Justin Philpott I will keep you updated
Dillon Peterson
11/07/2021, 2:09 PMThat did not fix it.
f
Frank
11/07/2021, 5:28 PM
Hey @Dillon Peterson, was the site working before and started happening recently?
d
Dillon Peterson
11/07/2021, 5:30 PMYes Sir just started happening recently!
Dillon Peterson
11/07/2021, 5:30 PM@Frank
Dillon Peterson
11/07/2021, 5:30 PMAny ideas?
f
Frank
11/07/2021, 5:34 PM
Yeah, let’s do some debugging. Where are you currently located geographically?
d
Dillon Peterson
11/07/2021, 5:34 PMMcAllen TX
f
Frank
11/07/2021, 5:39 PM
I see when you view the Site, the logs are stored to ur local region.
Frank
11/07/2021, 5:40 PM
Can you try going into the CloudWatch console and select the Ohio us-east-2 region?
d
Dillon Peterson
11/07/2021, 5:44 PMYes Sir I will go check now
Dillon Peterson
11/07/2021, 5:47 PMI don't see us-East-2 showing anything.
f
Frank
11/07/2021, 5:48 PM
I see.. which region is the Site deployed to?
d
Dillon Peterson
11/07/2021, 5:48 PMus-east-1
f
Frank
11/07/2021, 5:49 PM
lemme give it a give try on my end
Frank
11/07/2021, 5:49 PM
are all pages not working? Or specifically SSG pages or SSR pages?
d
Dillon Peterson
11/07/2021, 5:49 PMIt's just the API Edge Lambdas
Dillon Peterson
11/07/2021, 5:50 PMAll front end pieces are working ok
f
Frank
11/07/2021, 5:51 PM
A few type of pages rely to Edge Lambdas behind the scene: the Server Side rendered pages, Client Side rendered pages, image optimization, etc
d
Dillon Peterson
11/07/2021, 5:51 PMI see this error.
f
Frank
11/07/2021, 5:54 PM
I see. Let me check something quickly.
Frank
11/07/2021, 5:57 PM
What’s the name of this log group?
f
Frank
11/07/2021, 6:27 PM
trying on my end..
Frank
11/07/2021, 6:46 PM
hmm… works on my end
Frank
11/07/2021, 6:46 PM
which version of Next.js are you using?
d
Dillon Peterson
11/07/2021, 7:15 PMLatest version!
Dillon Peterson
11/07/2021, 7:15 PMWhat about you?
Dillon Peterson
11/07/2021, 11:22 PMI'm trying now with same version from your NextJS tutorial
Dillon Peterson
11/07/2021, 11:23 PMWill keep y'all posted
f
Frank
11/07/2021, 11:23 PM
@Dillon Peterson sorry afk just now
d
Dillon Peterson
11/07/2021, 11:23 PM11.1.2
f
Frank
11/07/2021, 11:23 PM
so u were using the new Nextjs 12?
d
Dillon Peterson
11/07/2021, 11:24 PMYes Sir
Dillon Peterson
11/07/2021, 11:24 PMI was afk too, so no worries!!
f
Frank
11/07/2021, 11:24 PM
oh I see. Lemme give Nextjs 12 a try as well.
Frank
11/07/2021, 11:25 PM
just curious… any specific Nextjs 12 feature made u decide to update?
d
Dillon Peterson
11/07/2021, 11:29 PMNo Sir, the package.json just had "latest" in there, I wasn't locking versions yet. So it just got updated on an npm install
Dillon Peterson
11/07/2021, 11:29 PMI don't need any of the additional features of NextJs 12 for my current work. 😊
j
Joe Kendal
11/08/2021, 12:20 AM@Frank I would like to upgrade to v12 when SST supports it as we are looking to do A/B testing on our sites.
Joe Kendal
11/08/2021, 12:21 AMThe middleware seems to open a lot of use cases. Would be nice to plan for those in the future, although not essential
Joe Kendal
11/08/2021, 12:22 AMFeature flags too
f
Frank
11/08/2021, 12:48 AM
@Dillon Peterson I’m able to reproduce the issue after upgrading to v12
Frank
11/08/2021, 12:49 AM
Can you pin it to v11 and give it a try?
Frank
11/08/2021, 12:50 AM
@Joe Kendal Yeah for sure! v12 support is definitely on our roadmap.
t
Tharshan
11/08/2021, 9:36 AMI had a similar issue and concluded it was next 12 upgrade too! Looking forward to the support. I'm also mostly looking forward to using Middlewares
d
Dillon Peterson
11/08/2021, 2:55 PMThat fixed it!! Thank you so much @Frank.
Dillon Peterson
11/26/2021, 6:55 PM@Frank I'm getting this error again
Dillon Peterson
11/26/2021, 6:55 PMUsing NextJS 11.1.2
Dillon Peterson
11/26/2021, 6:56 PMSST version 0.53.0
Dillon Peterson
11/27/2021, 3:50 PMI've been going through everything, it's def some kind of AWS issue. I'm getting a 503 on every NextJS API endpoint, and also on every SSR page.
Dillon Peterson
11/27/2021, 4:07 PMOk, I think I found something. It appears the Lambda@Edge API functions are being assigned an IAM role that does not exist.
Dillon Peterson
11/27/2021, 5:46 PMAPI endpoints have been fixed by changing AWS CDK version. Now it's just the SSR pages not working. All returning 503s
j
Joe Kendal
12/04/2021, 12:46 PMI’ve decided to abandon this construct following the announcement of Vercel’s $100M round. They are committed to reinvesting in Next.js and their cloud so it will be next to impossible (pun not intended) for the open source project to keep up with features and performance.
2 Views