corbetto
-
Posts
7 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by corbetto
-
-
I did make some further progress by adding the SeverName line to my local server ip with port for akaunting in the apache.conf file within the console - this stopped the fully qual'd domain name error. But i still cannot get pass the login, allthough the logs say that its POST ing
-
1 minute ago, Danuel said:
if you open akaunting console and type "service apache2 restart" still not working ?
Yup still not working, it shuts down container then this appears in log:
Module rewrite already enabled
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.6. Set the 'ServerName' directive globally to suppress this message
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.6. Set the 'ServerName' directive globally to suppress this message
[Sun Jun 19 19:31:27.215839 2022] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.53 (Debian) PHP/8.1.7 configured -- resuming normal operations
[Sun Jun 19 19:31:27.215879 2022] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND' -
Still having issues not been able to login now getting this error output any help please!!!
Enabling module rewrite.
To activate the new configuration, you need to run:
service apache2 restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.6. Set the 'ServerName' directive globally to suppress this message
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.6. Set the 'ServerName' directive globally to suppress this message
[Sun Jun 19 19:13:43.286237 2022] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.53 (Debian) PHP/8.1.7 configured -- resuming normal operations
[Sun Jun 19 19:13:43.286280 2022] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND'
172.18.0.1 - - [19/Jun/2022:19:13:51 +1200] "GET / HTTP/1.1" 302 1624 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.123.123.115 Safari/537.36" -
Just updated to the latest version and get constantly stuck on login - just hangs when i press login. Only thing that looks out of order in the log is this:
[2022-06-09 09:25:31] production.ERROR: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'accounting.ak_users' doesn't exist (SQL: select * from `ak_users` where `email` = [email protected] and `ak_users`.`deleted_at` is null limit 1) {"exception":"[object] (Illuminate\\Database\\QueryException(code: 42S02): SQLSTATE[42S02]: Base table or view not found: 1146 Table 'accounting.ak_users' doesn't exist (SQL: select * from `ak_users` where `email` = [email protected] and `ak_users`.`deleted_at` is null limit 1) at /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php:742)
-
UPDATE: Just turned off system ran CHKDSK on seperate PC and plugged in and seems to be working fine. Would anyone suggest i purchase a new USB?
-
I've just gotten back from holiday to find my server has pooped itself - I've tried signing back in but get "Failed to receive latest server info after successful key install.". Docker service seems to have disapeared but can still access the applications however. Any advice would be appreciated
[Support] Akaunting
in Docker Containers
Posted
Im in the exact same boat, if you find out anything please share!