a year ago
I am importing small sql dump (10 Mb) and have different variations of exported dumps. No of them work or give a mistake. It ends up in infinite waiting or "Wasn't able to load progress of import". Seems nobody reported about this problem except of me. I also tried other dumps, no luck.
4 Replies
a year ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 Internal Server Error Multiple Arguments Fed to Application
- 🧵 Angular 19 SSR Failed to load module script bug
- 🧵 Regular Deployment Crashing
If you find the answer from one of these, please let us know by solving the thread!
a year ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • about 1 year ago
a year ago
More context:
I deployed "PhpMyAdmin" template on railway, and used it's import functionality.
a year ago
phpMyAdmin SQL Import Hanging on Railway – Explanation and Fixes
phpMyAdmin gets stuck on Railway when importing a SQL dump of around 10 MB. The UI shows infinite loading or the message "Wasn't able to load progress of import". The reasons are below.
Why It Happens
- PHP upload limits are too low.
Default Railway phpMyAdmin environment uses:
"upload_max_filesize = 2M"
"post_max_size = 8M"
Files above 2 MB are rejected internally. The result is a frozen import page or a silent failure.
- phpMyAdmin on Railway does not include the uploadprogress extension.
Without this extension, phpMyAdmin cannot update the import progress. The UI often remains stuck at 0% even when the upload is rejected.
Because of these limits, a 10 MB SQL file almost always fails in the phpMyAdmin interface.
Working Solutions
- Increase PHP upload limits (only if you deploy phpMyAdmin yourself).
Example nixpacks.toml:
"[variables]"
"UPLOAD_MAX_FILESIZE = '20M'"
"POST_MAX_SIZE = '20M'"
If you use Nginx, also update "client_max_body_size".
This increases allowed upload size, but the progress bar will still not work without the uploadprogress extension.
- Compress the SQL file.
Use zip or gzip to reduce the size below 2 MB. phpMyAdmin accepts ".zip" and ".gz" files and extracts them automatically.
This bypasses the PHP upload limit.
- Import using MySQL CLI (recommended and most reliable).
Railway provides:
"MYSQLHOST"
"MYSQLPORT"
"MYSQLUSER"
"MYSQLPASSWORD"
"MYSQLDATABASE"
Import with:
"mysql -h $MYSQLHOST -P $MYSQLPORT -u $MYSQLUSER -p$MYSQLPASSWORD $MYSQLDATABASE < dump.sql"
You can run this on your local machine or from inside the service using:
"railway run bash"
This avoids phpMyAdmin entirely and works for any file size.
- Split the SQL dump.
Split the dump into smaller files and upload them one by one through phpMyAdmin. This is only a fallback solution.
Summary
The phpMyAdmin import hangs because:
- PHP upload_max_filesize is limited to 2 MB.
- The uploadprogress extension is missing.
Compression or raising upload limits can help, but the MySQL CLI import is the most reliable method and works consistently on Railway.
a month ago
For a template deployed from a Docker image, the important missing detail is which image it uses. A nixpacks.toml change will not configure PHP inside a prebuilt phpMyAdmin image.
If your service uses the official phpmyadmin image, its documented setting is UPLOAD_LIMIT, not UPLOAD_MAX_FILESIZE or POST_MAX_SIZE. First check the maximum upload size shown on the Import page. If it is below your 10 MB dump, set UPLOAD_LIMIT=32M in the phpMyAdmin service's Variables, review and deploy that configuration change, then confirm the displayed limit changed. This changes both PHP upload and POST limits. If the existing limit already exceeds the dump size, don't assume raising it will fix the problem. It does not require restarting the MySQL service. If the template uses another image, check that image's configuration instead; these variable names aren't universal. Official Docker settings.
A progress-display failure alone does not establish that a dump is invalid or that nothing was imported. Check the original import request in your browser's Network panel and the phpMyAdmin service logs at the same timestamp. A 413, a PHP memory/time-limit error, and a SQL error need different fixes. The phpMyAdmin FAQ lists the relevant limits and supports direct MySQL imports as a fallback. Don't blindly repeat the import into a populated database: a previous attempt may have partly completed.
One correction to the CLI workaround above: railway run bash runs locally, with Railway variables injected; it does not open a shell inside the deployed service. Railway documentation. For a local import, if the database already has an approved public TCP endpoint, use that proxy's host and port from Connect, rather than a *.railway.internal hostname. If no such endpoint exists, the command below is not ready to use; don't expose a private database solely to copy this example. TCP proxy documentation.
With a compatible MySQL client installed, this Bash/Command Prompt example prompts for the password instead of putting it in shell history:
mysql --host=PUBLIC_PROXY_HOST --port=PUBLIC_PROXY_PORT --user=DATABASE_USER --password DATABASE_NAME < dump.sqlAdd the TLS options required by your database's connection instructions; don't disable existing TLS verification. This executes the SQL in the dump, so verify the target and backup first, and review any USE, CREATE DATABASE, or destructive statements in the file. Prefer an empty intended target for the initial import. MySQL's file-import documentation.
Could you share only the phpMyAdmin image name/tag, displayed upload limit, and redacted error/status from the failing request? No database dump, password, cookies, or full connection string is needed.
AI-assisted answer, checked against the linked official documentation. I haven't accessed or tested your deployment.