#Looks like Sentry is picking up an internal Astro error?

29 messages · Page 1 of 1 (latest)

open helm
#

I've got a recurring error on my latest SSR Astro app.

NoMatchingRenderer
 
GET /api/v1/timelines/public

Ongoing
Level: Error
Unhandled
Unable to render `default`. No valid renderer was found for this file extension.

I don't have an API route or folder structure of api/vi/timelines/public so not sure why that error is firing for me.

Here's a link to my project to confirm: https://github.com/whitep4nth3r/p4nth3rworld

App is hosted on Netlify.

More stack trace info:

GitHub

Contribute to whitep4nth3r/p4nth3rworld development by creating an account on GitHub.

open helm
#

cc @lean crystal because I can

lean crystal
#

Am I your personal support staff now Salma?! So in my massive experience, that error is when it's trying to render something that's not real content. Have you tried running it locally and seeing if hitting that route logs that error? I'm guessing it's something to do with the 404 not rtendering properly, which is beign triggered by some old bot or something hitting that path

#

I note that all 404 routes on your site are returning a blank page

open helm
#

yeah I don't have a 404 set up

#

(and yes, obviously you're my personal support staff)

#

This site isn't worthy of a 404 yet as it has three pages

#

and anyway, doesn't astro come with a built in 404? 🫠

#

I'm only half joking

lean crystal
#

Yeah, it does which is what's weird here. I think that's the source of the issue though

open helm
#

Hitting any 404 locally serves the correct 404, including the api/v1/instance route which caught the error in prod

#

... perhaps this is a Netlify problem 🫠

#

I'm accessing the local site on port 4321, whilst running the netlify CLI, because the site doesn't work on 8888 due to middleware issues

#

that being said, on port 8888, the 404s work as expected locally

lean crystal
#

Does netlify serve have the same errors?

open helm
#

This is what happens when I try netlify serve

  errno: -2,
  code: 'ENOENT',
  syscall: 'lstat',
  path: '/Users/salma/dev/p4nth3rworld/.netlify/functions-serve/.unzipped/ssr/ssr.js'
}```
#

And interestingly I received an error in prod related to netlify yesterday

#

the file /var/task/.netlify/functions-internal/ssr/ssr.mjs

lean crystal
#

I don't think that's Astro code.

open helm
#

🫠

#

I'm trying to find out where I can report these issues to Netlify 🙂

lean crystal
#

I don't think it's Netlify either!

#

That looks like Sentry code

open helm
#

ah no

#

it's Auth.js code

#

which is experimental for Astro

#

and the experience doesn't full work anyway 😄

#

well line 1500 is at least auth.js code

#

where it errors at 1495 looks like where Astro is trying to delete the Set-Cookie header