Not being able to connect
exposuredesign
PROOP

2 years ago

My postgres Payload Admin server is Gateway timing out on frontend can see this error repeatedly in the log

@smithy/node-http-handler:WARN socket usage at capacity=50 and 726 additional requests are enqueued. See https://docs.aws.amazon.com/sdk-for-javascript/v3/developer-guide/node-configuring-maxsockets.html or increase socketAcquisitionWarningTimeout=(millis) in the NodeHttpHandler config.

Solved

11 Replies

brody
EMPLOYEE

2 years ago

Can you send a link to where we could experience this for ourselves.

exposuredesign
PROOP

2 years ago

https://lambethfringe.com/events/trashed

brody
EMPLOYEE

2 years ago

That's a Vercel hosted site, what part of your project is being hosted on Railway?

exposuredesign
PROOP

2 years ago

Here is a screenshot

Attachments

CleanShot%2...
exposuredesign
PROOP

2 years ago

The front end is a next site hosted on vercel that pulls data from a railway server with payload CMS running

exposuredesign
PROOP

2 years ago

The error log above is from the railway server

brody
EMPLOYEE

2 years ago

Please send a link to the Railway hosted application.

brody
EMPLOYEE

2 years ago

Looks like you have something missconfigured with payload, your question would be better asked in a payload forum of sorts since this isn't a platform issue, as we can't offer support for 3rd party software unfortunately.

exposuredesign
PROOP

2 years ago

Thanks. I've tracked it down to being something to do with a connection to aws s3.

brody
EMPLOYEE

2 years ago

I wish you the best of luck in solving this!

Status changed to Solved brody • over 1 year ago

Loading...