Known Issues and Troubleshooting
Review known issues and solutions.
Discuss in our Forum Discuss in SlackThis section provides information on known issues and solutions to common troubleshooting scenarios.
Known Issues
A repository can only be associated with one Front-End Site
Gatsby does not support SSR and DSG
Manual support is required
Preview functionality is not supported for Gatsby
Renaming a linked repository in GitHub will cause a break in your decoupled experience.
Select files can cause build errors
Select files, such as .dockerignore and .gcloudignore files can cause build errors or failed builds. Removing these files from source and adding them to .gitignore solves the issue.
Users must have permissions to enable decoupled for GitHub organization accounts.
How to uninstall a VCS
Uninstalling a GitHub application successfully requires manual intervention by the Pantheon Support team. Reach out to Support if you need to uninstall your GitHub application to connect and reinstall to a different GitHub account. If you have attempted to uninstall on your own and are unable to proceed, reach out to Support to correct your account.
Next.js 13 App Router
The caching recommendations outlined for use with our Next.js starter kits are currently only compatible with the Next.js Pages Router, not the App Router.
Troubleshooting
Build works locally but won't build on Pantheon
Follow the steps below if your build works locally but won't build on Pantheon.
Make sure any environment variables you have locally are set in the site’s Dashboard.
Verify that your scripts in
package.jsonhave an explicit step for build and start. For example:"scripts":{ "build": "next build", "start": "next start" }- If the build and start steps have a different name, specify it in the Dashboard in the Advanced Settings section when creating a site. You can also specify this in the Builds section of the site’s dashboard.
Images are not showing up on my Next.js site
Consult the Next.js docs on their image component. Set the IMAGE_DOMAIN environment variable if the images are coming from a domain that is different from your liked CMS.
Make sure you are passing the IMAGE_DOMAIN as a prefix to the src prop if you are using the next/image component. Refer to Next.js documentation for more information.