#payloadcms.com CMS and API outage?

23 messages · Page 1 of 1 (latest)

wanton drift
#

My CMS and API stopped working sometime on Oct 24. Is anyone else having this issue? The runtime logs show MongoDB connectivity errors, but I'm able to connect using the URI. The logs show:

(payload): MongoNetworkError: getaddrinfo ENOTFOUND ac-eprzywu-lb.skhjo38.mongodb.net
[2025-10-26T06:12:12]
at connectionFailureError (/workspace/node_modules/mongodb/lib/cmap/connect.js:387:20)
[2025-10-26T06:12:12]
at TLSSocket.<anonymous> (/workspace/node_modules/mongodb/lib/cmap/connect.js:310:22)
[2025-10-26T06:12:12]
at Object.onceWrapper (node:events:633:26)
[2025-10-26T06:12:12]
at TLSSocket.emit (node:events:518:28)
[2025-10-26T06:12:12]
at emitErrorNT (node:internal/streams/destroy:170:8)
[2025-10-26T06:12:12]
at emitErrorCloseNT (node:internal/streams/destroy:129:3)
[2025-10-26T06:12:12]
at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
[2025-10-26T06:12:15]
(payload): MongoNetworkError: getaddrinfo ENOTFOUND ac-eprzywu-lb.skhjo38.mongodb.net
[2025-10-26T06:12:15]
at connectionFailureError (/workspace/node_modules/mongodb/lib/cmap/connect.js:387:20)
[2025-10-26T06:12:15]
at TLSSocket.<anonymous> (/workspace/node_modules/mongodb/lib/cmap/connect.js:310:22)
[2025-10-26T06:12:15]
at Object.onceWrapper (node:events:633:26)
[2025-10-26T06:12:15]
at TLSSocket.emit (node:events:518:28)
[2025-10-26T06:12:15]
at emitErrorNT (node:internal/streams/destroy:170:8)
[2025-10-26T06:12:15]
at emitErrorCloseNT (node:internal/streams/destroy:129:3)
[2025-10-26T06:12:15]
at process.processTicksAndRejections (node:internal/process/task_queues:90:21)```

I can't find any way around this and I don't have any support contact to PayloadCMS Cloud. Would greatly appreciete any advice.
cold sonnetBOT
wanton drift
#

A bit more info - the problem started at teh timestamp below from the runtime logs:

(payload): MongoNetworkError: getaddrinfo ENOTFOUND ac-eprzywu-lb.skhjo38.mongodb.net
[2025-10-23T23:49:43]
at connectionFailureError (/workspace/node_modules/mongodb/lib/cmap/connect.js:387:20)
[2025-10-23T23:49:43]
at TLSSocket.<anonymous> (/workspace/node_modules/mongodb/lib/cmap/connect.js:310:22)
[2025-10-23T23:49:43]
at Object.onceWrapper (node:events:633:26)
[2025-10-23T23:49:43]
at TLSSocket.emit (node:events:518:28)```

Maybe this was related to the AWS outage?
mild viper
#

Are you using payload cloud?

#

Might be quicker to email

wanton drift
#

Yes using payload cloud.
Who should I email? I tried support@payloadcms but no answer

prime sierra
#

Did you get any information for this issue from the payload team? We are getting the same problem and the backend of our website is not accessible - the same error message in the logs. We are also using payload cloud.

wanton drift
#

No answer at all 🙁
I've had to switch to a maintenance page and am scrambling to get my data into a self-hosted payloadcms (which I'm not familiar with at all)

wanton drift
#

@prime sierra the good thing is that both the MongoDB database and S3 files are all still accessible. It's just a matter of resurrecting them on a functioning PayloadCMS instance

prime sierra
#

@wanton drift I will send them an email as well. I am scared to redeploy the site to be honest - because the frontend loads for the moment - not sure because it is cached and don't want to find out 😃

wanton drift
#

@prime sierra my API is totally broken - it seems the token may have expired

mild viper
#

yeah that email sounds correct

coarse pelican
#

Hey All, we've had multiple users report this issue when using hosted providers for MongoDB. This appears to happen on MongoDB Atlas as well as DigitalOcean's MongoDB offering. It looks like something must have changed in the way it's being served and looks to be transaction/cluster related.

🔧 The workaround right now is to set transactionOptions: false on the mongooseAdapter's options in the payload config. We're looking into a longer-term fix right now.

coarse pelican
#

@wanton drift @prime sierra Calling attention to the above 👆

wanton drift
#

Thanks @coarse pelican for the update.. I'll try to set this but I can't change the repo in my payloadCMS settings

coarse pelican
#

@wanton drift This is in your payload.config.ts code

wanton drift
#

@coarse pelican thanks. I emailed you about the issue that I can't change my repo in the UI

wanton drift
#

@coarse pelican I should presumably set the mongooseadapter as :

db: mongooseAdapter({
    url: process.env.DATABASE_URI,
    transactionOptions: false, // Disable transactions
  }),
  // ... other Payload config

Is this correct?

coarse pelican
#

@wanton drift I was actually told my our infra provider to perform a reset on your instance in order to reset the DNS cache, and that appears to have worked for your project.

Can you take a look at the current state of your project?

wanton drift
#

hi @coarse pelican yes thanks, the Admin panel is now available, and so is the API. Thanks so much for the quick help with that!

#

Could you please also help me to change the repository?

prime sierra
#

@coarse pelican thank you so much. The admin section now works and I didn't need to do anything.