22 days ago
hello,
My site has been in Production for a while. Jan 20 10 am Indian Standrard Time, i started getting this error:
code: 'ERR_TLS_CERT_ALTNAME_INVALID',
reason: "Host: api-production-94db.up.railway.app. is not in the cert's altnames: DNS:fallback.tls.fastly.net",
host: 'api-production-94db.up.railway.app',
cert: {
subject: [Object: null prototype],
issuer: [Object: null prototype],
subjectaltname: 'DNS:fallback.tls.fastly.net',
infoAccess: [Object: null prototype],
ca: false,
modulus: 'E45803FC264C809EE39907BD9A6328D2AC171865A5DCE819BB7E2A8A0BC273560F8DEA3A6D352318D9FD762A15D094E4E6773195DD7F29E236640E4E303338CE23C44E8682802B018E091C97294CEA36D7EF4FAC385C25F893B3A593BF0AB849F866B94BE10D7CB430C6740F54245C7116DD07B0195722C95C7872A62E5F5074CA20A3F018606C446266BC46A99EC52D76EC7F95933EC25659AFD51EB29F02CC4296F78C5C7CE6595B6BE7AE6AF2804D4A59445998ED9E7802811874D796FE44653E699CBE360F4549F368DE18450622D2B4F98E37C7E1BA6C38F1622A84D8C545E8985DBCDD1A291B48BE082F9A41323902FB2CBA4C7D2CC652F8DE0093D407',
bits: 2048,
exponent: '0x10001',
pubkey: <Buffer 30 82 01 22 30 0d 06 09 2a 86 48 86 f7 0d 01 01 01 05 00 03 82 01 0f 00 30 82 01 0a 02 82 01 01 00 e4 58 03 fc 26 4c 80 9e e3 99 07 bd 9a 63 28 d2 ac ... 244 more bytes>,
valid_from: 'Feb 11 11:28:05 2026 GMT',
valid_to: 'Mar 13 11:28:04 2026 GMT',
fingerprint: '27:22:24:99:F4:97:04:AD:0F:82:29:EA:D5:4B:67:BF:F9:25:D6:EB',
fingerprint256: '4F:71:70:E5:4B:F1:76:0D:E3:5E:4B:0F:0D:FF:07:05:0D:12:B1:23:E8:D8:A0:2C:1F:88:6C:B2:9D:FA:AF:39',
fingerprint512: '3E:A7:13:84:D3:3E:07:11:09:C7:62:11:3A:F7:C0:6D:75:D0:FB:95:5D:B4:76:18:1A:6F:0C:AA:E1:7E:BB:24:92:09:7B:88:F8:3B:47:7A:29:4E:CE:35:52:71:2D:B0:34:83:02:32:56:B7:27:33:8C:DF:09:36:24:67:9E:15',
ext_key_usage: [Array],
serialNumber: '787FAFF88AF6E6568F90354CCFE8E8F923D9',
raw: <Buffer 30 82 05 2b 30 82 04 13 a0 03 02 01 02 02 12 78 7f af f8 8a f6 e6 56 8f 90 35 4c cf e8 e8 f9 23 d9 30 0d 06 09 2a 86 48 86 f7 0d 01 01 0b 05 00 30 45 ... 1277 more bytes>,
issuerCertificate: [Object]
}
}
}
Now I am getting these errors:
[api-error] cid=4d063ee6-a9ee-40dc-beba-77c129e76405 sid=ce4246c6-a883-4855-b398-92cd1d5b64d9 s3=n/a time=Feb 20 2026 11:20:12 status=500 path=POST /api/public/photo-upload?token=2af5a6c7-e62f-4df7-ae43-0c55280b87be Error [TimeoutError]: @smithy/node-http-handler - the request socket did not establish a connection with the server within the configured timeout of 5000 ms.
at Timeout._onTimeout (/app/node_modules/@smithy/node-http-handler/dist-cjs/index.js:34:34)
at listOnTimeout (node:internal/timers:581:17)
at process.processTimers (node:internal/timers:519:7) {
'$metadata': { attempts: 3, totalRetryDelay: 215 }
}
Pinned Solution
22 days ago
So sorry for the interruption. Can you try again?
By way of background series of cascading issues hit us over the past few weeks: GitHub API rate limits backing up webhooks, build queues spiking, a false positive in our abuse detection system, and hostile traffic impacting our shared proxy layer. Part of our resolution including putting Fastly in place as a CDN but some people saw errors like you did initially. We think we've resolved this but please let us know if you still have a problem.
Again, sincere apologies.
8 Replies
22 days ago
Hello
This is my Prod env that is down. UAT is fine. NO CHANGES in lat 4 days.
Any chance i can get help soon?
22 days ago
So sorry for the interruption. Can you try again?
By way of background series of cascading issues hit us over the past few weeks: GitHub API rate limits backing up webhooks, build queues spiking, a false positive in our abuse detection system, and hostile traffic impacting our shared proxy layer. Part of our resolution including putting Fastly in place as a CDN but some people saw errors like you did initially. We think we've resolved this but please let us know if you still have a problem.
Again, sincere apologies.
Status changed to Awaiting User Response Railway • 22 days ago
22 days ago
Still getting this error:
[api-error] cid=5d521ff905fc6f1aecb4c271 sid=n/a s3=n/a time=Feb 21 2026 03:00:42 status=500 path=GET /entities/9704bcaf-052b-4912-a2d0-2954e269ae2f/persons/export-zip/2d193bf2-6ff5-4385-a38c-ebffa0ba0973/download?markPrinted=false Error [TimeoutError]: @smithy/node-http-handler - the request socket did not establish a connection with the server within the configured timeout of 5000 ms.
at Timeout._onTimeout (/app/node_modules/@smithy/node-http-handler/dist-cjs/index.js:34:34)
at listOnTimeout (node:internal/timers:581:17)
at process.processTimers (node:internal/timers:519:7) {
'$metadata': { attempts: 3, totalRetryDelay: 251 }
}
Status changed to Awaiting Railway Response Railway • 22 days ago
22 days ago
Do i need to restart something?
22 days ago
The domain and the correct certificate load correctly for me. Please make sure to clear your cache and try again.
Status changed to Awaiting User Response Railway • 22 days ago
22 days ago
Please make sure to clear your cache and try again.
>> Browser cache?
I went to a new page that should not have anything to do with browser cache
Status changed to Awaiting Railway Response Railway • 22 days ago
22 days ago
I think i am having S3 issue. Maybe this is a different issue. I cannot write to S3.
[api-error] cid=8ab0d072-bdf3-4a63-8105-d8600dfd69e3 sid=627481d7-68cc-474d-a422-9d9a326cad1a s3=n/a time=Feb 21 2026 03:12:20 status=500 path=POST /api/public/photo-upload?token=8ec5d6f1-cb8d-4686-99dd-50a9ebf14f97 Error [TimeoutError]: @smithy/node-http-handler - the request socket did not establish a connection with the server within the configured timeout of 5000 ms.
at Timeout._onTimeout (/app/node_modules/@smithy/node-http-handler/dist-cjs/index.js:34:34)
at listOnTimeout (node:internal/timers:581:17)
at process.processTimers (node:internal/timers:519:7) {
'$metadata': { attempts: 3, totalRetryDelay: 235 }
}
Log Explorer
0.5
22 days ago
I restart the api and the S3 connection is working. thx for your help.
Status changed to Solved brody • 22 days ago