Running weaviate is impossible on Railway

a year ago

There are dozens of other posts on here complaining about running both HTTP and GRPC ports which services like Weaviate require.

Are there any workarounds to exposing multiple ports

8c3e6c5c-f000-4937-b55e-e8991ced5da1 Project ID

Ideally one can just run a router or gateway service that has two or more public domains setup and then forwarded to the respective exposed ports

e.g.

service-a.railway.app = 443 -> 8080 HTTP Rest API

service-b.railway.app = 443 -> 5050 gRPC

IF theere isn't a workround we'll need to migrate elsewhere

Solved

12 Replies

a year ago

I have heard of users having success with a Cloudflare tunnel for HTTP2


a year ago

Can you say more?


a year ago

Looking into Weaviate cloud they expose both a public URL for HTTP and one for GRPC like this

kdj9yftes4gt5hlru7qq.c0.us-west3.gcp.weaviate.cloud


a year ago

Let me understand

Install Cloudflare tunnel (cloudflared) in railway service


a year ago

Configure it for tunnels for both ports and then point Railway DNS to that tunnel?


a year ago

You can find instructions to setup a Cloudflare tunnel here -


a year ago

nice thanks for the pointers


a year ago

actually looks like a LB in some sense


a year ago

Will need to also host DNS then there


a year ago

not a problem was planning on moving the primary domain theer or some of the app domains


a year ago

Cloudflare does have a pretty good nameserver after all


a year ago

!s


Status changed to Solved brody 12 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...