Any way to isolate these issues on deployment (vercel)?

Developer Support
1

During deployments with vercel a bunch of issues arise that I can’t see to isolate (due to our site having many pages and my lack of debugging experience with plasmic):

  1. PLASMIC: Encountered error when pre-rendering : Error: {“error”:{“message”:“Internal Server Error”}}
  2. Invalid href ‘/blog//blog’ passed to next/router in page: ‘/[[…catchall]]’. Repeated forward-slashes (//) or backslashes \ are not valid in the href.

Issue #1 occurs twice in the deployment log, while issue #2 appears 20-30 times, however I’m unsure where this issue is coming from and between the previous deployment (where the error didn’t exist) and the current one, there aren’t any new pages or changes to linking that would cause this issue, and the blog itself is hardly linked anywhere outside of navigation.

My question is if there if anyone knows how to get more information from the logs, or isolate the pages that are causing the issues (as the catchall stops me from being able to see the pages causing the issue).

It may be worth noting that when a page size is high, it specifies the page url slug, though in these circumstances it doesn’t. It’s also worth noting that the site still deploys without any issues despite these errors during deployment.

Thank you!

2

@jvx4 Hi!

  1. The first error is most likely related to some data queries on your page.
    We can definitely do a bit better in terms of error handling for such cases, it’s quite hard to debug from Vercel logs. If you run the app locally in the dev mode, it should provide way more data about this issue.

  2. This seems to be a legit warning. You should avoid preceeding slashes (i.e. /blog) in the url name, because it’s already there

And an off-topic, but still related to debugging – we recently posted an updated doc which includes some tips about how to debug your app in studio, and we launched a new feature called expression search. You can now search for your code snippets and dynamic values from the left sidebar.

3

Hi alex, thank you for the response. the blog issue was an easy solve, it was indeed a link leading to /blog instead of selecting a page.

I’m not sure how, though the first error managed to correct itself after duplicating the project and cleaning un-used components. I believe it was due to a hidden component with a form and integration inside of it (if that helps anyone else).

Thank you

1 Like