template neo4j
baobab-kernel
HOBBYOP

24 days ago

Hello,

I am experiencing an issue with one of my Railway services.

Context

Project: 74ddf14f-384e-431a-9822-a217784a4358

Neo4j service: d2b6d126-e771-49e7-99e1-61dbceb48ab0

Template used: Neo4J | Open Source Graph Database (or similar)

Issue

My backend crashes immediately with the following error:

Code

Error: Unknown scheme: null

at neo4j-driver/lib/index.js:204

This indicates that neo4j-driver is not receiving any valid URL in process.env.NEO4J_URI.

Observations

In the Neo4j service variables:

I see DB_PASSWORD, HEAP_*, NEO4J_PLUGINS, etc.

But no variable such as NEO4J_URI, BOLT_URL, NEO4J_USERNAME, etc.

The “13 variables added by Railway” only contain system-level variables (RAILWAY_PRIVATE_DOMAIN, RAILWAY_TCP_PROXY_DOMAIN, etc.)

The template exposes only a TCP proxy, but no Bolt URI usable by neo4j-driver.

Questions

Could you please clarify:

Whether this Neo4j template is supposed to generate a Bolt URI compatible with neo4j-driver

If yes, where this variable can be found (it does not appear in the UI)

If not, which official Neo4j template you recommend to obtain a working Bolt endpoint for a Node.js service on Railway

Whether the Railway TCP proxy is compatible with the Bolt protocol

Thank you in advance for your help.

I can provide additional logs if needed.

Best regards,

Philippe

Solved$10 Bounty

2 Replies

Railway
BOT

24 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway 24 days ago


Status changed to Solved baobab-kernel 24 days ago


baobab-kernel
HOBBYOP

24 days ago

j'ai résolu en ajoutant 'bolt' à la variable qui posait problème !


Status changed to Awaiting Railway Response Railway 24 days ago


24 days ago

Translation: I solved it by adding bolt to the variable that was causing the problem!


Status changed to Awaiting User Response Railway 24 days ago


Status changed to Open passos 24 days ago


Status changed to Solved passos 24 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...