Running weaviate is impossible on Railway

9 months 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

9 months ago

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


9 months ago

Can you say more?


9 months 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


9 months ago

Let me understand

Install Cloudflare tunnel (cloudflared) in railway service


9 months ago

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


9 months ago

You can find instructions to setup a Cloudflare tunnel here -


9 months ago

nice thanks for the pointers


9 months ago

actually looks like a LB in some sense


9 months ago

Will need to also host DNS then there


9 months ago

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


9 months ago

Cloudflare does have a pretty good nameserver after all


9 months ago

!s


Status changed to Solved brody 9 months ago


Loading...