Hello Railway Support,

We are unable to configure backups and Point-In-Time Recovery for a dedicated staging PostgreSQL service.

Project details:

• Project: mindujo-tessera-oro-demo
• Project ID: acd48cdb-67e6-472b-b62f-0cf872a52b8f
• Environment: staging-v1
• Environment ID: 8cfe2fab-7f43-44d1-9337-30090ee43f97
• Service: Postgres
• Service ID: 1087b9cf-e7b5-408d-baf3-309cb91c6c39
• Volume ID: 8c88b1fe-85a0-424d-8bbc-54cc197ccad2
• PostgreSQL version: 18.4
• Railway plan: Hobby
• Authenticated workspace role: Workspace Owner / ADMIN

Problem:

The PostgreSQL service and its private volume are operational. The deployment status is successful and the database is reachable through Railway’s private network.

However, the service’s Backups page loads only the Railway navigation and service menu. The backup controls and the Enable PITR option never appear.

Affected page:

Project → staging-v1 → Postgres → Backups

A backup-schedule operation through Railway’s API also returns:

Not Authorized

Expected behavior:

• The Backups page should display the controls for configuring scheduled backups.
• The PITR activation control should be available when supported by the current plan and service.
• If the feature is unavailable, the UI should show the specific plan, permission or configuration requirement.

Observed behavior:

• The page finishes loading but its main content remains empty.
• No backup schedule controls are displayed.
• No PITR activation control is displayed.
• No upgrade, permission or configuration warning is shown.
• The API returns Not Authorized, although the authenticated user is Workspace Owner / ADMIN.

The issue is limited to Backup/PITR management. The PostgreSQL service, deployment, private networking and volume are operational.

Could you please verify the project-side authorization and feature entitlement for Backup and PITR, and restore access or tell us the exact required action?

No Production environment or customer data is involved.

This issue is currently blocking our staging qualification and therefore the release path of the application.

Thank you.