i have been going through same thingwhat i noticed is when im adding https://primary-production-fbc5.up.railway.app/rest/oauth2-credential/callback its not workingbut when i remove my subdomain and just keep https://railway.app/rest/oauth2-credential/callback its workingi think its the subdomain isuue

The Problem: A PostgreSQL DowngradeThe key error is this one:"The data directory was initialized by PostgreSQL version 17, which is not compatible with this version 16.10"This means your database files (which are safe on the persistent volume) were created by PostgreSQL 17. When you clicked "update," Railway tried to deploy the latest stable version of its PostgreSQL template, which is 16.10.The Recovery Plan: Forcing PostgreSQL 17We can fix this by telling Railway to use the correct PostgreSQL 17 engine for your existing data. We will convert your PostgreSQL service from a managed template to a custom Docker image.1. Go to Your Broken PostgreSQL ServiceNavigate to your old project on Railway and click on the PostgreSQL service that is crashing.2. Change the Service SourceGo to the "Settings" tab of the PostgreSQL service.In the "Service" section, look for an option to "Change Source" or "Detach from Template."Choose to deploy from a Docker Image.3. Specify the Correct Docker ImageIn the "Image Name" field that appears, enter the correct version exactly: postgres:17Click "Update" or "Deploy."4. Verify Your SettingsAfter changing the source, quickly double-check two things:Variables: Make sure all your original database environment variables (POSTGRES_USER, POSTGRES_DB, POSTGRES_PASSWORD) are still there.Volumes: Make sure your persistent volume is still attached with the correct mount path (usually /var/lib/postgresql/data).5. Redeploy All ServicesOnce you've set the PostgreSQL image to postgres:17, trigger a manual redeploy of your n8n primary and worker services. This will force them to try and reconnect.Because the database will now be running the correct version (17), it will be able to read its data and start up successfully. This will allow your n8n services to connect, and you should regain access to your instance.Once You Regain AccessThe first thing you should do is export your important workflow as a JSON file and save it to your computer. You can then import this file into your new, clean project to be safe.