[PR #1] Fixes Error in Install #97

New issue

Closed

opened 2026-02-26 17:31:25 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 17:31:25 +03:00

Owner

Original Pull Request: https://github.com/ConvoyPanel/panel/pull/1

State: closed
Merged: No

When running php artisan migrate you run into the following error on a fresh database:

SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'installing' (SQL: alter table `servers` add `installing` tinyint(1) not null default '0' after `description`)

  at vendor/laravel/framework/src/Illuminate/Database/Connection.php:759
    755▕         // If an exception occurs when attempting to run a query, we'll format the error
    756▕         // message to include the bindings with SQL, which will make this exception a
    757▕         // lot more helpful to the developer instead of just the database's errors.
    758▕         catch (Exception $e) {
  ➜ 759▕             throw new QueryException(
    760▕                 $query, $this->prepareBindings($bindings), $e
    761▕             );
    762▕         }
    763▕     }

      +9 vendor frames 
  10  database/migrations/2022_08_02_042345_replace_is_installing_column_with_installing_in_servers_table.php:19
      Illuminate\Support\Facades\Facade::__callStatic()

      +25 vendor frames 
  36  artisan:37
      Illuminate\Foundation\Console\Kernel::handle()

Changing from installing back to is_installing, has fixed the issue for me.

**Original Pull Request:** https://github.com/ConvoyPanel/panel/pull/1 **State:** closed **Merged:** No --- When running `php artisan migrate` you run into the following error on a fresh database: ``` SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'installing' (SQL: alter table `servers` add `installing` tinyint(1) not null default '0' after `description`) at vendor/laravel/framework/src/Illuminate/Database/Connection.php:759 755▕ // If an exception occurs when attempting to run a query, we'll format the error 756▕ // message to include the bindings with SQL, which will make this exception a 757▕ // lot more helpful to the developer instead of just the database's errors. 758▕ catch (Exception $e) { ➜ 759▕ throw new QueryException( 760▕ $query, $this->prepareBindings($bindings), $e 761▕ ); 762▕ } 763▕ } +9 vendor frames 10 database/migrations/2022_08_02_042345_replace_is_installing_column_with_installing_in_servers_table.php:19 Illuminate\Support\Facades\Facade::__callStatic() +25 vendor frames 36 artisan:37 Illuminate\Foundation\Console\Kernel::handle() ``` Changing from `installing` back to `is_installing`, has fixed the issue for me.