Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] Akaunting

Featured Replies

This is one of the most difficult aps, hard to troubleshoot. Yesterday I've made it work for 10 minute, then it's said is an update, I've updated the docker container, now I can't login! I've deleted the docker reinstalled, use the php artisan command, password is not valid, looked in the user part of the database, used the password stored there and surprise "wrong password".

The docker image, get's an update every 2 days, why this often? Is quite bad, the app is good, don't want the cloud app, I want it on my on server for more privacy. Any ideas how to fix it?

  • Replies 77
  • Views 26.5k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • @Siroguh I have this working as Reverse Proxy using NginX proxy Manager. I did not try with Swag. I recently updated my Swag settings with NginX proxy manager (Easy to manager IMO). Below is my config

  • @eirizarry @Curtis777 @dgwharrison @feins I got mine to work. set AKAUNTING_SETUP=false I think because the container has setup variables, it's expecting setup to be false... Maybe not. But it wor

  • MagicSven
    MagicSven

    is there a solution? As i can see there are update available every 3 days - but i can´t get it to work. I´ve spend 6hrs now. The connection to mariadb is established, but i can´t log in with my userna

Posted Images

On 1/6/2023 at 5:55 AM, blue8lucian said:

This is one of the most difficult aps, hard to troubleshoot. Yesterday I've made it work for 10 minute, then it's said is an update, I've updated the docker container, now I can't login! I've deleted the docker reinstalled, use the php artisan command, password is not valid, looked in the user part of the database, used the password stored there and surprise "wrong password".

The docker image, get's an update every 2 days, why this often? Is quite bad, the app is good, don't want the cloud app, I want it on my on server for more privacy. Any ideas how to fix it?

Yeah. It's best to turn off auto updates, and don't apply any updates for now. I realize that it breaks after each update.

Hello community ! I came back whit another problem! Used the php command 

php artisan install --db-host="mariadb" --db-port="3306" --db-name="akaunting" --db-username="akaunting" --db-password="p)DyZk-nDSedNN3n" --db-prefix="ld" --company-name="LD" --company-email="[email protected]" --admin-email="[email protected]" --admin-password="#2*Szo#7WYEv&2mA&7!U3#Q^QJvsk$y2$H7#uQv2" --locale="US_EN"

 

and I can't login "These credentials do not match our records."

I've tried to change the password in the user table in the database same problem afther!

  • 4 weeks later...
On 1/12/2023 at 2:39 AM, blue8lucian said:

Hello community ! I came back whit another problem! Used the php command 

php artisan install --db-host="mariadb" --db-port="3306" --db-name="akaunting" --db-username="akaunting" --db-password="p)DyZk-nDSedNN3n" --db-prefix="ld" --company-name="LD" --company-email="[email protected]" --admin-email="[email protected]" --admin-password="#2*Szo#7WYEv&2mA&7!U3#Q^QJvsk$y2$H7#uQv2" --locale="US_EN"

 

and I can't login "These credentials do not match our records."

I've tried to change the password in the user table in the database same problem afther!

 

@blue8lucian Does the email and the password that you used in the php command match what you have in your container settings?

  • 3 weeks later...
On 9/29/2022 at 11:38 AM, TekDRu said:

Is there anyone that has this app working?  After initial install and setup 2 weeks ago, the app was working fine. But recently I've been trying to login and I can't get passed the login screen. It just hangs after entering login info.  I do not see any errors in logs and don't know where to go from here. Any help is appreciated. 

 

This is the apps log:

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2. Set the 'ServerName' directive globally to suppress this message
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2. Set the 'ServerName' directive globally to suppress this message
[Wed Sep 28 21:21:22.597968 2022] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.54 (Debian) PHP/8.1.10 configured -- resuming normal operations
[Wed Sep 28 21:21:22.597988 2022] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND'
[Wed Sep 28 21:22:25.014405 2022] [mpm_prefork:notice] [pid 1] AH00170: caught SIGWINCH, shutting down gracefully
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2. Set the 'ServerName' directive globally to suppress this message
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2. Set the 'ServerName' directive globally to suppress this message
[Thu Sep 29 13:55:59.399673 2022] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.54 (Debian) PHP/8.1.10 configured -- resuming normal operations
[Thu Sep 29 13:55:59.399692 2022] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND'
[Thu Sep 29 13:58:56.208050 2022] [mpm_prefork:notice] [pid 1] AH00169: caught SIGTERM, shutting down
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2. Set the 'ServerName' directive globally to suppress this message
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2. Set the 'ServerName' directive globally to suppress this message
[Thu Sep 29 14:00:01.473216 2022] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.54 (Debian) PHP/8.1.10 configured -- resuming normal operations
[Thu Sep 29 14:00:01.473236 2022] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND'
[Thu Sep 29 14:01:51.570443 2022] [mpm_prefork:notice] [pid 1] AH00170: caught SIGWINCH, shutting down gracefully
Enabling module rewrite.
To activate the new configuration, you need to run:
  service apache2 restart
[28/Sep/2022:21:21:34 -0400] "GET / HTTP/1.1" 302 1651 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15"
[28/Sep/2022:21:21:34 -0400] "GET /auth/login HTTP/1.1" 200 4753 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15"
[28/Sep/2022:21:21:50 -0400] "POST /auth/login HTTP/1.1" 500 1211 "http://192.168.50.145:8087/auth/login" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15"
Module rewrite already enabled
[29/Sep/2022:13:56:49 -0400] "GET / HTTP/1.1" 302 1651 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15"
[29/Sep/2022:13:56:49 -0400] "GET /auth/login HTTP/1.1" 200 4755 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15"
[29/Sep/2022:13:57:28 -0400] "POST /auth/login HTTP/1.1" 500 1211 "http://192.168.50.145:8087/auth/login" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15"
Module rewrite already enabled
[29/Sep/2022:14:00:07 -0400] "GET / HTTP/1.1" 302 1651 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15"
[29/Sep/2022:14:00:07 -0400] "GET /auth/login HTTP/1.1" 200 4755 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15"
[29/Sep/2022:14:00:33 -0400] "GET / HTTP/1.1" 302 1651 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15"
[29/Sep/2022:14:00:33 -0400] "GET /auth/login HTTP/1.1" 200 4755 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15"
[29/Sep/2022:14:00:46 -0400] "POST /auth/login HTTP/1.1" 500 1211 "http://192.168.50.145:8087/auth/login" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15"

** Press ANY KEY to close this window ** 

 

1214830609_ScreenShot2022-09-29at2_10_54PM.thumb.png.2eb22813fe2ee22311e65102157e85f5.png

 

 

 

Thanks

 

 

 

 

Having the same issue. I stupidly updated this container thinking it would be fine and it just went to hell. I managed to get the php artisan issue fixed by adding DB_PORT and DB_NAME as variables for the container, however when I try to log in I am having this issue where it is throwing a 500 whenever trying to login. Nothing seems to be fixing it.

 

EDIT: I managed to go through all the latest docker versions downgrading until it worked again. Made it to "akaunting/akaunting:3.0.0" in which everything started working again. Moral of the story, don't update your main instance.

Edited by 97WaterPolo

  • 3 weeks later...

Hi.

Someone solved this problem? I was try all from this topic but nothing work. I was try ver. 3.0.0 too.

16 hours ago, gregoriko said:

Hi.

Someone solved this problem? I was try all from this topic but nothing work. I was try ver. 3.0.0 too.

What errors or problems are you running into?   I am using the app. I do not apply any updates to the container to avoid breaking it.  I was able to update to 3.0.12 from within the app itself.

 

If and when I decide to update the container,  there is a process I go through to restore my existing database and avoid loosing everything. Below is a quick list of steps from memory. I can give more detail if needed.

  1. Backup the current database before making container updates
  2. Apply container updates and go through install process from scratch (with php artisan install commands  etc.) until I have a running app
  3. Open the backed-up sql file in a text editor, and change the first three initials of all tables in to match the first three letters in new table names from new database
  4. Delete all tables from new database
  5. Import sql file from existing database (with new table names) to replace the new database

 

 

7 hours ago, TekDRu said:

What errors or problems are you running into?   I am using the app. I do not apply any updates to the container to avoid breaking it.  I was able to update to 3.0.12 from within the app itself.

 

If and when I decide to update the container,  there is a process I go through to restore my existing database and avoid loosing everything. Below is a quick list of steps from memory. I can give more detail if needed.

  1. Backup the current database before making container updates
  2. Apply container updates and go through install process from scratch (with php artisan install commands  etc.) until I have a running app
  3. Open the backed-up sql file in a text editor, and change the first three initials of all tables in to match the first three letters in new table names from new database
  4. Delete all tables from new database
  5. Import sql file from existing database (with new table names) to replace the new database

 

 

I need Install first. I use mariaDB.
1. With Setup Account: true docker shutdown.
2. Later i was changed Setup Account: true and used in docker terminal (with my data)

php artisan install --db-host="localhost" --db-port="3306" --db-name="akaunting" --db-username="root" --db-password="" --db-prefix="ak3" --company-name="My Company" --company-email="myemailcompany@gmail" --admin-email="[email protected]" --admin-password="mypass" --locale="es-ES"

Base table are created but I can't logg inn. service apache2 restart  doesn't work, docker is closeing. I have log like in this post
3.  I tried adding the new variables for DB_PORT and DB_NAME. It's same.
4. I tried install by portainer with integrate mariaDB:
 

version: '2.1'

services:

  akaunting:
    image: kuralabs/docker-akaunting:latest
    restart: always
    ports:
      - 5003:8080
    environment:
      MYSQL_ROOT_PASSWORD: changeme #Change this password to something at least as long and complicated
    volumes:
      - /mnt/user/appdata/akaunting/mysql:/var/lib/mysql
      - /mnt/user/appdata/akaunting/logs:/var/log
      - /mnt/user/appdata/akaunting/config:/var/www/akaunting/config

but I have other error (screenshot). I don't know what can I do.

unraid akaunting.png

On 3/16/2023 at 6:47 PM, gregoriko said:

1. With Setup Account: true docker shutdown.
2. Later i was changed Setup Account: true and used in docker terminal (with my data)

 

The container Setup Account should be set to false.  Make that change and run the php artisan install command again and see if that gets you to the setup wizard.

 

Is the screenshot from portainer?  I haven't used portainer before so I can't help there. I've only used the docker with mariadb and use adminer to access my databases.

Edited by TekDRu

  • 3 months later...

For those who got f**ked just like I did after updating, please go edit your container and put "akaunting/akaunting:2.1" in your repository section. This will role it back to the last image before v3 which causes all sorts of issues.

 

I found this video to be helpful.

 

 

It is now working for me again. I was scared that I lost 2 years worth of tracking in this software.

  • 4 months later...

This looks like it'd be super useful for me, but I've had no luck trying to get it up and running.

 

Before I try the 2.1 version as above, wondering whether there's been any advances on getting the latest versions working in the last 6 months.

  • 1 month later...
On 11/26/2023 at 11:50 PM, -C- said:

This looks like it'd be super useful for me, but I've had no luck trying to get it up and running.

 

Before I try the 2.1 version as above, wondering whether there's been any advances on getting the latest versions working in the last 6 months.

Same question from me.

I used the custom string as suggested, which removed the DB NAME and DB PORT error. But now im left with this:
image.thumb.png.a4b64b523e94e03561e442adb73701a4.png

 

Rolling back toakaunting/akaunting:2.1 is worth it? Or do I just look for a different app?

Edited by K1LLA_KING_KING

On 3/16/2023 at 11:16 PM, TekDRu said:

What errors or problems are you running into?   I am using the app. I do not apply any updates to the container to avoid breaking it.  I was able to update to 3.0.12 from within the app itself.

 

If and when I decide to update the container,  there is a process I go through to restore my existing database and avoid loosing everything. Below is a quick list of steps from memory. I can give more detail if needed.

  1. Backup the current database before making container updates
  2. Apply container updates and go through install process from scratch (with php artisan install commands  etc.) until I have a running app
  3. Open the backed-up sql file in a text editor, and change the first three initials of all tables in to match the first three letters in new table names from new database
  4. Delete all tables from new database
  5. Import sql file from existing database (with new table names) to replace the new database

 

 

what are you doing with this error?
image.thumb.png.aed14efc87dfb2c88de03ef2b7ce99e7.png

12 hours ago, K1LLA_KING_KING said:

what are you doing with this error?

Did you already run the "php artisan install" script?

On 1/8/2024 at 5:31 AM, TekDRu said:

Did you already run the "php artisan install" script?

yes. Or I would be getting differnt error re: missing db port etc

hey @K1LLA_KING_KING, can you share a screenshot of your container or the docker run command to see If I notice any issues with the settings.

  • 1 month later...

Discovered a solution to updating the container without issue.  Adding variables for "DB_PREFIX" and "APP_INSTALLED=true" did the trick for me.  Got some help from these posts:

 

https://github.com/akaunting/docker/issues/61#issuecomment-1143664641

https://github.com/akaunting/docker/issues/107

 

For the DB_PREFIX variable,  you will need to use the first 4 characters seen in your specific existing database tables names.

 

I would advice backing up your database and appdata before making these edits.

 

 

 

Screenshot 2024-02-20 at 6.19.56 PM.png

Screenshot 2024-02-20 at 6.20.06 PM.png

Screenshot 2024-02-20 at 6.20.21 PM.png

Screenshot 2024-02-20 at 6.44.22 PM.png

  • 1 month later...

I've just install Akaunting and setup postgresql15.

When i try to launch Akaunting the log show this error and no login page.

 

Enabling module rewrite.
To activate the new configuration, you need to run:
  service apache2 restart
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, db-name
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, db-name
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, db-name
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, db-name
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, db-name
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, db-name

** Press ANY KEY to close this window **

  • 3 months later...
On 4/7/2024 at 6:47 PM, feins said:

I've just install Akaunting and setup postgresql15.

When i try to launch Akaunting the log show this error and no login page.

 

Enabling module rewrite.
To activate the new configuration, you need to run:
  service apache2 restart
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, db-name
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, db-name
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, db-name
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, db-name
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, db-name
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, db-name

** Press ANY KEY to close this window **

I'm having exactly the same issue.  Did you get it running? @Yoda can you help?

  • 5 months later...

anyone had luck getting it Running ?

  • 2 months later...

Hello, i have a problem with my akaunting docker. Akaunting says i have reached the maximum number of companies but i have only one companie. How i can fix this?  image.thumb.png.7218ddb57f8805b45e2b6f60aa26e674.png

On 4/7/2024 at 4:47 AM, feins said:

I've just install Akaunting and setup postgresql15.

When i try to launch Akaunting the log show this error and no login page.

 

Enabling module rewrite.
To activate the new configuration, you need to run:
  service apache2 restart
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, db-name
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, db-name
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, db-name
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, db-name
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, db-name
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, db-name

** Press ANY KEY to close this window **

I just installed a copy like 1hr ago and I’m getting this same error. For some reason I can’t edit the yml or config file that’s inside the actual container. I filled out all spaces in unraid but the app stops working because it has default values already pre set. It doesn’t have a folder in the app data folder to edit neither. For some reason what’s input in unraid is not overwriting that config file.

  • 2 months later...

@eirizarry @Curtis777 @dgwharrison @feins I got mine to work.

set AKAUNTING_SETUP=false

I think because the container has setup variables, it's expecting setup to be false... Maybe not. But it worked for me.


image.png


image.png

  • 3 months later...

Looks like I have lost all my old attachments from last year in the bills. Is there any way to get access to them. If I click them, instead of downloading, it shows something like: http://192.168.1.145:0121/1/uploads/139/download

upon further investigation looks like all the last 5 years is gone...this is a nightmare....

how come akaunting docker does not use a share like app data to store the documents?

Edited by war1000

  • 4 months later...

I just spent 3 hours trying to get this running and seem to have the same issues. i can not get it started...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.