3 hours ago
We have an existing, stopped QA service on Hobby and need to verify a running instance independently before enabling synthetic-customer proof routes. We are not asking to deploy, add billing, upgrade or create resources in this support inquiry.
The dashboard's Console tab is blank while the QA service is offline. Our CLI is version5.71.0. Its file-transfer implementation uses SSH and accepts a new server key on first use; we need an independently authenticated server-identity check rather than first-use trust.
Please have a HUMAN confirm whether there is a supported authenticated HTTPS console/exec method tied to an explicitly selected existing project/environment/service/deployment instance, capable of running a fixed read-only Node inspection of runtime IDs, package-file hashes and volume filesystem identity. Does that method work on Hobby, and what minimum permissions/access grant does it need? Does the Console panel become available only after a running deployment, or is a blank panel an unsupported/unavailable feature on this plan?
An existing RailwayBOT support reply says no stable published SSH key or pinning procedure is provided. We are not asking the bot to repeat that answer or asking to bypass host verification. If HTTPS console/exec is not supported, please identify a vendor-supported independently authenticated operator-access procedure, if one exists, and explain its permissions and verification boundary.
Also confirm whether a new private Hobby volume defaults to5GB and whether previewing/selecting its service stages a deploy or provisions immediately. We intend to stop before any cloud write until exact resource/cost/access approvals are obtained.
Please do not start/redeploy services, provision volumes, enable agents, change billing or alter permissions in response. We can supply the exact QA target identifiers privately if needed. No credentials, artwork, customer data, source bundle or account token is included in this inquiry.
1 Replies
Status changed to Awaiting Railway Response Railway • about 2 hours ago
an hour ago
The supported way to run a command inside a specific instance is railway ssh, which connects to ssh.railway.com and accepts explicit --project, --environment, --service and --deployment-instance targets, so a fixed read-only command such as railway ssh -s <service> -e <environment> -d <instance-id> -- node inspect.js runs against exactly that instance. Access requires an SSH key registered to your Railway account, or a workspace key, which only a workspace Admin can add, and project tokens cannot manage SSH keys, so use railway login or a workspace API token.
We have not verified an HTTPS exec alternative, a published host-key fingerprint for ssh.railway.com, or whether the blank Console tab on your stopped service reflects the service being offline, so we cannot confirm any of those here. The authenticated parts of the SSH flow we can confirm are your own registered key and your Railway login.
New Hobby volumes default to 5 GB. We have not verified whether selecting a service when adding a volume provisions it immediately or stages it for the next deploy.
Status changed to Awaiting User Response Railway • about 1 hour ago