@Phineas - IIRC we have something in fastly that has something to do with that path?

we do one second

cc @aris_byteg who is also having this issue

is this fixed now @therobotcarlson ?

great

sorry about that

This exact issue is resolved, yes. now hitting new ones. Will come back if they seem related

Feels related -- getting blocked gRPC-over-HTTP/2 calls

what errors are you seeing?

Hopefully not speculation:

Error [ConnectError]: [internal] protocol error: missing status
    at w (.next/server/chunks/5531.js:1:2754)
    at next (.next/server/chunks/5531.js:1:38845)
    at async Object.unary (.next/server/chunks/5531.js:1:37577)
    at async Object.i [as listSessions] (.next/server/chunks/5531.js:9:17830)
    at async T (.next/server/app/login/route.js:13:290)
    at async U (.next/server/app/login/route.js:13:859)
    at async k (.next/server/app/login/route.js:13:3811) {
  rawMessage: 'protocol error: missing status',
  code: 13,
  metadata: Headers {},
  details: [],
  cause: undefined
}

Trying to reset everything to what I had before I started changing things to fix the original issue here.

Okay, please let us know!

Okay, fairly confident this is a railway networking issue. I ran some diagnostics to see.

Is this related to 'well-known'? If not, please open a new thread.