I’m having an issue getting preview to work with a live URL. Preview works perfectly fine when running on localhost on gatsby develop (localhost:8000) and it also works perfectly fine when doing gatsby build & gatsby serve (localhost:9000), but as soon as I change the domain name to a live URL it d…

Hey Rob! Have you checked if the configuration for the production URL route is enabled? A configuration for each environment is required if you’re going to preview in each one: development, build and production, Also, check your link Resolver and add the properties validation: const linkResolver …

FWIW: I"m having the exact same problem. In my case it is using AWS Amplify for hosting, but probably the same deal. I’ve tried all manner of link resolver and gatsby config adjustments, and just can’t get to seem to get it to work outside of localhost.

Hi Paulina, Thanks for replying. I do have the different URL routes enabled and I just tried adding in the properties check inside my link resolver but still no luck. If I click the preview button to view changes on localhost it hits the following URLs: http://localhost:9000/preview?token=previ…

Following what we talked about on Twitter it appears to probably be an issue with AWS removing query string parameters if the URL doesn’t have a trailing slash :confused: let us know if you figure out something (or not) this way @robsimpson !

So I’ve managed to get it to work for everything except unpublished pages now. It appears to be a trailing / issue, so by setting my linkResolver to /preview/ (in the Prismic config section) this makes preview redirect to the correct page (if it’s already published) but doesn’t redirect to the corr…

Ah! Great @robsimpson , this sounds like the core issue then, and likely explains why I’m seeing the same thing on Amplify. Following this thread with eagle eyes @lihbr @Pau let us know if you have any ideas as to how we might finally push this one to the ‘resolved’ pile (there its lots of conversat…

I am also using AWS Amplify for hosting. I have found that the trailing slash alone did not work for my previews. By adding the following redirect rule to Amplify has fixed the preview issue for me, together with adding the trailing slash in the Prismic preview configuration /preview/ { "sour…

Note that I have created a new topic for this preview issue I am facing if anyone else is experiencing the same thing. [image] Gatsby preview URL / path not correct using gatsby-source-prismic-graphql Developing with Prismic I am having problems with the preview functiona…

We use Netlify and it works flawlessly.

Hello @williambell9708 Welcome to the Prismic community, and thanks for reaching out to us. I am glad that previews are working with Netlify flawlessly. Let us know if you have any other questions. Priyanka

Gatsby Prismic preview only working on localhost

Developing with Prismic

adrian (Adrian Hoess) July 9, 2020, 7:38am 9

Note that I have created a new topic for this preview issue I am facing if anyone else is experiencing the same thing.

Topic		Replies	Views
Gatsby preview URL / path not correct using gatsby-source-prismic-graphql Developing with Prismic gatsby	7	1601	November 3, 2020
Prismic Preview not redirected in Gatsby Developing with Prismic gatsby	1	664	November 25, 2021
Gatsby Cloud & Prismic Preview issue Developing with Prismic gatsby	1	442	November 8, 2021
Update preview url in settings then only homepage shows up Developing with Prismic gatsby	9	895	July 1, 2020
Gatsby + Prismic Previews on a staging environment/subdomain Developing with Prismic	1	1039	December 2, 2020

Gatsby Prismic preview only working on localhost

Related topics