We are seeing a public WebSocket upgrade failure for a Laravel Reverb service while the service itself is healthy. Environment - Project: boostly - Environment: staging - Service: reverb - Custom domain: reverb.boostly.hr - Deployment status: SUCCESS with one RUNNING instance - Runtime command: php artisan reverb:start --host=0.0.0.0 --port= - Runtime PORT: 8080 - Listener: 0.0.0.0:8080 - Railway domain metadata shows the custom domain attached to the Reverb service and no separate target-port override (targetPort is null). Observed evidence - DNS resolution, TCP connection and TLS 1.3 certificate verification pass both locally and from the existing Railway Web runtime. - Six allowlisted non-secret Reverb coordinates are byte-identical between Web and Reverb. - A container-local WebSocket Upgrade with the approved Origin returns HTTP 101. - A bounded public WSS/Pusher v7 handshake to reverb.boostly.hr passes TLS but does not receive HTTP 101 and times out after approximately 15 seconds. - A separate earlier bounded probe also timed out after approximately 5 seconds. - No event was published, no channel was subscribed to, no app secret was read, and no data or configuration change was made. - Reverb runtime and network-flow logs contained no request for the probe interval; the Railway HTTP-log query returned "Problem processing request". Classification edge_upgrade_failed: listener, bind address, injected port, local Upgrade, service association, DNS and TLS are verified. The remaining observed boundary is the public Railway edge-to-service HTTP/1.1 WebSocket Upgrade. Could Railway inspect the edge/upstream routing for this custom domain/service and confirm whether HTTP/1.1 Upgrade is reaching the Reverb instance? Please advise before we change any domain or service configuration. Exact Railway identifiers and probe timestamps are intentionally omitted because private threads may be converted to public bounties. We can provide them after a Railway agent confirms a secure private channel.

Public WSS upgrade fails at Railway edge while container-local upgrade returns HTTP 101

jlipovac014

PROOP

a month ago

We are seeing a public WebSocket upgrade failure for a Laravel Reverb service while the service itself is healthy.

Environment

Project: boostly
Environment: staging
Service: reverb
Custom domain: reverb.boostly.hr
Deployment status: SUCCESS with one RUNNING instance
Runtime command: php artisan reverb:start --host=0.0.0.0 --port=
Runtime PORT: 8080
Listener: 0.0.0.0:8080
Railway domain metadata shows the custom domain attached to the Reverb service and no separate target-port override (targetPort is null).

Observed evidence

DNS resolution, TCP connection and TLS 1.3 certificate verification pass both locally and from the existing Railway Web runtime.
Six allowlisted non-secret Reverb coordinates are byte-identical between Web and Reverb.
A container-local WebSocket Upgrade with the approved Origin returns HTTP 101.
A bounded public WSS/Pusher v7 handshake to reverb.boostly.hr passes TLS but does not receive HTTP 101 and times out after approximately 15 seconds.
A separate earlier bounded probe also timed out after approximately 5 seconds.
No event was published, no channel was subscribed to, no app secret was read, and no data or configuration change was made.
Reverb runtime and network-flow logs contained no request for the probe interval; the Railway HTTP-log query returned "Problem processing request".

Classification

edge_upgrade_failed: listener, bind address, injected port, local Upgrade, service association, DNS and TLS are verified. The remaining observed boundary is the public Railway edge-to-service HTTP/1.1 WebSocket Upgrade.

Could Railway inspect the edge/upstream routing for this custom domain/service and confirm whether HTTP/1.1 Upgrade is reaching the Reverb instance? Please advise before we change any domain or service configuration.

Exact Railway identifiers and probe timestamps are intentionally omitted because private threads may be converted to public bounties. We can provide them after a Railway agent confirms a secure private channel.

Solved$20 Bounty

3 Replies

Railway

BOT

a month ago

We've looked into this from our side and haven't found anything on the Railway platform that explains what you're seeing, so working it out means digging into your specific setup.

That's exactly what the Railway community is good at, so we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who solves it, and threads like this usually get picked up quickly.

Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.

Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
Keep it private and close the thread - Nothing becomes public and the thread closes.

Status changed to Awaiting User Response Railway • about 1 month ago

Railway

We've looked into this from our side and haven't found anything on the Railway platform that explains what you're seeing, so working it out means digging into your specific setup. That's exactly what the Railway community is good at, so we'd like to open your thread as a community [bounty](https://docs.railway.com/community/bounties). Railway pays a bounty to the community member who solves it, and threads like this usually get picked up quickly. **Opening it makes this entire thread public**, including everything already posted. Nothing becomes public until you decide. Use the buttons below. - **Open to the community** - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away. - **Keep it private and close the thread** - Nothing becomes public and the thread closes.

jlipovac014

PROOP

a month ago

I ask for human employee help then, thnak you

Status changed to Awaiting Railway Response Railway • about 1 month ago

Railway

BOT

a month ago

This still looks like an application-level problem, so Railway support can't take it further, but the community can. The buttons below are still live: open the thread up as a public bounty after editing out anything sensitive, or keep it private and close it.

Status changed to Awaiting User Response Railway • about 1 month ago

Railway

BOT

a month ago

This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.

Status changed to Open Railway • about 1 month ago

Status changed to Solved jlipovac014 • about 1 month ago

Welcome!