The installer stops at the database step
What to do when the web installer shows "Installation stopped", says the database already has tables or doesn't exist, or the command-line installer fails.
- Applies to
- Core 12.0 and later
- Who can do this
- Platform owner, Developer
On this page
Symptom
On the Database step of the web installer, you select Test connection and install and one of these appears:
- That database already has tables in it
- That database does not exist yet
- Installation stopped, with "Stopped at step …"
- The run fails with HTTP 0, or times out.
From the command line, php artisan app:install ends with The database already contains tables. or Could not connect to the database.
Check these, in order
1. The database isn't empty
Laramin refuses to install over an existing schema, because it can't tell your data from a previous attempt's. The message names the database and how many tables it holds.
Fix: choose one of the options on screen:
- Use a different database: go back and enter the name of an empty one.
- Empty this one and retry: type the database name to confirm, then select Drop and retry. This drops all its tables and can't be undone.
- Reinstall from the command line: run
php artisan app:install --fresh. This also drops everything. It needs shell access.
Danger: Only drop the tables if you are sure the database belongs to this installation. Dropping them deletes everything in it.
2. The database doesn't exist yet
The server accepted your username and password, but there is no database with that name.
Fix: under Create it for me, select Create the database. If your MySQL user isn't allowed to create databases, use Create it yourself: run the statement shown in phpMyAdmin, Adminer or a MySQL shell, then select Back and continue.
3. The run stopped part-way
Installation stopped tells you which step failed:
- "Nothing was changed — not your database, not .env." Fix the cause in the error message and run the step again.
- "Some tables were already created, so the database is now partly built". Drop the leftover tables with Empty this one and retry before you try again. Your
.envwas not touched.
Fix: to see the full error, open storage/ on the server. Every install run writes each command, its exit code and its output there.
4. You closed the tab or the request was cut off
Each step is requested from your browser, so closing the tab stops the run.
If you run the app with php artisan serve, the development server restarts whenever .env changes, and the step fails with HTTP 0.
Fix: keep the tab open until the run finishes. With php artisan serve, start it with php artisan serve --no-reload, or install with php artisan app:install instead.
5. The install times out on shared hosting
Fix: raise max_ and memory_limit in your PHP settings. If you have SSH access, install from the command line instead.
6. The command-line installer can't connect
app:install checks that DB_CONNECTION, DB_HOST, DB_PORT, DB_DATABASE and DB_USERNAME are set in .env, and that the connection works, before it changes anything.
Fix: correct the values in .env, then run the command again.
Still not working?
The app isn't installed yet, so you can't use Support Center. Have your purchase code ready, and include this page's link, what you checked, and the relevant lines from storage/. The log contains no credentials.
Module: Contact Brine Webs support: [support contact]. Include your workspace address and what you see on screen. If you can still sign in, raise a ticket from Support Center in your Laramin app instead.
Thanks. That helps us decide what to write next.
Thanks for telling us what was missing.
You already answered for this article today. Thanks.
We got a lot of answers from your network just now. Try again in a few minutes.
We couldn't send that. Check your connection and try again.
Links in this article
Printed from help.bsscn.com. The online article may have changed since.