fetch requests fails as network errors on chrome console

[omar-dulaimi]

fetch requests fails as network errors on chrome console

[tj]

Unfortunately debugging that is pretty app-specific, since it means your app is either taking too long (say connecting to databases before, reading files etc) before listening on PORT. Sometimes it can be as simple as forgetting to pass process.env.PORT or perhaps passing it incorrectly to the server (if it expects a number instead of string for example).

[omar-dulaimi]

Hey @tj
Increasing the timeout did fix a big chunk of the issue to make development a little bit easier than before. But the problem still occurs randomly; first fetch sometimes, immediately sometimes, sometimes it's really slow to respond, etc.

Since you mentioned connecting the database, what we use is a Prisma 1 server hosted on EC2. That Prisma server in turns connects to our RDS database. Do you think the issue might be related to these parts?
I just don't want this issue to come to the production server once I merge the code there. Anything else I could do to better debug this?

[omar-dulaimi]

Locally it works perfectly fine though. So the requests passing through apigw and lambda run into unreported issue it seem.

[omar-dulaimi]

For whoever struggles with this in the future, make sure to remove docker completely. You're welcome!