Failing requests due to stale certificates (Host is not in the cert's altnames)

esya
PROOP

25 days ago

Error [TRPCClientError]: fetch failed     at a.from (.next/server/chunks/8115.js:1:74674)     at <unknown> (.next/server/chunks/8115.js:1:80160) {   shape: undefined,   data: undefined,   meta: undefined,   digest: '3366230372',   [cause]: TypeError: fetch failed       at async E (.next/server/chunks/8115.js:1:76519)       at async Object.fetch (.next/server/chunks/8115.js:1:78934) {     [cause]: Error: Hostname/IP does not match certificate's altnames: Host: api.cardnexus.com. is not in the cert's altnames: DNS:*.up.railway.app         at oe.TLSSocket._finishInit (../../../../opt/rust/nodejs.js:16:11962) {       code: 'ERR_TLS_CERT_ALTNAME_INVALID',       reason: "Host: api.cardnexus.com. is not in the cert's altnames: DNS:*.up.railway.app",

Our frontend is suddenly having issues reaching our API due to Railway serving incorrect/stale certificates

Solved

2 Replies

Railway
BOT

25 days ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!

brody
EMPLOYEE

25 days ago

I am not seeing any SSL errors when connecting to that service. Perhaps there is some stale certificate cache on your end.

Status changed to Awaiting User Response Railway • 25 days ago

Railway
BOT

11 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 11 days ago

Failing requests due to stale certificates (Host is not in the cert's altnames) - Railway Help Station