Repository navigation
Hosted sharing still fails: default signaling server wss://y-webrtc-eu.fly.dev is offline #7
Description
Activity
Starting work on this issue /glorp:45E62B60
No fix implemented yet: this issue needs a production signaling server deployed first, and that's an infrastructure choice an agent shouldn't make on its own.
What I checked (2026-10-03)
wss://y-webrtc-eu.fly.devstill doesn't respond. The hosted bundle (/assets/subscript-write-15323ff1.js) still has it baked in as the only signaling URL, so the hosted page doesn't override it.- None of the other public y-webrtc relays work either:
signaling.yjs.devdoesn't resolve, and the twoy-webrtc-signaling-{eu,us}.herokuapp.comrelays return 404. Switching to another third-party relay isn't an option. subscript-write-signalingisn't deployed on the Cloudflare account this agent can reach (Loren's personal account,1815342e…). Thesubscript-writeapp worker isn't there either, so write.subscript.to is served from somewhere else.
Why I stopped
To meet the acceptance criteria, the defaultsignalingUrlhas to point at a real deployed endpoint. Deployingsignaling/to an account that doesn't host write.subscript.to, then hard-coding that*.workers.devURL as every user's default, would be a long-lived production decision. A person needs to make that call. I opened no PR and changed nothing in the repo.Manual verification
CI can't cover these steps:- Deploy the signaling worker to the Cloudflare account that serves write.subscript.to:
pnpm deploy:signaling, optionally adding a custom domain such assignal.subscript.to. - Check that
https://<deployed-host>/returns "Subscript Write signaling worker is running". - Comment the final
wss://URL here (@/glorp:45E62B60works).
Once that URL is posted, a rerun can make it the default in
config.ts,app/.env.example,signaling/README.mdand the root README, and remove every reference towss://y-webrtc-eu.fly.dev. Someone then still needs to confirm that two browsers on the same Share Draft link on write.subscript.to show "2 in room" and sync edits both ways.@/glorp:45E62B60 find another public signaling server
- added 2 commits that reference this issue
on Oct 3, 2026
Sharing on https://write.subscript.to still can't connect peers after #3, because the signaling server it uses is offline.
Details
app/src/lib/config.tsdefaultssignalingUrltowss://y-webrtc-eu.fly.dev, and the hosted page's<subscript-write>element sets nosignaling-url, so production uses that default.wss://y-webrtc-eu.fly.devno longer responds. The hostname resolves, but HTTPS and WebSocket connections time out (checked 2026-10-03), so browsers opening a Share Draft link never find each other.app/.env.exampleandsignaling/README.md("Write works out of the box without deploying anything") still describe that relay as a working default.signaling/worker underwrangler dev), two browsers connect and sync edits both ways, as verified in Fix typed text never reaching shared drafts #3.Acceptance criteria
signaling-url, points at a reachable signaling server, for example a deployedsignaling/worker (pnpm deploy:signaling).config.ts,app/.env.example,signaling/README.md, and the root README no longer referencewss://y-webrtc-eu.fly.devas a working default.Addresses #1 and #3