Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Completely Blank Site #3437

Closed
5 tasks done
joelucky39 opened this issue Apr 22, 2023 · 8 comments
Closed
5 tasks done

Completely Blank Site #3437

joelucky39 opened this issue Apr 22, 2023 · 8 comments
Labels
archived This issue has been locked. bug Something isn't working compute investigating

Comments

@joelucky39
Copy link

Before opening, please confirm:

  • I have checked to see if my question is addressed in the FAQ.
  • I have searched for duplicate or closed issues.
  • I have read the guide for submitting bug reports.
  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.

App Id

d2ep79ifpnoq7t

AWS Region

us-east-1

Amplify Hosting feature

Frontend builds

Describe the bug

Using the provided link in the app https://main.d2ep79ifpnoq7t.amplifyapp.com nothing but a blank page loads.

All pages (routes) are blank. It's not exclusive to one page or the other. It's a complete fail.

I am only using the default URL provided by Amplify ( https://main.d2ep79ifpnoq7t.amplifyapp.com ). I want to point my DNS to the app but I'm not going to do it until I know if I have to use a different hosting service.

During build I received an error that I had to set images to unoptimized: true in next.config.js

I also had to set my build to next build instead of next build && next export. Because with that build setting pages with getServerSideProps could not be exported.

These are the build settings I am using.

version: 1
frontend:
phases:
preBuild:
commands: - npm ci
build:
commands: - npm run build
artifacts:
baseDirectory: .next
files: - '/*'
cache:
paths: - node_modules/
/*

Expected behavior

I expect to see the same site I see when I run next start locally.
site

Reproduction steps

Visit https://main.d2ep79ifpnoq7t.amplifyapp.com

Build Settings

version: 1frontend:  phases:    preBuild:      commands:        - npm ci    build:      commands:        - npm run build  artifacts:    baseDirectory: .next    files:      - '**/*'  cache:    paths:      - node_modules/**/*

Log output

# Put your logs below this line


Additional information

No response

@joelucky39 joelucky39 added bug Something isn't working pending-triage labels Apr 22, 2023
@joelucky39
Copy link
Author

It works fine in Vercel ( https://hydra-headless-23cqoo6de-joelucky39.vercel.app ). I believe it's an issue with the way Amplify uses environment variables ( or can't use them ).

@SamKomesarook
Copy link

#3436 I am also getting this issue

@SamKomesarook
Copy link

As per #3428, a Next upgrade should fix this.

@ghost
Copy link

ghost commented Apr 24, 2023

Hi @joelucky39 👋🏽 What version of Next.js are you using?

If you are using version 12 or later please try running the following AWS CLI commands:

Update the application's platform:
aws amplify update-app --app-id <APP_ID> --platform WEB_COMPUTE --region <REGION>

Update the branch framework:
aws amplify update-branch --app-id <APP_ID> --branch-name <BRANCH_NAME> --framework 'Next.js - SSR' --region <REGION>

@ghost ghost added the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label Apr 24, 2023
@github-actions
Copy link

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

@github-actions github-actions bot added the closing-soon This issue will automatically close in 4 days unless further comments are made. label Apr 27, 2023
@joelucky39
Copy link
Author

I'm using version 13. I'll update the platform and let you know. Thanks for your help.

@github-actions github-actions bot removed closing-soon This issue will automatically close in 4 days unless further comments are made. response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. labels Apr 29, 2023
@joelucky39
Copy link
Author

When I run the first command I get, "Unable to locate credentials. You can configure credentials by running "aws configure"

I'll just stick with Vercel. Thanks.

@ghost ghost closed this as completed May 10, 2023
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot added the archived This issue has been locked. label May 10, 2023
@github-actions github-actions bot locked and limited conversation to collaborators May 10, 2023
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
archived This issue has been locked. bug Something isn't working compute investigating
Projects
None yet
Development

No branches or pull requests

2 participants