Hey,

Does anyone know if AWS SES being blocked at at the network level is a known limitation of Railway?

See below for my debug trace.

Best
Matt

[Better Auth POST] Request received: https://0.0.0.0:8080/api/auth/sign-in/magic-link

[Better Auth POST] Request body: {"email":"<redacted>","callbackURL":"/"}

[Network Debug] DNS resolved to IPs: [ '52.31.197.18' ]

[Network Debug] Testing HTTPS connection to: email.eu-west-1.amazonaws.com

[Network Debug] Socket assigned

[Network Debug] Socket DNS resolved to: 52.31.197.18

[Better Auth] sendMagicLink called for: <redacted>

[Better Auth] Magic link URL: https://<redacted>/api/auth/magic-link/verify?token=<redacted>

[SES] Starting sendMagicLinkEmail for: <redacted>

[SES] Sender address: "<redacted>" <noreply@<redacted>>

[SES] Creating SendEmailCommand

[SES] Sending email via SES...

[Network Debug] Diagnostics complete

[Network Debug] Request timeout after 5000ms

[Network Debug] HTTPS connection failed after 5029 ms

[Network Debug] Error: socket hang up

[Network Debug] Error code: ECONNRESET

@smithy/node-http-handler - [WARN] a request has exceeded the configured 10000 ms requestTimeout. Init client requestHandler with throwOnRequestTimeout=true to turn this into an error.

@smithy/node-http-handler - [WARN] a request has exceeded the configured 10000 ms requestTimeout. Init client requestHandler with throwOnRequestTimeout=true to turn this into an error.

code: 'ETIMEDOUT',

syscall: 'connect',

address: '34.252.104.46',

port: 443,

at async handler (/app/.next/server/app/api/auth/[...all]/route.js:53:3239)

name: 'TimeoutError',

at async n (/app/.next/server/app/api/auth/[...all]/route.js:53:2818)

at async gi (/app/.next/server/app/api/auth/[...all]/route.js:249:25353)

'$metadata': { attempts: 2, totalRetryDelay: 69 }

at async handler (/app/.next/server/app/api/auth/[...all]/route.js:53:3239)

}