Kafka Connect (Debezium) 503 Error on Railway
Anonymous
HOBBYOP

23 days ago

I'm trying to use Kafka Connect to stream PostgreSQL database updates via Debezium into Elasticsearch.

I'm using the Kafka template on Railway, which includes:

  • Kafka

  • Zookeeper

  • KRaft UI

I published a public Docker image to GHCR for Kafka Connect using:

debezium/connect:2.3

The service exposes port 8083.

For BOOTSTRAP_SERVERS, I'm using the internal Kafka domain provided by Railway.

However, when I try to create a connector by sending a POST request to /connectors, I always receive a 503 Service Unavailable error.

I’d like to confirm:

  • Is this setup supported on Railway?

  • If so, what might be wrong in my configuration?

Thank you.

$10 Bounty

3 Replies

Does this only happen on /connectors or all routes?


0x5b62656e5d

Does this only happen on /connectors or all routes?

Anonymous
HOBBYOP

22 days ago

Happens on all route


If your current URL is mapped to port 8083, I'd suggest setting a different port for your application to listen to, then changing the port the URL is mapped to, and see what happens from there.


Loading...