Multiple attempts required to resolve kafka broker internal domain

2 years ago

Closed

26 Replies

2 years ago

b4d5b2fe-0269-4ddf-8196-c06381b56b14


2 years ago

does this happen every deploy?


2 years ago

ye


2 years ago

are you on metal?


2 years ago

1295508947712741396


2 years ago

try off metal


2 years ago


2 years ago

worked, ty


2 years ago

no problem, ill try to reproduce


2 years ago

kafka was on us east, my pod was on metal


2 years ago

how long ago was the "pod" service created?


2 years ago

(by pod I meant service)

44hr


2 years ago

@BillyDotWS - please remove "runtime": "UNSPECIFIED", from your railway.json file


2 years ago

hmm, what should it be? nothing?


2 years ago

I'm using the auto generated one


2 years ago

just outright remove it


2 years ago

👍


2 years ago

then after that, you can switch back to metal


2 years ago

if you also have that line in any other railway.json elsewhere, now is the time to remove that line too


2 years ago

1295523808328941608


2 years ago

<:kekw:788259314607325204> fun


2 years ago

now you can switch back to metal


2 years ago

i like the icons btw


2 years ago

very fruity


2 years ago

seems fine ya


2 years ago

yep looks like you are not on the correct runtime


Welcome!

Sign in to your Railway account to join the conversation.

Loading...