-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Navigation issues in production. #2399
Comments
Unsure if that’s related but navigating from 404 pages is broken too. |
I’m having other issues when deploying to Netlify: http://piotrf.pl/ (problematic) vs. http://v2piotrfpl.netlify.com/ (all seems to work). It’s the same environment, but the former under custom domain and breaks for some reason.
This is awkward and I don’t really know how to deal with it just yet. Any help appreciated. |
I found this hint in another issue, seems like making following amends to
|
I’m getting a bunch of errors when navigating between some of the pages:
Steps to reproduce:
Read case study
linkExpected behaviour: navigate to http://piotrf.pl/made/palestine-remix and display related content
Actual behaviour: url is being updated, but content is not being presented, above console.log errors are returned. Refreshing the page then does show the proper content.
Note how it’s all OK when accessing s3 bucket directly: http://v2.piotrf.pl.s3-website.eu-central-1.amazonaws.com/ It’s also fine when running
gatsby serve
locally.Could this be gatsby or should I take it with S3?
Gatsby versions from my package.json:
The text was updated successfully, but these errors were encountered: