Forum

Ask, reply and learn. Join the community of Akaunting.

New Discussion

Login after Update

Krammer Andreas   ( User )

Commented 1 week ago

Hi,

i have the following problem. I didn't use akaunting for 2 weeks. Yesterday i wanted to use it. I tried to login and but the login site didn't load.

This was in the log files and the container stopped:


Some options are missing and --no-interaction is present. Please run the following command for more information :
❌ php artisan help install
❌ Missing options are : db-port


After editing the settings of the container and set setup to false, i restartet the container. I entered my credentials at the login screen but nothing happens.

Now i have a big problem to get it work again. I only have backups fom the database. I don*t no what happend. I think the problem comes from an update because i see the login screen in a new design.

Please help me because i am in big trouble.


When i use this line in the container:

php artisan install --db-host "ip_of_dbhost" --db-port "port_number_of_db" --db-name "db_name_here" --db-username "db_username_here" --db-password "db_password_here" --company-name "company_name" --company-email "[email protected]" --admin-email "[email protected]" --admin-password "password_here" --locale "en-US"

with my values, it connects to the database and after a few seconds this error came:


In Connection.php line 742:

SQLSTATE[HY000]: General error: 1005 Can't create table `akaunting`.`2gl_media` (errno: 121 "Du
plicate key on write or update") (SQL: alter table `2gl_media` add constraint `original_media_i
d` foreign key (`original_media_id`) references `2gl_media` (`id`) on delete set null)


In Connection.php line 527:

SQLSTATE[HY000]: General error: 1005 Can't create table `akaunting`.`2gl_media` (errno: 121 "Du
plicate key on write or update")

Best Regards

Jhay Pqb   ( User )

Commented 1 week ago

my advice is install a new one and connect your database.

Krammer Andreas   ( User )

Commented 1 week ago

Hi,

i tried your solution without positive result. The only solutions that works was to restore an old database backup before the update and start akaunting with version 2.1.35.
Thats not good. If there is another way to do, please let me know.

Best Regards

Please login or register to leave a response.

Showing 1 to 3 of 3 discussions