an hour ago
I can't deploy one of my production services because the MySQL service's actual root password no longer matches its root password variable. This started on 24 Oct 2026 and is still happening as of 3 Nov 2026. Railway Support told me by email that an engineer needs to reset it inside the container, but I haven't had an update since 25 Oct. I'd like someone from the team to pick up or escalate my existing email ticket. I can share the project details privately.
On 24 Oct I regenerated the MySQL password from the Database Config tab. I couldn't redeploy with the new password, so I set the password variable back to the old value. Since then the Database tab shows "Access denied" and deploys are blocked.
Support replied on 25 Oct saying Regenerate can't recover it and an engineer needs to work inside the container. I followed up on 28 Oct, 31 Oct and 3 Nov and haven't had a reply.
Please avoid any data loss. This post is not permission to delete or recreate the volume.
4 Replies
Status changed to Awaiting Railway Response Railway • about 1 hour ago
an hour ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 hour ago
an hour ago
Try this:
- Remember the current Custom Start Command
- Change the Custom Start Command to
docker-entrypoint.sh mysqld --skip-grant-tables --skip-networkingand redeploy - Go to the console tab of your MySQL service
- In the terminal, run
mysql -u root - Run the following commands:
ALTER USER 'root'@'localhost' IDENTIFIED BY '<PASSWD>';
ALTER USER 'root'@'%' IDENTIFIED BY '<PASSWD>';
FLUSH PRIVILEGES;Where <PASSWD> is replaced with the new password (From the variable MYSQL_ROOT_PASSWORD)
- Revert the custom start command and redeploy MySQL
- Make sure to restart other services that depend on your MySQL database
an hour ago
If there's even a slight risk of the deployment becoming stale because the password's still don't match, I don't want to risk it. It's in production and unfortunately I can't rely on 'try this'.
0x5b62656e5d
Try this: 1. Remember the current Custom Start Command 2. Change the Custom Start Command to `docker-entrypoint.sh mysqld --skip-grant-tables --skip-networking` and redeploy 3. Go to the console tab of your MySQL service 4. In the terminal, run `mysql -u root` 5. Run the following commands: ```sql ALTER USER 'root'@'localhost' IDENTIFIED BY '<PASSWD>'; ALTER USER 'root'@'%' IDENTIFIED BY '<PASSWD>'; FLUSH PRIVILEGES; ``` Where `<PASSWD>` is replaced with the new password (From the variable `MYSQL_ROOT_PASSWORD`) 6. Revert the custom start command and redeploy MySQL 7. Make sure to restart other services that depend on your MySQL database
an hour ago
If there's even a slight risk of the deployment becoming stale because the password's still don't match, I don't want to risk it. It's in production and unfortunately I can't rely on 'try this'.
an hour ago
I have tested that process and it's worked successfully for me and other users that have faced the same issue.
